developing Core requirement
No Keyboard Traps
Summary in Plain English
Anything you can enter or activate with the keyboard, you can leave using standard keyboard techniques - unless a non-standard way out is described on the page or earlier in the process.
Why It Matters
A keyboard trap ends the session: the user cannot move on, cannot go back, and often cannot reach the browser's own controls.
Scope: When This Applies
The draft's own conditions, quoted from guidelines/groups/input-operation/keyboard-interface-input/no-keyboard-traps.md.
Except when
- The non-standard keyboard navigation technique is described in the page/view or earlier in the process.
Examples from the Draft
Worked examples the W3C editors wrote into the provision itself, not examples invented here.
- Ensuring that users can exit a modal dialog, menu, or calendar picker after entering it.
- Ensuring that users can deactivate an animation, video, drop down menu, or carousel after activating it.