Resource guide

2.4.11 Focus Not Obscured (Minimum)

When a component receives keyboard focus, it must not be completely hidden by other content such as a sticky header or cookie banner.

By Calling All Minds·Last updated April 2026

2.4.11

Success criterion

AA

Conformance level

Legal standard — required for EAA compliance.

New

Added in WCAG 2.2

What it means

Sticky headers, fixed footers, chat widgets, and cookie banners sit on top of page content and can cover focused elements. If a user tabs to a link or button that is completely hidden behind one of these overlays, they cannot see where focus is and effectively lose control of the keyboard experience.

This new criterion in WCAG 2.2 requires that no focused component is fully obscured. At Level AA, partial obscuring is acceptable as long as some part of the focused element is visible.

In practice

Add scroll padding or margin to account for sticky headers when an element receives focus: scroll-padding-top: 80px (matching your header height) on the html element.

Ensure modal overlays and chat widgets do not cover the focused element.

Test by tabbing through a page with a sticky header and checking that each focused element is at least partially visible.

Common failures

  • Sticky navigation header that covers the focused element when tabbing through page content
  • Cookie consent banner that obscures the first interactive element on the page
  • Fixed chat widget that covers a focused button or form field

The tricky parts

This criterion requires that the focused component is not completely hidden. If half of a focused button is visible beneath a sticky header, that passes at Level AA. The enhanced version (2.4.12, Level AAA) requires the component to be fully visible.

AXS Audit

AXS Audit checks your site against 2.4.11 and flags issues your team can act on straight away. It covers criteria that automated scanners often miss.

Explore AXS Audit