WCAG Checklist: All 2.2, 2.1 and 2.0 Criteria, Free

Version:

Show levels:

Group byCriteria

50 criteria shown for WCAG 2.1, level A, AA. The full version has 78 criteria.

How to use

Pick a version and levels

Click WCAG 2.0, 2.1 or 2.2, then toggle A, AA and AAA. The default shows A and AA, which most laws require. Use Criteria to show only what is new in 2.1 or 2.2, and Group by to switch to topics.

Test and tick each criterion

Each row shows the number, name, level, version and a short test, such as 1.4.3 needing 4.5:1 text contrast. Tick it when verified, or open Status and note to mark it needs work or not applicable.

Export your progress

Use Copy as Markdown for an issue tracker, CSV for a spreadsheet or PDF for a dated record. Exports list every criterion currently shown with its status and notes. Save progress file keeps a copy.

Why WCAG Compliance Checklist

Every WCAG 2.0, 2.1 and 2.2 success criterion, with a plain-English test.
Filter by version, level or what is new; group by principle or topic.
Four statuses and notes per item, with links to the W3C Understanding pages.
Export Markdown, CSV or PDF, and save progress to a file.

What changed in WCAG 2.2

WCAG 2.2 keeps every WCAG 2.1 criterion except 4.1.1 Parsing and adds the nine below. Six of them are at Level A or AA, so they matter if you target 2.2 AA. 2.5.5 keeps its number and level but is renamed Target Size (Enhanced).

Criterion	Level	What it asks
2.4.11 Focus Not Obscured (Minimum)	AA	A focused element is not completely hidden by sticky headers or banners
2.4.12 Focus Not Obscured (Enhanced)	AAA	No part of the focused element is hidden
2.4.13 Focus Appearance	AAA	The focus indicator is large enough and has 3:1 contrast
2.5.7 Dragging Movements	AA	Anything done by dragging can also be done with single clicks or taps
2.5.8 Target Size (Minimum)	AA	Targets are at least 24 by 24 CSS pixels, or have enough spacing
3.2.6 Consistent Help	A	Help options appear in the same relative order across pages
3.3.7 Redundant Entry	A	Information already entered in a process is not asked for again
3.3.8 Accessible Authentication (Minimum)	AA	Login does not rely on a memory or puzzle test without an alternative
3.3.9 Accessible Authentication (Enhanced)	AAA	As 3.3.8, with fewer exceptions
4.1.1 Parsing	Removed	No longer part of WCAG 2.2

Which laws use which WCAG version

Laws usually name a specific WCAG version and level, and the version often lags behind the latest W3C release. Test against the version your law names. Because newer versions include the older criteria, meeting a newer version usually covers an older requirement too.

Law or standard	Who it applies to	WCAG version
ADA Title II web rule	US state and local governments	WCAG 2.1 Level AA
ADA Title III	US businesses open to the public	No formal rule; WCAG 2.1 AA is commonly used
Section 508	US federal agencies	WCAG 2.0 Level AA
AODA (IASR)	Ontario organizations with 50+ employees and the public sector	WCAG 2.0 Level AA, with two exceptions
European Accessibility Act	Many products and services sold in the EU	EN 301 549, which maps to WCAG 2.1 AA for web content
EU Web Accessibility Directive	EU public sector websites and apps	EN 301 549 (WCAG 2.1 AA)

Common questions

What is the difference between WCAG 2.1 and 2.2?

WCAG 2.2 became a W3C Recommendation in October 2023. It adds nine success criteria about focus visibility, target size, dragging, consistent help, re-entering information and accessible login, and it removes 4.1.1 Parsing. Everything else is the same as 2.1.

How many success criteria are in WCAG 2.2 Level AA?

Conforming to WCAG 2.2 Level AA means meeting 55 criteria: 31 at Level A and 24 at Level AA. For WCAG 2.1 the figure is 50: 30 at Level A and 20 at Level AA. The full 2.2 list, including Level AAA, has 86 criteria.

Which WCAG level is legally required?

Most laws point to Level AA. The ADA Title II rule uses WCAG 2.1 AA, EN 301 549 (used for the European Accessibility Act) maps to WCAG 2.1 AA for web content, and Section 508 and AODA use WCAG 2.0 AA. None of these require Level AAA.

Is WCAG 2.2 backwards compatible with 2.1?

Yes. The W3C designed 2.2 so that content meeting it also meets WCAG 2.1 and 2.0. If a law asks for 2.1 AA, meeting 2.2 AA covers it. Progress you tick in the 2.1 view carries over to the same criteria in the 2.2 view.

Why was 4.1.1 Parsing removed in WCAG 2.2?

Browsers and assistive technology now handle markup errors themselves, so the W3C decided the criterion no longer matched real barriers. Problems it used to catch, such as broken ARIA references, are covered by other criteria like 4.1.2. The checklist shows 4.1.1 only in the WCAG 2.1 view.

Can automated tools check every WCAG criterion?

No. Automated tools can find things like missing alt text, low contrast and unlabeled form fields. They cannot judge whether alt text is accurate, whether captions match the audio or whether focus order makes sense. A checklist like this one is how you track the criteria that need a person.

How long does a WCAG audit take?

There is no fixed time. It depends on how many different page templates, forms and media types the site has, and on the tester's experience. A practical approach is to test each unique template and each key task, such as sign-up or checkout, rather than every single page.

Can I use the WCAG checklist for a WCAG 2.0 audit?

Yes. Click WCAG 2.0 and the list drops the 17 criteria added in 2.1 and the 9 added in 2.2, leaving 61, with 38 at Level A and AA. That is the set Section 508 and AODA point to. Each row shows the version that introduced it.

Is ticking every WCAG checklist box the same as conformance?

No. The checklist records your testing; it does not do the testing. Several criteria, such as keyboard traps or caption quality, only show up when you test with a keyboard and a screen reader.

Where is my WCAG checklist progress stored?

In your browser's local storage on this device, when the browser allows it. Private windows and strict privacy settings can block that, and the checklist tells you when they do. Click Save progress file to download a small JSON file, then Load progress file on any device to carry on.