Skip to main content
WCAGrules
Quick navigation

Fixes

Every technique. Explained.

W3C documents 432 techniques for meeting WCAG 2.2, and not one of them is required. They are worked examples of ways to satisfy a rule, so you take the route that suits your code and leave the rest. The catch is that they are written for standards experts, so we rewrite each one for the person doing the work. A guide tells you what the fix is, how we find the problem in an audit, how it lands on the people it affects, and what a pass looks like beside a fail. For the separate question of how a rule gets tested rather than satisfied, the ACT rules are the other half of the picture. All 432 have a guide here, with none skipped.

The guides use the standard's own vocabulary. The A to Z glossary decodes every term →

432 of 432 techniques

317 of these are enough on their own, 90 are documented ways to break a rule, and 25 are advisory extras. The three technique types explain why one technique can hold two of those labels at once.

HTML52

ARIA26

CSS36

JavaScript23

Common failures90

General166

Plain text3

PDF23

Media (SMIL)8

Server-side5

Not sure which of these your site needs?

That is what the audit answers. Every finding in your report names the rule it breaks, links to the technique that fixes it, and shows the evidence, in the order worth doing.

Order your audit

Go somewhere useful

Find tools, resources and your workspace.

29 destinations