smukh Keyboard navigation review
Evaluate a bounded task with real browser key presses. Synthetic keyboard evidence is useful but is not complete assistive-technology evidence.
Workflow
- Define the starting URL/state, viewport, task completion condition, and expected focus behavior.
- Run
a11y-agent keyboard <url> --journey <file>or perform the equivalent physical-key review. Journey files must use only the bounded actions in references/journey-review.md; never add arbitrary JavaScript. - Check reachability, visible focus, logical sequence, traps, skip links, composite-widget arrow-key behavior, route/state changes, dialog entry, and focus restoration.
- Record every action, resulting focused element, accessible name, and failure reason.
- Replay any repair from the identical starting state and add a behavior-focused regression journey.
Boundaries
Do not infer that a passing scripted journey works with every keyboard layout, switch device, voice input system, browser, or screen reader. Manual review remains required for visual focus quality and task-level sequence judgment.