Flows workflow logoFlows
Accessibility QA
0/5 steps0%

Step 1 of 5

Keyboard-only audit

Unplug the mouse: can you use the whole app?

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

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 EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

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

Should NOT happen

  • An existing feature broke
  • A button only logs to console
  • Data disappears after refresh
  • Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Track what changed, failed, or needs follow-up. Notes export with the flow.

Made with Emergent