
Success criterion 2.4.12
Focus Not Obscured (Enhanced)
When a user interface component receives keyboard focus, no part of it is obscured by other content, ensuring complete visibility of the focused element.
- Level AAA
- Principle 2: Operable
- Guideline 2.4: Navigable
- New in WCAG 2.2
In a user’s words
“One leaf held close is enough to hide the sun. One banner is enough to hide my focus.”
What each role can do
- Product manager
- Aim for the highest level of clarity by ensuring that no focused component is partially or fully obscured.
- Designer
- Design the user experience to keep the focus area completely unobscured, regardless of the site's dynamic content or overlays.
- Developer
- Develop web pages so that focused elements are always fully visible and not covered by any author-created content.
- Tester
- Conduct thorough accessibility testing to ensure that when elements receive focus, they are entirely visible.
Once it is fixed
“Not a leaf in the way now. I can see my whole focus, edge to edge. Thank you!”
Share this with your team
The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 2.4.12 in the W3C quick reference for WCAG 2.2 (opens in a new tab).
Or press ←the left arrow and →the right arrow.