WCAG 2.2 Fix Guides

WCAG 2.2 has dozens of success criteria. These guides break each one down into what it means, why it matters, and exactly how to fix it — with real code examples.

Perceivable

1.1.1 A

Non-text Content

WCAG 1.1.1 requires that all non-text content presented to the user has a text alternative that serves the equivalent pu...
1.3.1 A

Info and Relationships

WCAG 1.3.1 requires that information, structure, and relationships conveyed through visual presentation are also availab...
1.4.3 AA

Contrast (Minimum)

WCAG 1.4.3 requires that text and images of text have a contrast ratio of at least 4.5:1 against their background, with ...
1.4.11 AA

Non-text Contrast

WCAG 1.4.11 requires that user interface components and graphical objects essential to understanding the content have a ...

Operable

2.1.1 A

Keyboard

WCAG 2.1.1 requires that all functionality of the content is operable through a keyboard interface without requiring spe...
2.4.4 A

Link Purpose (In Context)

WCAG 2.4.4 requires that the purpose of each link can be determined from the link text alone, or from the link text toge...
2.4.6 AA

Headings and Labels

WCAG 2.4.6 requires that headings and labels describe the topic or purpose of the content they introduce. This does not ...
2.5.3 A

Label in Name

WCAG 2.5.3 requires that for user interface components with visible text labels, the accessible name contains the visibl...

Understandable

3.3.2 A

Labels or Instructions

WCAG 3.3.2 requires that labels or instructions are provided when content requires user input. Every form control that e...

Robust

4.1.2 A

Name, Role, Value

WCAG 4.1.2 requires that for all user interface components, the name and role can be programmatically determined, states...