2.1.1 Keyboard

What this criterion requires

All functionality must be operable through a keyboard interface, without requiring specific timings for individual keystrokes. Pointer-only interactions are a failure unless the underlying function is path-dependent (like freehand drawing).

Who it helps

People who cannot use a mouse: blind users, people with motor disabilities, switch-device users, power users.

Example: fails vs passes

<div class="btn" onclick="save()">Save</div>

<button type="button" onclick="save()">Save</button>

A native button is focusable and fires on Enter and Space for free. Custom widgets must add the expected key handling.

How to meet and fix it

• Use native interactive elements (button, a, input) which are keyboard-operable for free
• For custom widgets, implement the expected key handling (Enter/Space to activate, arrows within composites)
• Unplug the mouse and complete every task on the site

Common failures auditors find

• Click handlers on div/span with no keyboard path
• Custom dropdowns and date pickers that only respond to pointer events
• Hover-only menus with no keyboard equivalent

Automated scanning catches a share of these instantly - run a free check - and a manual audit covers the judgement calls a tool cannot make.

Last updated 12 August 2026. Reviewed by the EqualWeb accessibility team.