How many success criteria are in WCAG 2.2?

86: 31 at Level A, 24 at Level AA and 31 at Level AAA. That excludes 4.1.1 Parsing, which WCAG 2.2 marks obsolete and removed. Level AA conformance means meeting all 55 Level A and AA criteria.

Does WCAG 2.2 replace WCAG 2.1?

It builds on it. The W3C states that content conforming to WCAG 2.2 also conforms to WCAG 2.0 and 2.1, and that 2.2 does not deprecate or supersede the earlier versions. Rules that name 2.0 or 2.1 still name those versions.

Is 4.1.1 Parsing still required?

Not in WCAG 2.2. The W3C marks it obsolete and removed, because assistive technology no longer parses HTML directly and the problems it addressed are covered by other criteria.

Which WCAG 2.2 criteria can automated tools test?

Some part of 23 of the 55 Level A and AA criteria has an axe-core rule mapped to it. A mapped rule checks one detectable failure of a criterion, not the whole of it — whether alternative text is accurate, focus order is logical or an error message is helpful still takes a person or a behavioral test.

WCAG 2.2 Success Criteria Checklist — Every Level A and AA Criterion

Q: Should I aim for Level AAA?

Not across a whole site. The W3C does not recommend requiring Level AAA as a general policy for entire sites, because some content cannot satisfy every AAA criterion. Aim for AA and meet AAA criteria where the content allows.

What is in the WCAG 2.2 checklist?

WCAG 2.2 has 86 success criteria: 31 at Level A, 24 at Level AA and 31 at Level AAA. Meeting Level AA — the level most accessibility rules and procurement policies point to — means meeting all 55 Level A and AA criteria below. The obsolete 4.1.1 Parsing is not included.

How to use this checklist

Start with Level A. A failure there usually shuts a group of people out entirely rather than slowing them down.
Run automated checks first to clear the detectable failures on every page — see automated scanning.
Then test what the scan cannot decide — every row marked for human or behavioral testing, and the judgment part of every row that has rules.
Test tasks, not just pages. Several criteria, like focus order and status messages, only fail while someone is using the page.

About the automated checks column. “axe-core rules exist” means at least one axe-core rule is mapped to that criterion (23 of 55 here). It does not mean the criterion can be fully tested automatically: a rule checks one detectable failure, such as a missing alt attribute, not whether the alternative text is meaningful. A clean result is never proof a criterion is met. For why, read why sites pass axe-core but fail real screen reader users.

1. Perceivable

1.1 Text Alternatives

Guideline 1.1 Text Alternatives: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
1.1.1Non-text Content	A	Every image, icon and other non-text element has a text alternative that serves the same purpose, or is marked as decorative.	axe-core rules exist — partial

1.2 Time-based Media

Guideline 1.2 Time-based Media: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
1.2.1Audio-only and Video-only (Prerecorded)	A	Prerecorded audio-only content has a transcript, and prerecorded video-only content has a transcript or an audio track.	axe-core rules exist — partial
1.2.2Captions (Prerecorded)	A	Prerecorded video with sound has synchronized captions.	axe-core rules exist — partial
1.2.3Audio Description or Media Alternative (Prerecorded)	A	Prerecorded video has audio description or a full text alternative.	Needs human or behavioral testing
1.2.4Captions (Live)	AA	Live video with sound has captions.	Needs human or behavioral testing
1.2.5Audio Description (Prerecorded)	AA	Prerecorded video has audio description of important visual information.	Needs human or behavioral testing

1.3 Adaptable

Guideline 1.3 Adaptable: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
1.3.1Info and Relationships	A	Structure and relationships shown visually — headings, lists, tables, labels — are also in the markup or stated in text.	axe-core rules exist — partial
1.3.2Meaningful Sequence	A	When the order of content affects its meaning, the reading order in the code matches it.	Needs human or behavioral testing
1.3.3Sensory Characteristics	A	Instructions do not rely only on shape, color, size, position, orientation or sound.	Needs human or behavioral testing
1.3.4Orientation	AA	Content works in both portrait and landscape unless a specific orientation is essential.	axe-core rules exist — partial
1.3.5Identify Input Purpose	AA	Form fields that collect information about the user identify their purpose in code, for example with autocomplete.	axe-core rules exist — partial

1.4 Distinguishable

Guideline 1.4 Distinguishable: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
1.4.1Use of Color	A	Color is not the only way information, actions or state are shown.	axe-core rules exist — partial
1.4.2Audio Control	A	Audio that plays automatically for more than 3 seconds can be paused, stopped or turned down separately.	axe-core rules exist — partial
1.4.3Contrast (Minimum)	AA	Text has a contrast ratio of at least 4.5:1 against its background, or 3:1 for large text.	axe-core rules exist — partial
1.4.4Resize Text	AA	Text can be resized up to 200% without losing content or functionality.	axe-core rules exist — partial
1.4.5Images of Text	AA	Real text is used instead of images of text, except where the presentation is essential or customizable.	Needs human or behavioral testing
1.4.10Reflow	AA	Content reflows to a 320 CSS pixel width without scrolling in two directions.	Needs human or behavioral testing
1.4.11Non-text Contrast	AA	Controls, their states and meaningful graphics have at least 3:1 contrast against adjacent colors.	Needs human or behavioral testing
1.4.12Text Spacing	AA	No content or functionality is lost when users increase line, paragraph, letter and word spacing.	axe-core rules exist — partial
1.4.13Content on Hover or Focus	AA	Content that appears on hover or focus can be dismissed, can be hovered itself, and stays until dismissed.	Needs human or behavioral testing

2. Operable

2.1 Keyboard Accessible

Guideline 2.1 Keyboard Accessible: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
2.1.1Keyboard	A	Everything can be operated with a keyboard alone.	axe-core rules exist — partial
2.1.2No Keyboard Trap	A	Keyboard focus can always be moved away from any component using the keyboard.	Needs human or behavioral testing
2.1.4Character Key Shortcuts	A	Single-character keyboard shortcuts can be turned off, remapped, or only work when their component has focus.	Needs human or behavioral testing

2.2 Enough Time

Guideline 2.2 Enough Time: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
2.2.1Timing Adjustable	A	Time limits can be turned off, adjusted or extended, with narrow exceptions.	axe-core rules exist — partial
2.2.2Pause, Stop, Hide	A	Moving, blinking, scrolling or auto-updating content can be paused, stopped or hidden.	axe-core rules exist — partial

2.3 Seizures and Physical Reactions

Guideline 2.3 Seizures and Physical Reactions: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
2.3.1Three Flashes or Below Threshold	A	Nothing flashes more than three times in any one second, unless the flash is below the general and red flash thresholds.	Needs human or behavioral testing

2.4 Navigable

Guideline 2.4 Navigable: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
2.4.1Bypass Blocks	A	A mechanism, such as a skip link or landmarks, lets users bypass blocks repeated across pages.	axe-core rules exist — partial
2.4.2Page Titled	A	Each page has a title that describes its topic or purpose.	axe-core rules exist — partial
2.4.3Focus Order	A	Focus moves through the page in an order that preserves meaning and operability.	Needs human or behavioral testing
2.4.4Link Purpose (In Context)	A	The purpose of each link is clear from its text or its programmatically determined context.	axe-core rules exist — partial
2.4.5Multiple Ways	AA	There is more than one way to find a page within the site, except for steps in a process.	Needs human or behavioral testing
2.4.6Headings and Labels	AA	Headings and labels describe their topic or purpose.	Needs human or behavioral testing
2.4.7Focus Visible	AA	The keyboard focus indicator is visible.	Needs human or behavioral testing
2.4.11Focus Not Obscured (Minimum)New in 2.2	AA	A focused component is not entirely hidden by other author-created content, such as a sticky header.	Needs human or behavioral testing

2.5 Input Modalities

Guideline 2.5 Input Modalities: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
2.5.1Pointer Gestures	A	Anything operated with multipoint or path-based gestures can also be operated with a single pointer.	Needs human or behavioral testing
2.5.2Pointer Cancellation	A	Actions triggered by a single pointer can be aborted or undone rather than firing on the down-event.	Needs human or behavioral testing
2.5.3Label in Name	A	A control's accessible name contains the text shown on its visible label.	axe-core rules exist — partial
2.5.4Motion Actuation	A	Functions triggered by device or user motion can also be operated with controls, and motion response can be disabled.	Needs human or behavioral testing
2.5.7Dragging MovementsNew in 2.2	AA	Anything that uses dragging can also be done with a single pointer without dragging.	Needs human or behavioral testing
2.5.8Target Size (Minimum)New in 2.2	AA	Pointer targets are at least 24 by 24 CSS pixels, or have enough spacing, with listed exceptions.	axe-core rules exist — partial

3. Understandable

3.1 Readable

Guideline 3.1 Readable: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
3.1.1Language of Page	A	The default language of each page is set in code.	axe-core rules exist — partial
3.1.2Language of Parts	AA	The language of passages in a different language is set in code.	axe-core rules exist — partial

3.2 Predictable

Guideline 3.2 Predictable: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
3.2.1On Focus	A	Moving focus to a component does not trigger a change of context.	Needs human or behavioral testing
3.2.2On Input	A	Changing a setting does not automatically change context unless users are warned first.	Needs human or behavioral testing
3.2.3Consistent Navigation	AA	Navigation repeated across pages appears in the same relative order.	Needs human or behavioral testing
3.2.4Consistent Identification	AA	Components with the same function are identified consistently across pages.	Needs human or behavioral testing
3.2.6Consistent HelpNew in 2.2	A	Help mechanisms repeated across pages appear in the same relative order.	Needs human or behavioral testing

3.3 Input Assistance

Guideline 3.3 Input Assistance: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
3.3.1Error Identification	A	When an input error is detected, the field in error is identified and the error is described in text.	Needs human or behavioral testing
3.3.2Labels or Instructions	A	Labels or instructions are provided when content requires user input.	axe-core rules exist — partial
3.3.3Error Suggestion	AA	When an input error is detected and a correction is known, the suggestion is offered.	Needs human or behavioral testing
3.3.4Error Prevention (Legal, Financial, Data)	AA	Legal, financial and data-changing submissions can be reversed, checked, or confirmed before they are final.	Needs human or behavioral testing
3.3.7Redundant EntryNew in 2.2	A	Information already entered in a process is auto-filled or selectable rather than required again.	Needs human or behavioral testing
3.3.8Accessible Authentication (Minimum)New in 2.2	AA	Signing in does not require a cognitive function test, such as remembering or transcribing, without an alternative or assistance.	Needs human or behavioral testing

4. Robust

4.1 Compatible

Guideline 4.1 Compatible: Level A and AA success criteria
Success criterion	Level	What it requires	Automated checks
4.1.2Name, Role, Value	A	Every control exposes its name and role, and its states and values can be read and set by assistive technology.	axe-core rules exist — partial
4.1.3Status Messages	AA	Status messages are announced by assistive technology without moving focus.	Needs human or behavioral testing

What is new in WCAG 2.2

6 of the criteria above arrived with WCAG 2.2: 2.4.11 Focus Not Obscured (Minimum), 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 (Minimum). 2.2 also removed 4.1.1 Parsing. The WCAG 2.2 guide explains each addition, including the AAA ones.

What Level AA means for regulations

WCAG is a technical standard, not a law. Accessibility rules point to it — often to Level AA, and not always to 2.2: some still name 2.0 or 2.1. The W3C states that content conforming to 2.2 also conforms to 2.0 and 2.1 (W3C, 2024). Meeting a criterion is not the same as legal compliance, which depends on the rule that applies to you. See which WCAG version the ADA, Section 508 and the EAA reference.

Level AAA criteria

The 31 Level AAA criteria are a higher bar for specific content. The W3C does not recommend requiring AAA conformance as a general policy for entire sites, because some content cannot satisfy every AAA criterion.

WCAG 2.2 Level AAA success criteria by guideline
Criterion	Name	Guideline
1.2.6	Sign Language (Prerecorded)	1.2 Time-based Media
1.2.7	Extended Audio Description (Prerecorded)	1.2 Time-based Media
1.2.8	Media Alternative (Prerecorded)	1.2 Time-based Media
1.2.9	Audio-only (Live)	1.2 Time-based Media
1.3.6	Identify Purpose	1.3 Adaptable
1.4.6	Contrast (Enhanced)	1.4 Distinguishable
1.4.7	Low or No Background Audio	1.4 Distinguishable
1.4.8	Visual Presentation	1.4 Distinguishable
1.4.9	Images of Text (No Exception)	1.4 Distinguishable
2.1.3	Keyboard (No Exception)	2.1 Keyboard Accessible
2.2.3	No Timing	2.2 Enough Time
2.2.4	Interruptions	2.2 Enough Time
2.2.5	Re-authenticating	2.2 Enough Time
2.2.6	Timeouts	2.2 Enough Time
2.3.2	Three Flashes	2.3 Seizures and Physical Reactions
2.3.3	Animation from Interactions	2.3 Seizures and Physical Reactions
2.4.8	Location	2.4 Navigable
2.4.9	Link Purpose (Link Only)	2.4 Navigable
2.4.10	Section Headings	2.4 Navigable
2.4.12	Focus Not Obscured (Enhanced)New in 2.2	2.4 Navigable
2.4.13	Focus AppearanceNew in 2.2	2.4 Navigable
2.5.5	Target Size (Enhanced)	2.5 Input Modalities
2.5.6	Concurrent Input Mechanisms	2.5 Input Modalities
3.1.3	Unusual Words	3.1 Readable
3.1.4	Abbreviations	3.1 Readable
3.1.5	Reading Level	3.1 Readable
3.1.6	Pronunciation	3.1 Readable
3.2.5	Change on Request	3.2 Predictable
3.3.5	Help	3.3 Input Assistance
3.3.6	Error Prevention (All)	3.3 Input Assistance
3.3.9	Accessible Authentication (Enhanced)New in 2.2	3.3 Input Assistance

The requirement column is a plain-language summary. The normative text — including every exception — is the W3C Recommendation, and it is what to rely on when a criterion is in dispute.

Sources

Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab). W3C, December 12, 2024. W3C Recommendation; the normative text of every criterion listed here.

WCAG 2.2 success criteria checklist