Success criterion 2.1.1
Keyboard
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
- Level A
- Principle 2: Operable
- Guideline 2.1: Keyboard Accessible
In a user’s words
“Mouse? Who needs a mouse when you've got keyboard kung fu skills?”
What each role can do
- Product manager
- Ensure all features are accessible via keyboard navigation.
- Designer
- Design with keyboard shortcuts and focus indicators.
- Developer
- Implement robust keyboard navigation and avoid using keyboard traps.
- Tester
- Test extensively for keyboard-only operation across various browsers.
Once it is fixed
“You just made my keyboard the magic wand of the Internet. Hats off to you!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 2.1.1 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.