Blog

What Are All 87 WCAG 2.2 Success Criteria?

TestParty
TestParty
December 17, 2025

The Web Content Accessibility Guidelines (WCAG) 2.2 contains exactly 87 success criteria that define web accessibility standards. Released in October 2023, WCAG 2.2 builds upon version 2.1 by adding 9 new criteria while removing one (4.1.1 Parsing), bringing the total from 78 to 87 testable requirements. Understanding this complete WCAG 2.2 success criteria list is essential for legal compliance, as over 4,000 ADA web accessibility lawsuits were filed in 2023 alone.


Key Takeaways

This comprehensive breakdown covers every WCAG 2.2 success criterion organized for practical implementation.

  • WCAG 2.2 contains 87 success criteria organized under 4 principles (POUR) and 13 guidelines
  • Level A has 32 criteria (minimum baseline), Level AA adds 24 criteria (legal standard), and Level AAA adds 31 criteria (enhanced accessibility)
  • 9 new criteria in WCAG 2.2 focus on cognitive accessibility, mobile usability, and improved focus indicators
  • The removed criterion (4.1.1 Parsing) was deprecated because modern browsers handle parsing errors gracefully
  • Most legal requirements and organizational policies target Level AA compliance, covering 56 total criteria

Understanding WCAG 2.2 Structure

Before diving into the complete list, it's important to understand how WCAG 2.2 organizes its success criteria. The guidelines follow a hierarchical structure designed for practical implementation.

The POUR Principles

WCAG organizes all criteria under four foundational principles, often remembered by the acronym POUR:

  1. Perceivable: Information must be presentable in ways users can perceive
  2. Operable: Interface components must be operable by all users
  3. Understandable: Information and UI operation must be understandable
  4. Robust: Content must be robust enough for diverse technologies

Conformance Levels Explained

Each success criterion is assigned one of three conformance levels:

  • Level A: Essential accessibility requirements that must be met
  • Level AA: Standard accessibility requirements for most situations
  • Level AAA: Enhanced accessibility for specialized contexts

Level AA conformance means meeting all Level A AND Level AA criteria—the levels are cumulative.


Principle 1: Perceivable (28 Criteria)

The Perceivable principle ensures users can perceive content through at least one of their senses.

Guideline 1.1: Text Alternatives

CriterionLevelRequirement
1.1.1 Non-text ContentAProvide text alternatives for non-text content

Guideline 1.2: Time-Based Media

CriterionLevelRequirement
1.2.1 Audio-only and Video-only (Prerecorded)AProvide alternatives for prerecorded audio/video
1.2.2 Captions (Prerecorded)AProvide captions for prerecorded audio in video
1.2.3 Audio Description or Media AlternativeAProvide audio description or text alternative
1.2.4 Captions (Live)AAProvide captions for live audio in video
1.2.5 Audio Description (Prerecorded)AAProvide audio description for prerecorded video
1.2.6 Sign Language (Prerecorded)AAAProvide sign language interpretation
1.2.7 Extended Audio DescriptionAAAProvide extended audio description when needed
1.2.8 Media Alternative (Prerecorded)AAAProvide text alternative for prerecorded media
1.2.9 Audio-only (Live)AAAProvide alternative for live audio content

Guideline 1.3: Adaptable

CriterionLevelRequirement
1.3.1 Info and RelationshipsAPreserve structure and relationships in code
1.3.2 Meaningful SequenceAMaintain correct reading sequence in code
1.3.3 Sensory CharacteristicsADon't rely solely on shape, size, location, or sound
1.3.4 OrientationAADon't restrict content to single display orientation
1.3.5 Identify Input PurposeAAIdentify the purpose of input fields
1.3.6 Identify PurposeAAAIdentify the purpose of UI components

Guideline 1.4: Distinguishable

CriterionLevelRequirement
1.4.1 Use of ColorADon't use color as only visual means of conveying info
1.4.2 Audio ControlAProvide mechanism to pause/stop audio over 3 seconds
1.4.3 Contrast (Minimum)AAText contrast ratio of at least 4.5:1
1.4.4 Resize TextAAText resizable up to 200% without loss of function
1.4.5 Images of TextAAUse text instead of images of text when possible
1.4.6 Contrast (Enhanced)AAAText contrast ratio of at least 7:1
1.4.7 Low or No Background AudioAAASpeech recordings have minimal background noise
1.4.8 Visual PresentationAAAText formatting options for readability
1.4.9 Images of Text (No Exception)AAAImages of text only for decoration or essential
1.4.10 ReflowAAContent reflows without horizontal scrolling at 400%
1.4.11 Non-text ContrastAAUI components have 3:1 contrast ratio
1.4.12 Text SpacingAANo loss of content with adjusted text spacing
1.4.13 Content on Hover or FocusAADismissable, hoverable, persistent content

Principle 2: Operable (29 Criteria)

The Operable principle ensures users can interact with all interface components and navigation.

Guideline 2.1: Keyboard Accessible

CriterionLevelRequirement
2.1.1 KeyboardAAll functionality available via keyboard
2.1.2 No Keyboard TrapAKeyboard focus can move away from components
2.1.3 Keyboard (No Exception)AAAAll functionality available via keyboard
2.1.4 Character Key ShortcutsAShortcuts using only letters can be turned off

Guideline 2.2: Enough Time

CriterionLevelRequirement
2.2.1 Timing AdjustableATime limits can be extended or turned off
2.2.2 Pause, Stop, HideAMoving content can be paused, stopped, or hidden
2.2.3 No TimingAAATiming not essential part of activity
2.2.4 InterruptionsAAAInterruptions can be postponed or suppressed
2.2.5 Re-authenticatingAAAData preserved after re-authentication
2.2.6 TimeoutsAAAUsers warned about data loss from inactivity

Guideline 2.3: Seizures and Physical Reactions

CriterionLevelRequirement
2.3.1 Three Flashes or Below ThresholdANo content flashes more than 3 times per second
2.3.2 Three FlashesAAANo content flashes more than 3 times per second
2.3.3 Animation from InteractionsAAAMotion animation can be disabled

Guideline 2.4: Navigable

CriterionLevelRequirement
2.4.1 Bypass BlocksAMechanism to bypass repeated content blocks
2.4.2 Page TitledAPages have descriptive titles
2.4.3 Focus OrderAFocus order preserves meaning and operability
2.4.4 Link Purpose (In Context)ALink purpose determinable from link or context
2.4.5 Multiple WaysAAMultiple ways to locate pages within a site
2.4.6 Headings and LabelsAAHeadings and labels describe topic or purpose
2.4.7 Focus VisibleAAKeyboard focus indicator is visible
2.4.8 LocationAAAInformation about user's location in site
2.4.9 Link Purpose (Link Only)AAALink purpose determinable from link text alone
2.4.10 Section HeadingsAAASection headings used to organize content
2.4.11 Focus Not Obscured (Minimum)AAFocused component not entirely hidden
2.4.12 Focus Not Obscured (Enhanced)AAAFocused component not partially hidden
2.4.13 Focus AppearanceAAAFocus indicators meet size and contrast requirements

Guideline 2.5: Input Modalities

CriterionLevelRequirement
2.5.1 Pointer GesturesAMulti-point gestures have single-point alternatives
2.5.2 Pointer CancellationADown-event not used to trigger functions
2.5.3 Label in NameAVisible label included in accessible name
2.5.4 Motion ActuationAMotion-triggered functions have alternatives
2.5.5 Target Size (Enhanced)AAATouch targets at least 44Ă—44 CSS pixels
2.5.6 Concurrent Input MechanismsAAADon't restrict input to single modality
2.5.7 Dragging MovementsAADragging has single-pointer alternatives
2.5.8 Target Size (Minimum)AATouch targets at least 24Ă—24 CSS pixels

Principle 3: Understandable (17 Criteria)

The Understandable principle ensures users can comprehend content and interface operation.

Guideline 3.1: Readable

CriterionLevelRequirement
3.1.1 Language of PageADefault language can be programmatically determined
3.1.2 Language of PartsAALanguage of passages can be programmatically determined
3.1.3 Unusual WordsAAAMechanism for definitions of unusual words
3.1.4 AbbreviationsAAAMechanism for expansions of abbreviations
3.1.5 Reading LevelAAASupplemental content for complex text
3.1.6 PronunciationAAAMechanism for pronunciation of ambiguous words

Guideline 3.2: Predictable

CriterionLevelRequirement
3.2.1 On FocusANo context change on focus
3.2.2 On InputANo context change on input without warning
3.2.3 Consistent NavigationAANavigation appears in consistent order
3.2.4 Consistent IdentificationAASame functions identified consistently
3.2.5 Change on RequestAAAContext changes only on user request
3.2.6 Consistent HelpAHelp mechanisms appear in consistent location

Guideline 3.3: Input Assistance

CriterionLevelRequirement
3.3.1 Error IdentificationAErrors automatically detected and described
3.3.2 Labels or InstructionsALabels or instructions provided for input
3.3.3 Error SuggestionAASuggestions for fixing errors when known
3.3.4 Error Prevention (Legal, Financial, Data)AASubmissions reversible, checked, or confirmed
3.3.5 HelpAAAContext-sensitive help available
3.3.6 Error Prevention (All)AAAAll submissions reversible, checked, or confirmed
3.3.7 Redundant EntryAAuto-populate previously entered information
3.3.8 Accessible Authentication (Minimum)AANo cognitive function test for authentication
3.3.9 Accessible Authentication (Enhanced)AAANo object or user-supplied content recognition

Principle 4: Robust (13 Criteria)

The Robust principle ensures content works with current and future technologies.

Guideline 4.1: Compatible

CriterionLevelRequirement
4.1.2 Name, Role, ValueAName, role, value available for all UI components
4.1.3 Status MessagesAAStatus messages announced to assistive technologies

Note: Criterion 4.1.1 Parsing was removed in WCAG 2.2 because modern browsers handle parsing errors robustly.


New Criteria in WCAG 2.2

WCAG 2.2 introduced 9 new success criteria focusing on cognitive accessibility and mobile users:

Level A Additions

  1. 2.4.11 Focus Not Obscured (Minimum): Focused elements cannot be completely hidden by other content
  2. 3.2.6 Consistent Help: Help mechanisms appear in consistent locations
  3. 3.3.7 Redundant Entry: Don't require re-entering previously submitted information

Level AA Additions

  1. 2.4.12 Focus Not Obscured (Enhanced): Focused elements cannot be partially hidden
  2. 2.4.13 Focus Appearance: Focus indicators must meet specific size and contrast requirements
  3. 2.5.7 Dragging Movements: Provide alternatives to drag-and-drop functionality
  4. 2.5.8 Target Size (Minimum): Touch targets must be at least 24Ă—24 CSS pixels
  5. 3.3.8 Accessible Authentication (Minimum): Don't require cognitive function tests for login

Level AAA Additions

  1. 3.3.9 Accessible Authentication (Enhanced): Stricter authentication requirements

Level Breakdown Summary

LevelCriteria CountCumulative Total
A3232
AA2456
AAA3187

For Level AA compliance (the most common legal requirement), organizations must meet all 56 Level A and Level AA criteria.


Implementation Priority Guide

When implementing WCAG 2.2 compliance, consider this priority framework:

High Priority (Legal Risk)

  • 1.1.1 Non-text Content (alt text)
  • 1.4.3 Contrast (Minimum)
  • 2.1.1 Keyboard accessibility
  • 2.4.7 Focus Visible
  • 4.1.2 Name, Role, Value

Medium Priority (User Impact)

  • 1.3.1 Info and Relationships
  • 2.4.1 Bypass Blocks
  • 3.3.1 Error Identification
  • 3.3.2 Labels or Instructions

New 2.2 Criteria to Prioritize

  • 2.5.8 Target Size (Minimum)
  • 3.3.7 Redundant Entry
  • 3.3.8 Accessible Authentication

Testing Your Implementation

Automated testing tools can detect approximately 30-40% of WCAG issues. The remaining criteria require manual testing and expert evaluation.

Automated Testing Coverage

  • Color contrast (1.4.3, 1.4.11)
  • Missing alt text (1.1.1)
  • Form labels (3.3.2)
  • Language attributes (3.1.1)

Manual Testing Required

  • Keyboard navigation (2.1.1, 2.1.2)
  • Focus order logic (2.4.3)
  • Content comprehension (3.1.x)
  • Context changes (3.2.x)

Frequently Asked Questions

How many success criteria are in WCAG 2.2?

WCAG 2.2 contains exactly 87 success criteria distributed across three conformance levels: 32 at Level A, 24 at Level AA, and 31 at Level AAA. This represents an increase from WCAG 2.1's 78 criteria, with 9 new additions and 1 removal.

What is the difference between WCAG levels A, AA, and AAA?

Level A represents minimum accessibility requirements, Level AA is the standard for most legal compliance requirements, and Level AAA provides enhanced accessibility for specialized situations. The levels are cumulative, meaning Level AA compliance requires meeting all Level A and AA criteria (56 total).

Which WCAG 2.2 criteria were newly added?

WCAG 2.2 added 9 new criteria: Focus Not Obscured (Minimum and Enhanced), Focus Appearance, Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry, and Accessible Authentication (Minimum and Enhanced). These primarily address cognitive disabilities and mobile accessibility.

Why was criterion 4.1.1 Parsing removed from WCAG 2.2?

The W3C removed 4.1.1 Parsing because modern web browsers and assistive technologies now handle HTML parsing errors gracefully. The original intent—ensuring content is correctly interpreted—is now achieved through browser standards rather than requiring perfectly valid markup.

Do I need to meet all 87 criteria for compliance?

Most legal requirements specify Level AA compliance, which includes 56 criteria (all Level A and AA). Level AAA is typically not required for full conformance but may apply to specific organizational policies or specialized audiences.

How often should I audit against WCAG 2.2?

Organizations should conduct comprehensive accessibility audits annually at minimum, with automated testing integrated into development workflows. Any significant site updates or new feature launches should trigger additional focused testing.



This article was crafted using a cyborg approach—human expertise enhanced by AI to provide accurate, comprehensive accessibility guidance based on the official W3C WCAG 2.2 specification at https://www.w3.org/TR/WCAG22/.

Stay informed

Accessibility insights delivered
straight to your inbox.

Contact Us

Automate the software work for accessibility compliance, end-to-end.

Empowering businesses with seamless digital accessibility solutions—simple, inclusive, effective.

Book a Demo