Admin Keyboard And Tab-Order Audit
Representative keyboard and focus expectations for the admin routes covered by the current hardening pass.
Before you start
- You are reviewing admin keyboard behavior, focus order, or shortcut coverage before release.
Expected outcome
You can verify the expected focus order, shortcut behavior, and layer-dismissal rules across the audited admin routes.
Admin keyboard and tab-order audit
This audit covers the representative admin routes used in the current keyboard-hardening pass.
Pages reviewed
- Dashboard
- Sites
- Inspections
- Defects
- Scheduling
- Organization
- Account settings
Expectations
- Every primary action is reachable with
Tab. - Transient layers restore focus to the trigger when they close.
Esccloses only the topmost layer.- Search, menus, and shortcut help do not steal focus from editable controls unexpectedly.
- Tab order follows the visual reading order of the page.
Route checks
Dashboard
- Shell actions receive focus before dashboard content.
Cmd/Ctrl+Kopens global search.?opens keyboard shortcuts and restores focus on close.
Sites
- Search, filters, table, and
Create siteaction tab in visual order. Shift+Nopens the create-site dialog.- Closing the site dialog restores focus to the
Create sitetrigger.
Inspections and defects
- List filters precede row actions.
- Row action menus keep arrow-key behavior and return focus on close.
Scheduling
- Planner controls precede timeline content.
- Dialog launches restore focus to their trigger.
- Keyboard-only users can enter and leave scheduling overlays safely.
Organization
- Section buttons are reachable before section content.
Shift+Iopens the invite-member dialog.- Settings search results are reachable and their actions are explicit.
Account settings
- Personal settings sections read top to bottom without hidden jumps.
- Toggle controls, passkey actions, and password/email forms follow the visible order.
Follow-up notes
- Legacy specialized widgets that remain allowlisted for raw controls must preserve logical tab order.
- Any new page-level shortcut should be registered in the shared shortcut sheet and tested against editable-field focus rules.