Level AAOperableNew in 2.2
2.4.11

Focus Not Obscured (Minimum)

When you Tab to something, a sticky header, footer, or cookie bar must not completely hide it from view.

In plain English

Sticky headers, sticky “add to cart” bars, cookie notices, and chat bubbles all pin themselves over your page. That looks fine with a mouse. But a keyboard user Tabbing down the page can land on a link or field that has just scrolled up and hidden behind the sticky header, so they cannot see where they are.

This rule, new in WCAG 2.2, says the thing you just focused cannot be completely covered. Part of it must stay visible.

Who this is for

  • Keyboard users, who rely on seeing the focused element to know their place.
  • Low-vision users who zoom in, where sticky bars take up even more of the screen.

How to check and fix it yourself

Tab slowly down a long page (a product page or checkout) and watch the focus outline. If it ever disappears behind your sticky header or footer, that fails. The usual one-line fix:

/* Leave room so focused items don't hide under a ~64px sticky header */
:target,
a, button, input, select, textarea {
  scroll-margin-top: 72px;
}

Also make sure cookie banners and chat widgets can be closed, so they are not permanently covering content.

Where we can help

Sticky elements interact with focus in ways that are easy to miss by eye. In an audit we Tab through your real templates and flag every spot where focus hides, with the exact CSS fix. It pairs with other keyboard issues on the common failures list, and it is one of the new checks in WCAG 2.2.

How to meet it

Techniques the W3C accepts as sufficient (summarized). Follow a link for the full method.

Common mistakes

Patterns the W3C lists as failures of this criterion. Avoid these.

Frequently asked questions

What does focus not obscured require?+

Success Criterion 2.4.11 (Level AA, new in WCAG 2.2) says that when a component receives keyboard focus, it must not be entirely hidden by content you added to the page, such as a sticky header, sticky footer, or a cookie banner. At least part of the focused item has to stay visible.

Why does this happen?+

As you Tab down a page, the browser scrolls the focused element into view. But if you have a sticky header pinned to the top, the element can scroll up and end up tucked behind it, so a keyboard user sees the header, not the field they are on.

How do I fix it myself?+

Add CSS scroll-margin-top (roughly the height of your sticky header) to focusable elements, so the browser stops scrolling before they slide under the bar. Making sure cookie banners and chat widgets can be dismissed also helps.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 2.4.11?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit