Back to Research & Compliance Index
WCAG 2.0Level AOperableMandatory for ADA Title II
WCAG 2.1.1: Keyboard
All functionality of the content must be operable through a keyboard interface without requiring specific timings for individual keystrokes.
Requirement Overview & Intent
If all functionality can be operated using a keyboard, it can be operated by vision-impaired users (who cannot see a mouse pointer) and by people who must use alternate keyboards or speech-input tools.
Common Technical Failures
- 1Attaching click event handlers to non-interactive `<div>` or `<span>` elements without `tabIndex={0}` or keypress handlers.
- 2Custom dropdown menus that only open on hover (`mouseenter`) without focus triggers.
- 3Drag-and-drop interfaces without keyboard arrow key alternatives.
Remediation & Code Fixes
- ✓Replace clickable `<div>` elements with standard `<button>` or `<a>` HTML elements.
- ✓Add `onKeyDown` listeners for `Enter` and `Space` keypresses on custom controls.
Need an immediate code review or PDF tag check?
Ask Luke to inspect your page markup, analyze contrast ratios, or verify veraPDF structure compliance.