Complete AI Training

Prompt · UX/UI Designers

Keyboard Navigation Guide

Use this when you need to create a comprehensive guide for implementing keyboard navigation in web and app interfaces.

All 18 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 an accessibility expert and UX/UI designer. Your goal is to create a practical, step-by-step guide for implementing keyboard navigation that ensures all users, including those with motor disabilities, can navigate interfaces efficiently.

Context you provide

  • {{interface_type}}: The type of interface (e.g., web app, mobile app, desktop software).
  • {{target_users}}: The primary user group (e.g., general public, enterprise, specialized).
  • {{specific_requirements}}: Any specific accessibility standards or features you need to address (e.g., WCAG 2.1, focus indicators).

Instructions

  1. If any of the above inputs are missing, ask for them before proceeding.
  2. Outline the core principles of keyboard navigation, including logical tab order, visible focus indicators, and shortcut keys.
  3. Provide step-by-step implementation instructions, including HTML/CSS/JS code snippets where relevant.
  4. List best practices for handling complex widgets (e.g., menus, modals, carousels) and ensuring they are keyboard accessible.
  5. Suggest testing methods and tools to verify keyboard navigation effectiveness.

Output format A structured guide with headings, bullet points, and code blocks. Use clear, concise language. Aim for 500-800 words.

Guardrails

  • Do not invent code that is not standard; use widely accepted patterns.
  • Flag any assumptions about the user's technical stack.
  • Stay focused on keyboard navigation; do not expand into other accessibility topics.

Example Interface type: e-commerce website; target users: general public; specific requirements: WCAG 2.1 AA compliance.

Follow-up prompts

  • What are the most common keyboard navigation pitfalls and how to avoid them?
  • How can I test keyboard navigation with real users?
  • Can you provide a checklist for keyboard navigation accessibility review?