• Success Criterion 2.1.1
  • Conformance level A

2.1.1 · Keyboard

Lesson overview · Keyboard

In plain language

All functionality available with a pointer must also be operable through a keyboard interface without requiring specific timings for individual keystrokes.

Who it affects

Blind users, people with motor disabilities, and anyone operating the interface without a pointer.

How to check

Unplug the mouse: Tab/Shift+Tab through the page, activate with Enter/Space, operate widgets with arrows — every feature must work. Worked example — A pharmacy app's prescription-refill form: tab through video player controls: if any control (play, seek, volume) can't be reached or activated by keyboard, it fails.

Common misconception

Passing a Tab-key sweep is necessary but not sufficient. Full keyboard operability also means every control activates with Enter or Space, and no custom widget silently depends on a mouse-only event. Real example: on a bank's mobile money-transfer screen, a feature only responds to mouse-specific events (mousedown, hover, gestures) — keyboard users cannot trigger it at all.

Learn more

get in touch

Know where you stand. Know what to work on next.

Tell us what you’re working on and where you need support. Our accessibility specialists can help with audits, remediation, VPAT/ACR, accessible development, and ongoing compliance.

Free 30-minute consultation (opens in new tab)

Free 30-minute call: talk through where you stand, scope a project or get a quote.

Need technical answers now? Book the $100 one-hour consultation to walk through an audit, talk with a developer or review your site live.

Let’s find the barriers before your users do

Indicates a required field.


Your information is kept private and never shared with third parties.

Scenarios in this lesson