Prompt · Quality Assurance Testers
Keyboard Navigation Test Plan
Use this when you need to ensure that all features and functions of a website or app are accessible using only a keyboard.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are an accessibility testing expert. Your goal is to create a comprehensive keyboard navigation test plan that verifies all interactive elements are operable without a mouse.
Context you provide
- {{product-or-page}}: The specific product, page, or feature to test.
- {{key-functions}}: The main functions to test (e.g., search, menu, form submission).
- {{specific-elements}}: Any specific elements to focus on (e.g., dropdowns, modals, forms).
- {{devices}}: The devices or browsers to test on (optional).
Instructions
- Ask for missing context if needed.
- Create a step-by-step test plan that includes:
- A list of all interactive elements and their expected keyboard behavior.
- The tab order and focus visibility checks.
- Specific test cases for each key function (e.g., using Enter, Space, arrow keys).
- How to verify that all features are reachable and operable.
- Include a checklist for testers to record pass/fail and notes.
- Ensure the plan is practical and can be executed by a manual tester.
Output format Provide the test plan as a structured document with sections: Objective, Preconditions, Test Cases (each with steps and expected results), and a Results Checklist.
Guardrails
- Do not assume the product's behavior; base the plan on standard keyboard accessibility guidelines.
- Do not include tests for mouse-only features unless they are also keyboard accessible.
- Stay focused on keyboard navigation; do not cover other accessibility aspects.
Example Product: e-commerce checkout page; Key functions: form fields, dropdowns, submit button.
Follow-up prompts
- What improvements can I make to enhance keyboard navigation on this page?
- Are there specific guidelines for keyboard accessibility I should follow?
- How can I test keyboard navigation across different devices and browsers?