Accessibility
Accessible content and destinations
Short labels, honest provider handoffs and clear public visibility reduce ambiguity.
On this page
Naming guidance
- Use recognizable destination names rather than raw URLs where possible.
- Give public collections a concise title and a useful description within 120 characters.
- Distinguish settings navigation, external search and AI handoff.
- Explain destructive scope in plain language and avoid implying undo.
Observed gaps
Truncated bookmark labels retain a title/full accessible name in the authenticated tile. Public tiles are anchors, but the public page’s main title is h2. Board/accessibility selection state is incomplete. Reset requests intentionally avoid revealing whether an email address exists.
The source URL save contract does not guarantee safe protocols. Privacy and destination validation require source changes separately authorized from documentation.
Source references
| Repository file | Responsibility |
|---|---|
| app/(home)/AppHome.tsx | Labels and provider handoff |
| app/board/[id]/page.tsx | Public outline |
| app/api/auth/request-password-reset/route.ts | Generic recovery response |
Examples from the app
Actual Startboard source UI with isolated fictional records; both native themes at 2× resolution or higher. No live integrations or account writes. Captured at 2× resolution or higher. Select an image to inspect it full size.
Related topics
Source audit: 2026-10-08 · Revision 08fa2595a668 · Documentation v1.0.0