Can keyboard users navigate the site or application content and not get “trapped” within components on the page?
Why is this important?
Some users with visual or physical impairments may not be able to use pointing devices, such as a mouse. These users need to be able to access content and navigate using keystrokes, such as the tab key, arrow keys or other keyboard commands. Using only the keyboard, they must be able to enter, interact, and exit all content (e.g. modal dialogue boxes, video players, etc.).
Whom does it benefit?
As a person who is blind and cannot use a mouse,
I want to tab through my assignment calendar and exit without being trapped within it
so that I can quickly view my upcoming due dates.
As a person with severe fine motor impairments,
I want to use my mouth stick to navigate modal dialog boxes
so that I can read the content and not get trapped within it.
What should you do?
- Make sure users can navigate using keyboard-only controls without getting stuck within subsections of a page.
- Ensure users can navigate by either the Tab or arrow keys.
How do you do it?
- Use standard HTML coding whenever possible.
- If the site or application uses intentional trapping, provide clear instructions to end the keyboard trap.
Need technical guidance?
Technical guidance is available for implementing this Success Criterion at the Understanding Success Criterion 2.1.2: No Keyboard Trap page.
Additional resources to help you