Operable · Level AA · Introduced in WCAG 2.2
WCAG 2.4.11: Focus Not Obscured (Minimum)
Published by whatisADA / Grow Wild Agency · Updated
What this criterion means
When a component receives keyboard focus, author-created content must not hide it entirely. Sticky headers, banners and overlays can otherwise leave users unsure where keyboard input will act.
A practical example
A sticky consent banner covers the final checkout button when it receives focus. Add enough scrolling clearance or adjust the banner layout so at least part of the focused component remains visible.
How to check it
- Tab through the page with sticky headers, footers, notices and expanded panels in place.
- Check focused components near viewport edges and repeat at zoomed and narrow sizes.
- Where user-opened content obscures focus, verify any applicable mechanism for revealing the component without advancing focus.
What can be missed
The AA minimum prohibits complete hiding; partial coverage still deserves repair and can fail the enhanced criterion. Review WCAG's notes for movable and user-opened content rather than assuming all overlays are exceptions.
Record your test
Use this worksheet to record what you actually checked. Notes stay on this device when you choose Save; they are not sent to us. Avoid personal or confidential information on shared devices.
These are your observations, not automated results or a conformance certificate. A complete evaluation needs appropriate scope, supported technologies, all applicable criteria and relevant page states.
Primary sources and scope
This is independent implementation guidance with original examples. The linked standard contains the full definitions, exceptions and conformance requirements. A criterion or checklist alone does not establish legal applicability or whole-site conformance.