Accessibility architecture
The canvas is one view, not the whole interface.
Fabric uses semantic application chrome, labeled form controls, visible focus, and a read-only list for shared board content while keeping the whiteboard’s current accessibility boundary explicit.
See the Semantic ModelShared-board representation
One shared board, two ways to inspect it.
The public canvas and semantic list read the same saved board projection. The list is a reading aid, not a full editing replacement.
Onboarding findings
Frame 1 of 3
Quote: I want to explore first.
Theme: Preserve momentum.
Spatial canvas view · pan, zoom, select, arrange
Read-only Board List
Frame
Onboarding findings
3 children
Note
Quote: I want to explore first
Position 180, 120
Note
Theme: Preserve momentum
Position 520, 120
Connector
Quote to theme
Straight route
Core principles
Access starts outside the canvas pixels.
Fabric keeps navigation, permissions, comments, sharing, recovery, and AI review in semantic controls, then states where canvas equivalence remains incomplete.
- Semantic shared view
- A shared board can expose its stored semantic objects as an ordered DOM list alongside the read-only canvas.
- Standard controls
- Workspace, account, member, comment, share, checkpoint, and AI flows use labeled buttons, links, dialogs, and form controls.
- Visible focus and state
- Interactive controls expose focus, disabled, loading, error, sync, and approval states without relying on color alone.
- Known canvas boundary
- The tldraw editor provides its own keyboard and accessibility behavior, but Fabric does not claim a complete non-spatial authoring equivalent.
Keyboard path
Product workflows use ordinary controls.
The application shell and collaboration workflows remain reachable through labeled links, buttons, forms, and dialogs; spatial authoring still depends on the canvas editor.
| Task | Current Keyboard Path | Boundary |
|---|---|---|
| Open or create a board | Tab to the board link or Create Board button, then press Enter or Space | Requires an authenticated workspace |
| Manage members | Use the labeled email, role, and member action controls | Owner capability required for changes |
| Read or write comments | Open Comments and use the thread and reply forms | Comment capability and sign-in rules apply |
| Review an AI proposal | Use Instructions, Generate Proposal, Discard Preview, and Apply Proposal | Requires an editable, fully synced board |
| Author on the canvas | Use the tldraw toolbar and its keyboard commands | No complete non-spatial editing equivalent is asserted |
Device contract
Different inputs, explicit scope.
Responsive layouts adapt application controls by viewport while the dense whiteboard remains most capable with desktop-sized input and space.
Desktop
The complete workspace and whiteboard UI is available with mouse, trackpad, keyboard, and standard form controls.
Tablet
Responsive controls and the touch-capable canvas are available; no independent real-device certification is claimed.
Phone
Workspace, shared-board, and comment surfaces adapt to narrow screens; dense canvas authoring remains viewport constrained.