WCAG 2.1.3: Keyboard (No Exception) (Level AAA)
If your mouse isn’t working or you’re navigating a site using only a keyboard, you expect to be able to access every feature—no exceptions. For users who rely on keyboards, if a website can’t be fully operated without a mouse, it becomes unusable. Keyboard (No Exception) ensures that every part of a website is accessible using just a keyboard, so no one is excluded from using key functions.
Who this impacts
- People with motor impairments: Users who depend on the keyboard to navigate need to be able to access every interactive element.
- Screen reader users: Many assistive technologies require full keyboard navigation, and any missing functionality limits their access to content.
- People in temporary situations: Whether your mouse battery dies or you’re using a device without a mouse, full keyboard accessibility is critical.
- Everyone: Making all features keyboard-accessible ensures a more flexible, inclusive experience for all users.
How to meet Keyboard (No Exception)
- Ensure full keyboard access: Make sure that all interactive elements, including menus, buttons, and forms, can be accessed and used entirely via the keyboard without requiring a mouse.
- Test for full functionality: Regularly test your site to confirm that users can perform every action using keyboard commands, such as Tab and Enter, without exceptions.
- Provide visible focus indicators: Ensure there is a clear visual indicator showing which element is currently in focus so users know where they are on the page as they navigate with the keyboard.
Practical example
A productivity app ensures that users can access every part of its interface using only the keyboard. From navigating dropdown menus to completing forms and pressing buttons, everything can be done without a mouse, with a clear focus indicator showing where users are on the screen.
Exceptions
Unlike other guidelines, 2.1.3 does not allow any exceptions. All site functionality must be keyboard-accessible, regardless of the content or interface type. So bear this in mind, as locking people into cookie banners isn’t allowed if you’re trying to meet AAA requirements.
Top tips
- Test for complete keyboard accessibility: Regularly navigate your entire site using only the keyboard to ensure full functionality, no matter the device.
- Ensure focus visibility: Make sure users can always see which element is in focus as they navigate the page using keyboard commands.
- Design for flexibility: Consider how users who rely on keyboards will interact with your site and build in keyboard shortcuts where possible to enhance the experience.