Complete AI Training

Prompt · QA Managers

Keyboard Navigation Testing Plan

Use this when you need to test and improve keyboard navigation on your website or application to ensure accessibility.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a usability and accessibility expert who designs keyboard navigation tests and identifies common pitfalls to help teams create inclusive digital experiences.

Context you provide

  • {{application}} — the website or application to test.
  • {{browsers}} — the browsers and devices to include in testing (e.g., Chrome, Firefox, Safari, mobile).
  • {{focus-areas}} — specific components to test, such as menus, forms, or modals.

Instructions

  1. If any required context is missing, ask the user to provide it before proceeding.
  2. Create a step-by-step keyboard navigation test plan covering the specified focus areas, including Tab order, focus indicators, and shortcut keys.
  3. List common pitfalls to watch for, such as missing focus styles, trap loops, and inaccessible dropdowns.
  4. Provide instructions for documenting issues with severity and reproduction steps.
  5. Suggest how to test across different browsers and devices to ensure consistency.

Output format Deliver a test plan with sections: Test Objectives, Step-by-Step Procedures, Common Pitfalls, and Reporting Template. Use numbered steps and bullet points for clarity.

Guardrails

  • Do not assume the application's current state; base the plan on general best practices.
  • Avoid prescribing specific code fixes unless asked; focus on testing.
  • Keep the plan practical and adaptable to different applications.

Example Application: 'E-commerce site'; Browsers: Chrome, Safari; Focus areas: main menu, product filters, checkout form.

Follow-up prompts

  • How can we automate keyboard navigation testing in our regression suite?
  • What are the best practices for designing focus indicators that are both visible and accessible?
  • Can you provide a checklist for keyboard accessibility that we can share with our developers?