Keyboard Accessibility Audit Guide
Step-by-step guide to auditing keyboard accessibility per WCAG 2.1. Covers keyboard operability (2.1.1), no keyboard traps (2.1.2), focus order (2.4.3), and focus visible (2.4.7).
Detailed Explanation
Keyboard Accessibility Audit
Keyboard accessibility is fundamental to web accessibility because it enables access for users who cannot use a mouse, including screen reader users, motor-impaired users, and power users who prefer keyboard navigation.
Relevant WCAG Criteria
| Criterion | Level | Name |
|---|---|---|
| 2.1.1 | A | Keyboard |
| 2.1.2 | A | No Keyboard Trap |
| 2.1.4 | A | Character Key Shortcuts |
| 2.4.1 | A | Bypass Blocks |
| 2.4.3 | A | Focus Order |
| 2.4.7 | AA | Focus Visible |
| 2.5.1 | A | Pointer Gestures |
Testing Methodology
Unplug your mouse (or disable your trackpad) and test the entire page:
Tab through all elements — Press Tab repeatedly to visit every interactive element. Verify focus moves in a logical order matching the visual layout.
Activate every control — Use Enter for links and buttons, Space for checkboxes and buttons, arrow keys for radio groups and selects.
Check for keyboard traps — Ensure you can always Tab away from any element. Modal dialogs should trap focus within the dialog but release it when dismissed.
Verify skip links — Press Tab on page load. A "Skip to main content" link should appear and function correctly.
Test focus visibility — Every focused element must have a visible indicator (outline, ring, background change).
Test custom widgets — Dropdowns, date pickers, carousels, accordions, and modals must all be fully keyboard-operable.
Common Failures
- Custom dropdowns that only open on mouse click
- Modals that do not trap focus or cannot be closed with Escape
- Carousels with no keyboard controls for slides
- Drag-and-drop interfaces without keyboard alternatives
- Hidden focus caused by
outline: nonewithout a replacement indicator - Off-screen elements that receive focus and confuse tab order
Use Case
Keyboard accessibility testing should be performed on every page and every interactive component. It is especially critical for single-page applications with dynamic content, modal dialogs, and custom UI widgets. QA engineers should include keyboard-only testing as a standard step in every test plan.
Try It — Accessibility Audit Checklist
Perceivable
Operable
Understandable
Robust
50 criteria shown · Click the status badge to cycle through Pass / Fail / N/A / Untested
Perceivable
Operable
Understandable
Robust
Related Topics
WCAG Level A Accessibility Checklist
Level Checklists
Form Accessibility Checklist and Audit Guide
Category Audits
ARIA Roles and Properties Accessibility Audit
Component Audits
WCAG Color Contrast Accessibility Audit Guide
Category Audits
Screen Reader Testing Guide for Accessibility Audits
Component Audits