Goal
Ensure keyboard focus is fully visible (enhanced).
Loading ...
Success Criterion · WCAG 2.4.12
When a user interface component receives keyboard focus, no part of the component is hidden by author-created content.
Goal
Ensure keyboard focus is fully visible (enhanced).
What to do
When an element receives focus, ensure it is not obscured at all by author-created content.
Why it matters
Partially hidden focus still causes confusion, especially for low vision users and users navigating quickly.
Success criterion
Summarized directly from the official Understanding document so teams can quote the requirement accurately.
When a user interface component receives keyboard focus, the component is not hidden due to author-created content.
Intent
Benefits
Why it matters
Summaries drawn from the Understanding document help you socialize impact statements with product stakeholders.
Partially obscured controls can appear ambiguous or look like the wrong element.
Users may misclick/activate wrong controls when the focused control is covered.
This AAA criterion strengthens 2.4.11: the focused component must not be obscured at all by author-created content (sticky headers, overlays, etc.).
Reference: All summaries and highlights originate from Understanding WCAG 2.4.12 and the W3C quick reference.
Examples
Share pass/fail snapshots to coach designers, engineers, QA, and content authors.
Pass
Focused heading/button is fully visible below the sticky header.
Fail
Focused element is partially covered by the sticky header.
Pass
Cookie banner pushes content up so focus targets remain fully visible.
Fail
Cookie banner overlaps page and covers focused controls.
Evidence to keep
Capture artifacts for VPATs, procurement reviews, and regression testing.
Official resources
Keep these links handy when writing acceptance criteria or responding to audits.
Implementation checklist
Testing ideas
Related success criteria