What WCAG 2.1.2 Requires
Once keyboard focus moves into a component, the visitor must always be able to move focus back out using only the keyboard, with no trap that requires the mouse to escape.
Can AccessBell Test This Automatically?
Not fully. Like most WCAG criteria that depend on meaning or context, this one needs a person to judge. AccessBell's report lists it for manual review rather than marking it pass or fail automatically, so it never gets missed.
How to Test It by Hand
Tab into every modal, widget and embedded frame and confirm Tab, Shift+Tab or Escape always lets you move focus back out.
Common Failures
- A modal dialog has no Escape handler and focus cannot leave it by keyboard.
- An embedded third-party widget (a map, a video player) traps Tab focus inside it.
Related Criteria in Keyboard Accessible
WCAG 2.1.2 Questions
What does WCAG 2.1.2 require?
Once keyboard focus moves into a component, the visitor must always be able to move focus back out using only the keyboard, with no trap that requires the mouse to escape.
Can AccessBell test WCAG 2.1.2 automatically?
Not fully. This criterion needs a person to judge, so AccessBell's report lists it for manual review rather than marking it pass or fail on its own.
What level is WCAG 2.1.2?
Level A, added in WCAG 2.0.
Sources
- W3C: Understanding 2.1.2 No Keyboard Trap (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.