WCAG 2.4.11 Focus Not Obscured (Minimum)
WCAG 2.4.11 Focus Not Obscured (Minimum) explained: a focused control cannot be fully hidden by a sticky bar. How to test and how to fix it.
Table of contents
WCAG 2.4.11 Focus Not Obscured (Minimum) is a Level AA success criterion, added in WCAG 2.2. This page is part of the WCAG 2.2 success criteria guide. It explains the rule in plain English, who it helps, what passing and failing code look like, and how to test it by hand and with AccessBell, a website accessibility monitoring tool. AccessBell is not an overlay.
What WCAG 2.4.11 Focus Not Obscured (Minimum) requires
When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
That sentence is the heart of the criterion. The exceptions and notes are in the WCAG 2.2 Recommendation and the Understanding document for 2.4.11 Focus Not Obscured (Minimum).
What WCAG 2.4.11 means in plain English
WCAG 2.4.11 Focus Not Obscured (Minimum) is new in WCAG 2.2. Keyboard focus has to leave at least part of the control visible. A sticky header, a cookie bar or a chat bubble that covers the whole focused link or button fails. Covering a corner of it can still pass this minimum. The stricter rule, where no part of the control may be covered, is 2.4.12 Focus Not Obscured (Enhanced), Level AAA.
The W3C notes two cases that are not failures. If the person can move the author content, only the starting position counts. And if the person opened something that covers the control, such as a menu they just activated, it is not a failure when they can reveal the focused item without moving focus forward. Content the site itself pins to the screen is in scope.
Who WCAG 2.4.11 helps
People who tab through a page and sighted people who use speech recognition and need to see the control they are about to activate. A focused link hidden under a promo bar looks as if focus has vanished, which is the same practical problem as a missing focus indicator.
Pass and fail examples
.promo {
position: fixed;
bottom: 0;
left: 0;
right: 0;
height: 96px;
} html {
scroll-padding-top: 5rem;
scroll-padding-bottom: 6rem;
} How to test WCAG 2.4.11
- Tab from the top of the page through the last link. Watch the focused control as it goes under any sticky header, sticky footer, cookie banner or chat launcher.
- If the whole control disappears, the page fails 2.4.11. If a sliver remains visible, it meets this minimum and may still fail 2.4.12.
- Open a disclosure or menu the person asked for. If they can scroll or dismiss it and see the focused item without extra Tab presses, that overlay is allowed.
- Test at 200% zoom as well. Sticky bars cover more of the page when text is larger.
Testing WCAG 2.4.11 with AccessBell
Sticky overlays are hard for automation to score, because the tool has to know which element is author-pinned and whether any pixel of the focused control remains. AccessBell, a website accessibility monitoring tool, will show an axe-core rule when one applies and otherwise leave 2.4.11 for a manual tab through the page. Do not read a silent scan as a pass.
Check your site for this with a free scan of one public page. AccessBell is a website accessibility monitoring tool, not an overlay.
Common failures on Shopify, WordPress, Wix and Squarespace
These are patterns in how the builders work. They are not counts from AccessBell scans. Where a platform hosts the screen, a merchant may not be able to change it, and an unscanned page is not a pass.
Shopify
Announcement bars, sticky add-to-cart bars and cookie apps are the usual covers. Tab a long product description and the footer with the bar present. Theme CSS can add scroll-padding-bottom so focused items clear the bar. The Shopify checker is the automated pass. The store checklist maps 2.4.11 onto a product page and a cart.
WordPress
Fixed headers and consent plugins pin content over the footer links. A theme that uses scroll-padding-top on html often fixes the header. The footer banner needs the same treatment, or a layout that is not position: fixed over the links. Check with the WordPress checker, then tab.
Wix
A sticky header and a chat app are both author-created. The Accessibility Wizard’s limits are listed in the Wix checklist, and it does not tab under a banner for you. Set the header to hide on scroll or add spacing, publish, and tab. Then run the Wix checker.
Squarespace
Announcement bars and fixed promotional blocks sit over the last links in a section. Squarespace’s focus guidance is summarized in the Squarespace checklist. Tab the published page with the bar open. If the focused link vanishes, shorten the bar or stop pinning it.
Level and conformance
Level AA, added in WCAG 2.2. It is not part of WCAG 2.0 or 2.1. A target of WCAG 2.2 Level AA includes it. Partial coverage can pass 2.4.11 and fail 2.4.12, which is Level AAA. The W3C introduction, with the normative sentence, is on What’s New in WCAG 2.2.
Conforming at Level AA means meeting every Level A and Level AA criterion that applies, not only the ones labeled AA. See the WCAG 2.2 conformance requirements. This page explains the technical rule. It is not a legal opinion. Read the disclaimer.
Related WCAG criteria
- 2.4.7 Focus Visible (Level AA, WCAG 2.0)
- 2.4.12 Focus Not Obscured (Enhanced) (Level AAA, WCAG 2.2)
- 2.4.3 Focus Order (Level A, WCAG 2.0)
- 1.4.11 Non-text Contrast (Level AA, WCAG 2.1)
Every criterion is listed in the WCAG 2.2 success criteria guide.
Frequently Asked Questions
What level is WCAG 2.4.11 Focus Not Obscured (Minimum)?
Level AA. It was added in WCAG 2.2. It is not a WCAG 2.1 requirement.
Can a sticky header partly cover a focused button?
Under 2.4.11, yes, as long as some of the focused component stays visible. If any part is hidden, the page fails the AAA criterion 2.4.12 Focus Not Obscured (Enhanced) and can still pass 2.4.11.
Does a cookie banner fail 2.4.11?
It fails when it completely hides the control that has keyboard focus and the person did not open it as the thing they are operating. A banner they can move or dismiss, used in its initial position, is what you test.
Sources
- W3C: Understanding 2.4.11 Focus Not Obscured (Minimum) (opens in a new tab)
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)
This page explains a technical standard and is not legal advice. See our disclaimer.