💬 Plain English & Scope
🧪 Testing & Methods
📊 W3C Status & Draft Notes
⚖️ WCAG 2.2 Comparison
📜 W3C Official Text
Summary in Plain English A user can move focus into an area such as a modal or popup and get back to the rest of the content in a small number of steps.
Why It Matters Escaping an overlay by tabbing through everything inside it is slow enough that many keyboard users give up on the task.
0
Test Procedure from the W3C Draft
Quoted from the provision's informative document,
informative/guidelines/interactive-components/navigating-content/focus-retained.md .
It is the group's own procedure, not an editorial testing guide.
Procedure
For each situation where the keyboard focus is removed:
Check that the keyboard focus moves to its previous location, or, if that no longer exists, to another meaningful location.
Expected results
W3C Working Group Status W3C Maturity Status: developing
Track / Group: interactive-components
The draft records no open editors' notes on this provision.
W3C Threads on This Provision 2 GitHub threads carrying 3 comments,
fetched from w3c/wcag3 by the
tracker. Titles, numbers and states are the threads' own.
Nobody has read these threads and written up the positions yet, so
only the threads themselves are listed.
WCAG 2.2 Criteria That Map Here
From this site's reviewed WCAG 2.2 → WCAG 3 map. The map is
an interpretation, not a W3C mapping: W3C has not published one yet.
No mapping recorded. No WCAG 2.2 criterion in
this site's map is recorded as a predecessor of this provision.