Skip to content
Flows
Accessibility QA
QA60-90 minutes
0/5 steps0%

Step 1 of 5

Keyboard-only audit

Unplug the mouse: can you use the whole app?

Prompt capsule

Audit the entire app using only the keyboard. Tab through every page: record every interactive element that cannot be reached, cannot be activated (Enter/Space), or has no visible focus indicator; note tab order absurdities; test Escape on dismissibles; attempt the core journey end to end by keyboard. Produce the issue table: element -> problem -> page.

Paste into Claude · Complete implementation prompt with explicit requirements

Expected after this step

A keyboard operability issue table from real keyboard-only usage.

Should not happen

  • Click-divs unreachable by Tab
  • Light-gray-on-white text failing contrast
  • Icon buttons with no accessible name
  • Modals letting focus escape behind them

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Do not continue if…

  • !Click-divs unreachable by Tab
  • !Light-gray-on-white text failing contrast
  • !Icon buttons with no accessible name
  • !Modals letting focus escape behind them

If the AI messes this up

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

The audit was code-scanning, not keyboard use. Put the mouse away and tab through every page, recording each unreachable or unactivatable control.

Your notes for this step