Guides WCAG 2.2

WCAG 2.2 — the current standard

The current standard reala11y targets: +9 criteria, 4.1.1 Parsing removed.

Version
2.2
Year
2023
Status
W3C Recommendation
Criteria
86 testable (87 numbered)
reala11y WCAG · GUIDE 2.2 Web Content Accessibility Guidelines 2023 · W3C Recommendation

What WCAG 2.2 is

WCAG 2.2 is the current W3C Recommendation — the international reference for making web content usable by people with disabilities. It is organised as testable success criteria grouped under four principles, each rated A, AA, or AAA. Most laws and procurement standards target Level AA, which is the level reala11y is built around.

FactDetail
StatusW3C Recommendation
Date5 October 2023 (errata revision Dec 2024; requirements unchanged)
New criteria9 added since WCAG 2.1
Removed4.1.1 Parsing (marked obsolete)
Success criteria87 numbered; 86 testable after the 4.1.1 removal

Automated tools, including reala11y, can detect a portion of these criteria (industry analyses put automated coverage at roughly 30–40% of WCAG criteria); the remainder require manual review by a person.

The four principles

Content must be Perceivable, Operable, Understandable, and Robust (POUR). Under each principle sit guidelines, and under each guideline sit the testable success criteria.

Success criteria by guideline

Every Level A and AA criterion is below with a plain-language explanation. Criteria new in 2.2 are marked. Level AAA criteria are listed by name.

Perceivable

SCNameLevelPlain language
1.1.1Non-text ContentAText alternative for images, icons, charts; decorative items marked to ignore.
1.2.1Audio-only / Video-only (Prerecorded)ATranscript for audio-only; description/text for silent video.
1.2.2Captions (Prerecorded)ASynchronized captions for prerecorded video with sound.
1.2.3Audio Description or Media AlternativeADescribed track or full text alternative.
1.2.4Captions (Live)AAReal-time captions for live audio.
1.2.5Audio Description (Prerecorded)AANarration of key visuals during dialogue pauses.
1.3.1Info and RelationshipsAVisual structure also available programmatically.
1.3.2Meaningful SequenceACorrect reading order is programmatic.
1.3.3Sensory CharacteristicsANot by shape, size, or location alone.
1.3.4OrientationAANot locked to portrait/landscape unless essential.
1.3.5Identify Input PurposeAACommon fields declare their purpose for autofill.
1.4.1Use of ColorAColor is not the only means of conveying info.
1.4.2Audio ControlAAuto-playing audio can be paused or muted.
1.4.3Contrast (Minimum)AAText contrast ≥ 4.5:1 (3:1 large).
1.4.4Resize TextAAText resizes to 200% without loss.
1.4.5Images of TextAAPrefer real text over images of text.
1.4.10ReflowAASingle-column reflow at 320px / 400% zoom.
1.4.11Non-text ContrastAAUI components and graphics ≥ 3:1.
1.4.12Text SpacingAANo loss when users adjust spacing.
1.4.13Content on Hover or FocusAAHover/focus content is dismissable, hoverable, persistent.

AAA: 1.2.6–1.2.9, 1.3.6, 1.4.6–1.4.9.

Operable

SCNameLevelPlain language
2.1.1KeyboardAAll functionality works from a keyboard.
2.1.2No Keyboard TrapAFocus can always move away by keyboard.
2.1.4Character Key ShortcutsASingle-key shortcuts can be turned off/remapped.
2.2.1Timing AdjustableATime limits can be turned off, adjusted, extended.
2.2.2Pause, Stop, HideAMoving/auto-updating content can be paused.
2.3.1Three Flashes or Below ThresholdANo flashing above the threshold.
2.4.1Bypass BlocksASkip link / landmarks bypass repeated blocks.
2.4.2Page TitledADescriptive page title.
2.4.3Focus OrderAFocus order preserves meaning.
2.4.4Link Purpose (In Context)ALink purpose clear from text or context.
2.4.5Multiple WaysAAMore than one way to find a page.
2.4.6Headings and LabelsAADescriptive headings and labels.
2.4.7Focus VisibleAAVisible keyboard focus indicator.
2.4.11Focus Not Obscured (Minimum)AANew in 2.2. A focused element is not entirely hidden by sticky headers/banners.
2.5.1Pointer GesturesAMultipoint/path gestures have a single-pointer alternative.
2.5.2Pointer CancellationASingle-pointer actions can be aborted or undone.
2.5.3Label in NameAAccessible name includes the visible label.
2.5.4Motion ActuationAMotion-operated functions have a UI control.
2.5.7Dragging MovementsAANew in 2.2. Drag actions have a single-pointer alternative (no dragging required).
2.5.8Target Size (Minimum)AANew in 2.2. Pointer targets are at least 24×24 CSS px, or adequately spaced.

AAA: 2.1.3, 2.2.3–2.2.6, 2.3.2, 2.3.3, 2.4.8–2.4.10, 2.4.12 Focus Not Obscured (Enhanced, new in 2.2), 2.4.13 Focus Appearance (new in 2.2), 2.5.5, 2.5.6.

Understandable

SCNameLevelPlain language
3.1.1Language of PageAPage language set in markup.
3.1.2Language of PartsAAForeign-language passages marked.
3.2.1On FocusAFocus does not cause unexpected context change.
3.2.2On InputAInput does not cause surprise context change.
3.2.3Consistent NavigationAARepeated nav keeps order.
3.2.4Consistent IdentificationAASame-function components labelled consistently.
3.2.6Consistent HelpANew in 2.2. Help mechanisms appear in a consistent relative location across pages.
3.3.1Error IdentificationAErrors identified in text.
3.3.2Labels or InstructionsAInputs have labels/instructions.
3.3.3Error SuggestionAAKnown fixes are suggested.
3.3.4Error Prevention (Legal, Financial, Data)AAImportant submissions reversible/checked/confirmed.
3.3.7Redundant EntryANew in 2.2. Don’t make users re-enter info already given in the same process.
3.3.8Accessible Authentication (Minimum)AANew in 2.2. Login must not require a cognitive test (memorising, puzzles) without an alternative.

AAA: 3.1.3–3.1.6, 3.2.5, 3.3.5, 3.3.6, 3.3.9 Accessible Authentication (Enhanced, new in 2.2).

Robust

SCNameLevelPlain language
4.1.1ParsingRemoved/obsolete in 2.2 — see below.
4.1.2Name, Role, ValueAComponents expose name, role, state, value (the core of ARIA).
4.1.3Status MessagesAAStatus messages reach assistive tech without moving focus.

What’s new in WCAG 2.2

WCAG 2.2 is backward-compatible with 2.1 (except the removed 4.1.1). It adds 9 success criteria:

SCNameLevel
2.4.11Focus Not Obscured (Minimum)AA
2.4.12Focus Not Obscured (Enhanced)AAA
2.4.13Focus AppearanceAAA
2.5.7Dragging MovementsAA
2.5.8Target Size (Minimum)AA
3.2.6Consistent HelpA
3.3.7Redundant EntryA
3.3.8Accessible Authentication (Minimum)AA
3.3.9Accessible Authentication (Enhanced)AAA

Why 4.1.1 Parsing was removed. It originally required valid markup (no duplicate IDs, correct nesting) because early assistive tech parsed HTML directly. Modern browsers build the accessibility tree from a robust, error-correcting parser, so those specific failures no longer cause accessibility problems — any real impact is covered by 1.3.1 and 4.1.2. Duplicate IDs are still worth flagging as a code-quality issue.

How reala11y maps to WCAG 2.2

reala11y ships 22 scanner rules; several criteria are covered by more than one rule. Automated detection covers an estimated 30–40% of WCAG criteria — the rest needs human review.

reala11y rule(s)WCAG 2.2 SC
R0013.1.1 Language of Page
R002, R0141.1.1 Non-text Content
R0031.4.3 Contrast (Minimum)
R004, R013, R018, R020, R0211.3.1 Info and Relationships
R0052.4.1 Bypass Blocks
R0062.4.7 Focus Visible
R0073.3.2 Labels or Instructions
R008, R009, R0174.1.2 Name, Role, Value
R0104.1.1 (informational, since 4.1.1 was removed in 2.2)
R0112.5.8 Target Size (Minimum) — new in WCAG 2.2
R012, R0222.4.4 Link Purpose (In Context)
R0152.4.3 Focus Order
R0161.4.4 Resize Text
R0191.2.2 Captions (Prerecorded)

Highlight: reala11y rule R011 directly addresses 2.5.8 Target Size (Minimum) — one of the nine criteria new in WCAG 2.2 — flagging interactive targets smaller than 24×24 CSS px.

reala11y helps your site move toward WCAG 2.2 AA conformance by identifying common code-level issues and offering safe, automated remediation where possible. It pairs automated scanning with manual review — it does not certify conformance or guarantee freedom from legal claims.

Further reading