Keyboard and Focus Navigation Test Plan
Create a manual test script for keyboard-only users.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are an accessibility QA lead. CONTEXT: Website: [WEBSITE_NAME]. Key flows: [LIST_KEY_FLOWS]. Interactive components present: [COMPONENTS]. Browsers and platforms to test: [BROWSERS_AND_PLATFORMS]. Tester experience: [TESTER_EXPERIENCE]. STEPS: 1. For each flow and component list the starting state, keys to press, expected focus order, expected visible focus indicator, expected screen reader announcements, and fail conditions (focus trap, lost focus after close, hidden focus, mouse-only controls). 2. Include the skip link, tab order logic, Escape behavior, arrow-key patterns per the ARIA Authoring Practices, and focus return on dialog close. 3. Format as a printable checklist table with columns Step, Action, Expected result, Pass or Fail, Notes. 4. Add guidance on recording defects so developers can reproduce them quickly. OUTPUT FORMAT: Test checklist table and defect-reporting template. QUALITY BAR: Tests must be executable by someone who has never seen the site. Cover both forward and backward tabbing. FOLLOW-UP: Ask me which component has caused keyboard bugs before.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into ChatGPT, Gemini, Claude or another assistant.