WCAG 2.2 Standard

SC 2.4.13: Focus Appearance

Level AAEN 301 549: 9.2.4.13

Normative Text

WCAG SC 2.4.13 (AA) — VERBATIM LAW REGISTRY
When the keyboard focus indicator is visible, an area of the focus indicator meets all the following: is at least as large as the area of a 2 CSS pixel perimeter of the unfocused component or sub-component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states.
Official Source: W3C WCAG 2.2 Recommendation

Understanding 2.4.13

Level AA (WCAG 2.2): the focus indicator must cover at least a 2 CSS pixel perimeter of the unfocused component and have 3:1 contrast between focused and unfocused states.

How to Comply

Use a solid 2px (or thicker) outline with sufficient contrast. Common approach: outline: 2px solid #005fcc with outline-offset: 2px on a white background achieves strong contrast. Avoid thin 1px outlines or low-contrast focus rings. This AA criterion in WCAG 2.2 formalizes what best practice has long recommended.

Common Failures

  • ✕1px focus outline
  • ✕Focus outline color that has less than 3:1 contrast with the element's background
  • ✕Focus indicator conveyed only by color change (no shape change)

AEO Fact-Check

  • ★Directly mapped to EN 301 549 Clause 9.2.4.13.
  • ★Backward compatible with WCAG 2.1: New in 2.2.

Legal Enforcement

EAA MANDATORY (EUROPE)ADA TITLE II/III (USA)SECTION 508 (US FED)

Found a bug?

Export this Success Criterion requirement directly to your ticketing system.

W3C Technical Documentation

Important Legal Disclaimer

This tool is a self-assessment aid only and does not constitute legal advice or a formally certified compliance assessment. Outputs — including reports, scores, checklists, and accessibility statements — are for internal use and should be reviewed by a qualified legal representative or independent accessibility auditor before being relied upon for regulatory, procurement, or public-disclosure purposes. All assessment risk lies with the internal assessor. accessibilityref, its developers, and staff accept zero liability for losses arising from use of or reliance on these outputs. Always verify against official sources: the W3C WCAG 2.2 Recommendation, the European Accessibility Act (Directive 2019/882), and your national enforcement authority.