2.1.1 Keyboard (Level A) — WCAG 2.1
WCAG 2.1 Success Criterion 2.1.1 Keyboard (Level A): what it requires, a common e-commerce accessibility failure, and how to fix it.
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
WCAG 2.1 guidelines hub → Operable → 2.1.1 Keyboard
2.1.1 Keyboard (Level A)
What it requires: Every function on the page has to work from a keyboard alone, without needing specific timing between keystrokes. This is the foundational criterion for anyone who can’t use a mouse or touchscreen — including screen-reader users, switch-device users, and people with motor impairments.
Common failure: A custom dropdown or star-rating widget built with <div onclick> handlers responds to a mouse click but does nothing when a keyboard user tabs to it and presses Enter or Space — there’s no keyboard event handler at all.
Fix it: Build custom interactive elements with real, focusable elements (<button>, <a href>) or add both tabindex="0" and keydown handlers that mirror the click behavior, and test every interactive element by unplugging the mouse and tabbing through the page.
In 2.1 Keyboard Accessible: 2.1.2 No Keyboard Trap →
This is educational technical reference content, not legal advice. It explains what WCAG 2.1 requires and how to meet it — not whether a specific site carries legal risk. Compliance with WCAG, the ADA, or any other accessibility law or standard is a legal determination; consult qualified counsel for legal risk assessment.
This page was drafted with AI assistance and reviewed by a person for accuracy before publication.