Operable · Level A · Introduced in WCAG 2.0
WCAG 2.1.1: Keyboard
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
Provide keyboard operation for all functionality, without requiring precisely timed individual keystrokes, except for functions whose underlying purpose depends on a movement path. Native HTML controls provide much of this behavior automatically.
A practical example
A product gallery can be advanced by clicking thumbnails but not by keyboard. Use real buttons with clear names, then ensure selection and the enlarged image update when those buttons are activated.
How to check it
- Put the pointer aside and follow each important task using a keyboard.
- Reach and operate controls, menus, dialogs, media players and custom widgets using their expected keys.
- Compare the available keyboard actions with pointer actions and document any genuinely path-dependent function.
What can be missed
Adding tabindex makes something focusable but does not supply its role or activation behavior. A text-entry feature does not become exempt merely because its chosen interface uses handwriting.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.