Design Accessible Navigation for Keyboard and Screen Reader Users
Overview
Use semantic landmarks, visible focus, logical tab order, and restrained ARIA to make site navigation understandable and operable.
Use native navigation semantics
Wrap primary site links in a nav landmark with a concise accessible label when multiple navigation regions exist. Use lists for groups of related links and anchors for navigation. Buttons are for actions such as opening a menu, not for changing pages. Avoid clickable div elements that require recreating browser behavior.
Preserve keyboard operation
Every interactive item must be reachable with Tab and operable with the expected key. Keep a visible focus indicator; do not remove outlines without a strong replacement. A menu trigger should be a real button with an accurate aria-expanded value and an aria-controls relationship to the controlled region.
<button type="button" aria-expanded="false" aria-controls="site-menu">
Menu
</button>
<nav id="site-menu" aria-label="Primary navigation">
<ul><li><a href="/guides/">Guides</a></li></ul>
</nav>
Manage focus intentionally
When a dialog-style mobile menu opens, move focus only when the interaction pattern requires it, and return focus to the trigger when it closes. Do not trap focus inside an ordinary disclosure menu. Ensure Escape closes an open overlay and that focus does not disappear behind a closed panel.
Verify with real interaction
Test keyboard-only navigation, browser zoom, a screen reader, and touch input. Check contrast, accessible names, expanded state, and the order in which controls are announced. Automated audits are useful, but they do not replace manual testing of interaction and focus behavior.
Implementation checklist
- Define the expected behavior and supported environments.
- Keep security, accessibility, and failure states in the design.
- Measure the result with representative user journeys.
- Document operational assumptions and review them after changes.