Definition: Keyboard navigation refers to the ability to access, navigate, and operate all functionality of a website or application using only keyboard inputs — Tab (to move forward through interactive elements), Shift+Tab (to move backward), Enter/Space (to activate), and arrow keys (to navigate within components like menus or sliders) — without requiring a mouse, trackpad, or touch screen. Full keyboard operability is a fundamental web accessibility requirement for users with motor impairments who cannot use pointing devices.
Why It Matters: Keyboard navigation is required by WCAG 2.1 Success Criterion 2.1.1 (Level A — the most critical level) and is one of the most commonly failed accessibility requirements on real-world websites. Beyond users with motor impairments, keyboard navigation is used by power users who prefer keyboard shortcuts, users with temporary injuries (a broken arm, for example), and screen reader users who navigate primarily via keyboard. Custom interactive components — dropdown menus, modal dialogs, carousels, date pickers, and tab panels — frequently fail keyboard navigation because they are built without proper focus management and keyboard event handling. Testing keyboard navigation requires simply unplugging or disabling a mouse and attempting to complete key user journeys on the website using keyboard alone.
How It Works: Keyboard navigation is implemented through proper HTML semantics (using native HTML elements like <button>, <a>, <input>, and <select> which have built-in keyboard behaviour) and, for custom components, through ARIA roles and keyboard event handlers that replicate expected keyboard behaviour. The Tab key should move through all interactive elements in a logical, reading-order sequence. The currently focused element must have a visible focus indicator (Focus State) — removing the browser’s default outline without providing an alternative is a common WCAG failure. Custom components like modals must trap focus within the dialog when open and return focus to the triggering element when closed. Keyboard navigation testing is performed manually and cannot be reliably automated.
Related: WCAG, Accessibility Audit, Focus State, Screen Reader, ADA Website Compliance