Marcelo Paiva

All criteriaPresent as slides

A man with glasses and a grey beard holds a red maple leaf up beside his face, with a small, knowing smile.Meant to show: A man with low vision who navigates by keyboard

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.”

Who this helps: Visual Impairments, Motor Impairments

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!”

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.

A success criterion

This is one page of a phrase book. It takes one success criterion and tells it from the side of the person it helps.

From top to bottom

  1. At the top, the site header: my name, which goes home, then links to Writing, Work, Signal, Tools and Resume, then Settings, where you choose the drawings, light or dark, and movement.
  2. Links back to all the criteria, and to present this one as slides.
  3. A drawing, the criterion’s number and name, what it requires in one sentence, and its level.
  4. In a user’s words: a quote from the person who meets the barrier.
  5. What each role can do: one task each for the product manager, the designer, the developer and the tester.
  6. Once it is fixed: the same person again.
  7. Share this with your team: post to LinkedIn, download the slides as a PDF, or copy a link.
  8. Some criteria then have a t-shirt to order.
  9. Links to the previous and next criterion. The left and right arrow keys go there too.
  10. At the bottom, the footer: a note on how this site is built, links to Illustrations, Pens, Concepts and Accessibility, this Describe this page button, then GitHub, LinkedIn and email.

What you can do here

Learn what this criterion asks, and what your part of the fix is.

Also here

The quotes are written to illustrate the criterion. They are not from real people.