- Success Criterion 2.1.2
- Conformance level A
Non-Standard Focus Exit Key That’s Never Explained to Users
2.1.2 — No Keyboard Trap
Scenario
Setting
A professional networking site's profile editor
What’s wrong
Non-standard exit exists (e.g., Ctrl+M) but user is never advised of it — normative fail of the advisory clause.
Example
Watch a professional networking site's profile editor closely and you'll spot this: non-standard exit exists (e.g., Ctrl+M) but user is never advised of it — normative fail of the advisory clause.
Why it matters
All keyboard and screen-reader users who can become stuck inside a component. In this case (a professional networking site's profile editor), they get stuck and can't reach the control.
How to test
Look for any documentation or on-screen text advising a non-standard exit key (e.g., Ctrl+M): if such a key exists but the user is never told about it, it fails the advisory requirement.
How to fix
Focus must always be able to leave the component using Tab/Shift+Tab or Esc (or a standard method the user is told about).
Outcome
Once corrected, a professional networking site's profile editor lets them keep track of where they are on the page.
Who is affected
All keyboard and screen-reader users who can become stuck inside a component.
Learn more
- Understanding Understanding document (opens in a new tab)
Related scenarios
- Keyboard Focus Stuck Inside an Embedded Plugin or Widget
- Modal Focus Trap With No Escape Key or Close Button
- Widget Where Tab Cycles Internally With No Way Out
- Third-Party Embed That Captures and Never Releases Tab Focus
- Script That Yanks Focus Back Every Time the User Tabs Away
- Rich Text Editor That Captures Tab With No Documented Escape