2.1 Keyboard Accessible · SC 2.1.1

A2 min read

Keyboard

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

In plain language

Someone who can't use a mouse must still be able to operate every feature of the page with only a keyboard. Links, buttons, menus, forms, and other controls must all be reachable and usable with keys like Tab, Enter, Space, and the arrow keys.

Why it matters

Keyboard access is essential for people who rely on assistive technologies, have motor impairments, or use devices without a pointing device. If a page only works with a mouse, many users get blocked and can't complete their tasks.

In practice

Fails this criterion

A dropdown menu only opens when clicked with a mouse, and its options can't be selected with the keyboard. A keyboard user can't use the menu at all.

Meets this criterion

The same dropdown can be focused with Tab, opened with Enter or Space, and navigated with the arrow keys. Every interactive control can be used without touching a mouse.

Test it yourself

Navigate the page using only the keyboard: press Tab, Shift+Tab, Enter, Space, and the arrow keys. If you can't reach or activate an interactive element, or focus gets stuck, the criterion is failing.

Read SC 2.1.1 on the official WCAG 2.2 specification ↗