2.1 Keyboard Accessible · Operable
WCAG 2.1.1 Keyboard
Level A
All functionality must be operable through a keyboard interface — Tab to move, Enter/Space to activate, arrow keys for grouped controls — with no required mouse-only gestures.
Common failures
- Custom dropdowns built on `<div onclick>` can't be opened with the keyboard.
- Drag-and-drop interactions have no keyboard alternative.
- Modal close buttons are reachable only via mouse.
How to fix
- Use native interactive elements (`<button>`, `<a>`, `<select>`) wherever possible.
- For custom widgets, follow the ARIA Authoring Practices Guide for keyboard models.
- Provide an explicit keyboard alternative for any pointer-only interaction.
Related criteria
- WCAG 2.1.2 No Keyboard Trap Level A
- WCAG 2.4.3 Focus Order Level A
- WCAG 2.4.7 Focus Visible Level AA