Create Accessible Keyboard Navigation Maps for Complex Web Layouts
Generate a logical, WCAG-compliant keyboard navigation sequence for complex web components to ensure full usability for screen reader and keyboard-only users.
Prompt
Act as a Senior Accessibility Engineer. I will provide the HTML structure or a visual description of a web interface. Create a detailed keyboard navigation map. Follow these rules: 1. Define the exact tab order for all interactive elements. 2. Specify where roving tabindex patterns should be applied for navigation grids or tab lists. 3. Identify boundaries for focus traps in modals or off-canvas menus. 4. List any potential keyboard shortcut collisions with existing browser or screen reader commands. 5. Note the visual focus indicator requirements for each state. This information is for technical guidance and does not replace manual accessibility testing or compliance audits. Consult a certified accessibility specialist for legal verification. Output format: 1. Keyboard Navigation Map (Markdown Table with columns: Element, Tab Order, Focus Behavior, Notes). 2. Roving Tabindex Strategy (List of implementation steps). 3. Focus Trap Logic (Description of boundaries and exit conditions). 4. Potential Conflicts (List of risks). Please ask me to paste the interface description or HTML code now.Example output
Tips and common edits
Why this works
- Forces a structured, table-based audit that makes complex tab orders easy to visualize.
- Specifically addresses the technical nuance of roving tabindex vs focus traps.
- Includes a mandatory accessibility disclaimer to ensure professional responsibility.
Use this when building or auditing complex UIs like sidebars, modals, or data grids. Paste your HTML or a clear description of the component structure. Works in ChatGPT, Claude, and Gemini.
Common edits
- Add specific browser-testing requirements if you are optimizing for Safari versus Chrome.
- Include a section for screen reader announcements if the interface updates dynamically.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Keep exploring
More like this
Write accessible alt text for product and UI imagery
Produce concise, accessible image descriptions that prioritize functional context for screen-reader users over visual fluff.
Create a WCAG 2.2 AA Accessibility Audit Checklist
Receive a structured accessibility audit checklist for complex interactive components based on WCAG 2.2 AA standards.
Audit mobile forms for keyboard friction
Identify mismatched mobile keyboards, missing autocomplete attributes, and form fields that slow down mobile completion.
Audit mobile screens for thumb reach
Evaluate mobile UI layouts to fix out-of-reach controls, tight tap targets, and accidental mis-taps on handheld devices.
Check mobile layouts against dynamic font scaling
Review mobile UI against dynamic font scaling and accessibility text sizes. Use it to catch truncated text, clipped buttons, and broken navigation before handoff.
Create an information architecture and menu tree
Organize cluttered navigation items into a logical, task-oriented app menu hierarchy. Ideal for product redesigns and software cleanup.
- Plan a wireframe content hierarchy before sketching
- Audit and Rewrite UX Error Messages for User Recovery
- Audit Form Labels and Helper Text for UX Clarity
- Design a Progressive Disclosure Pattern for Complex Settings
- Build a Live Accessible Color Palette Builder with a WCAG Contrast Matrix
- Build a Multi-Step Onboarding Wizard with Stepper and Inline Validation