WCAG 2.2 AA Checklist: All 55 Criteria You Can Test Yourself [Free Download]

Last updated: October 17, 2026

This WCAG 2.2 checklist puts all 55 Level A and AA success criteria on one page as checkboxes — a WCAG 2.2 AA checklist you actually run, not another explainer of what the standard means. Every row names the criterion, its level, and a one-sentence test you can perform yourself, organized under WCAG's four principles: Perceivable, Operable, Understandable, and Robust.

Key numbers: WCAG 2.2 numbers 87 success criteria, but 4.1.1 Parsing is obsolete, leaving 86 in force — 55 at Levels A and AA (W3C). In 2026, 95.9% of the top one million home pages carried detectable WCAG failures, averaging 56.1 per page (WebAIM Million 2026). Automated tools reliably decide about 9 of the 55 A/AA criteria and catch 60–70% of issue volume; the rest needs manual testing (TestParty data, 100+ brands). TestParty has remediated 35 million-plus issues as of August 2026, spanning all 55 criteria below.

How do you use this checklist?

For what each criterion means and why regulators require it, see our WCAG 2.2 AA pillar guide — this page is the test-yourself companion. Test one instance of every key template — home, collection, product, cart, checkout, account, search — rather than every URL.

Run a scanner first: tools reliably decide about 9 of the 55 criteria outright, catching 60–70% of issue volume in minutes. Then work every remaining checkbox by hand — keyboard, screen reader, 200% zoom — since the other 30% is judgment a machine can't make. TestParty runs this sequence daily via automated scans plus monthly expert audits, since theme updates reopen closed criteria. A spreadsheet version of these 55 rows is also available as a free download.

Perceivable: does every visitor perceive your content?

Perceivable criteria test whether information and interface elements can be perceived through sight, sound, or another sense. Twenty of the 55 A/AA criteria live here, numbered 1.x.

Operable: can every control actually be operated?

Operable criteria test whether every control can be operated — by keyboard, by pointer, or without triggering seizures or timing pressure. Twenty of the 55 A/AA criteria live here, including three new WCAG 2.2 additions.

Understandable: is content and behavior predictable?

Understandable criteria test whether content and interface behavior are predictable, and whether errors are recoverable. Thirteen of the 55 A/AA criteria live here, including three more new WCAG 2.2 additions.

Robust: does it work with assistive technology?

Robust criteria test whether content works reliably across current and future assistive technology, mostly through correct markup. Only 2 of the 55 A/AA criteria remain here — 4.1.1 Parsing was declared obsolete when WCAG 2.2 published.

4.1.1 Parsing is skipped on purpose: modern browsers now resolve HTML parsing errors identically, so the W3C removed it as redundant. A scanner still flagging 4.1.1 is running an outdated rule set.

How do you check forms specifically?

Forms fail more often than any other component because a missing label or blocked autocomplete field is invisible on screen but load-bearing for screen readers. Seven criteria decide almost every form failure — run them on every field, then again on checkout.

In TestParty's audits of Shopify Plus checkouts, shipping-and-payment fails more of these checks than any template: a promo-code field blocking paste breaks 3.3.8, and a "card declined" message that never reaches a live region breaks 4.1.3. See the Shopify WCAG 2.2 mapping for cart and checkout specifics.

What tools run this checklist for you?

WAVE, Lighthouse, and axe automate the machine-decidable slice — about 9 of 55 criteria outright — largely why automated tools catch 60–70% of issue volume. None finishes the checklist alone; see which WCAG criteria a scanner can and can't test.

WAVE overlays flags on the rendered page but checks one URL at a time and won't walk checkout for you. Lighthouse runs inside Chrome DevTools and CI, scoring 0–100 against a subset of rules — a regression gate, not a conformance test. axe-core is the open-source engine under many other scanners, and what most teams wire into CI for automated WCAG testing.

TestParty's thresholds are Lighthouse 90+, WAVE errors under 5, axe violations under 3 — a regression floor, not a conformance claim. A perfect score still leaves half this checklist untested. Full methodology: our WCAG audit guide.

Frequently Asked Questions

How many criteria are in the WCAG 2.2 AA checklist? 55 total — 31 at Level A and 24 at AA. The numbered list runs to 87, but 4.1.1 Parsing was declared obsolete, leaving 86 in force. WCAG 2.1 had only 50 criteria at A and AA.

Does passing every checkbox make my site conformant? Not on its own. A conformance claim requires testing every applicable criterion across full pages and complete processes, per the W3C's conformance requirements. This checklist catches real failures fast; a formal claim is a separate, documented statement.

What are the six new criteria in WCAG 2.2? 2.4.11 Focus Not Obscured, 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent Help, 3.3.7 Redundant Entry, and 3.3.8 Accessible Authentication. Four need a human walking an actual flow; only 2.5.8 is comfortably automated.

Why doesn't this checklist include 4.1.1 Parsing? Because it no longer exists. The W3C declared it obsolete when WCAG 2.2 published, since modern browsers now resolve HTML parsing ambiguities identically. The numbered list still runs to 87, but only 86 criteria — 55 at A and AA — are in force.

Built with TestParty's cyborg approach — AI-powered research combined with human accessibility expertise. This article contains TestParty's editorial analysis based on publicly available information. We're an accessibility vendor with opinions informed by working with 100+ brands, and we encourage readers to do their own due diligence when evaluating any solution.