- Success Criterion 2.1.2
- Conformance level A
- W3C reference F10
Keyboard Focus Stuck Inside an Embedded Plugin or Widget
2.1.2 — No Keyboard Trap
Scenario
Setting
An email client's compose window
What’s wrong
Keyboard focus can get stuck inside an embedded plugin/format (video player, widget) and the user cannot Tab back out to the rest of the page.
Example
Here's what happens on an email client's compose window: keyboard focus can get stuck inside an embedded plugin/format (video player, widget) and the user cannot Tab back out to the rest of the page.
Why it matters
All keyboard and screen-reader users who can become stuck inside a component. Here, on an email client's compose window, the result is they get stuck and can't reach the control.
How to test
Tab into any embedded plugin/format (PDF viewer, old Flash-style widget): confirm Tab or Shift+Tab can move focus back out to the surrounding page.
How to fix
Ensure focus can Tab out of every embedded format/plugin back to the page.
Outcome
After the fix, the same visitor to an email client's compose window can now reach and operate the control without a mouse.
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)
- Technique Related technique (opens in a new tab)
Related scenarios
- 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
- Autocomplete List That Keeps Recapturing Focus on Every Blur