Marcelo Paiva

All criteriaPresent as slides

A young woman in glasses and a yellow hoodie sits back in a power wheelchair with a headrest, one hand on a keyboard, looking sideways at the screen in front of her.Meant to show: A young woman with a spinal cord injury, who uses a power wheelchair and has limited use of her hands

Success criterion 2.4.11

Focus Not Obscured (Minimum)

Ensures that when a user interface component receives keyboard focus, it is not completely obscured by other content, maintaining its visibility for users.

  • Level AA
  • Principle 2: Operable
  • Guideline 2.4: Navigable
  • New in WCAG 2.2

In a user’s words

“Playing peek-a-boo with focused elements isn't fun. Keep my focus visible!”

Who this helps: Visual Impairments, Motor Impairments

What each role can do

Product manager
Design interfaces to prevent essential elements from being obscured when they receive focus.
Designer
Consider the placement and visibility of interactive elements to ensure they remain visible when focused.
Developer
Implement UI designs where focused elements are not hidden by overlays or other content.
Tester
Test with keyboard navigation to ensure that focused elements are always at least partially visible.

Once it is fixed

“Thanks for keeping my digital path clear! Now I can navigate without guesswork.”

The quotes are written to illustrate the criterion. They are not testimonials from real people. For the official wording, find 2.4.11 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.