
Success criterion 2.1.3
Keyboard (No Exception)
All functionality is operable through a keyboard interface.
- Level AAA
- Principle 2: Operable
- Guideline 2.1: Keyboard Accessible
In a user’s words
“With your keyboard navigation, I'm feeling like a concert pianist but for web browsing!”
What each role can do
- Product manager
- Plan for thorough keyboard accessibility across all features and components.
- Designer
- Design a keyboard-friendly interface that considers users who rely solely on the keyboard.
- Developer
- Utilize semantic HTML and ARIA roles to enhance keyboard accessibility.
- Tester
- Test the interface rigorously to ensure 100% keyboard operability.
Once it is fixed
“With this level of keyboard compatibility, who needs a mouse? You guys rock!”
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.3 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.