WCAG 2.2 Explained: The New Success Criteria and How They Apply to PDFs

WCAG 2.2 is the current version of the Web Content Accessibility Guidelines, and it became an official W3C Recommendation in October 2023. It builds on WCAG 2.1 by adding nine new success criteria — most of which target interaction and usability rather than static text. For PDFs, only some of those nine matter much, and which ones depend heavily on whether your document is a static report or an interactive form. This post breaks down WCAG's structure, lists the new 2.2 criteria, and flags the ones that actually apply to PDFs.

For the wider picture of how WCAG fits together with the PDF-specific standard, start with our pillar guide on making a PDF technically accessible with WCAG and PDF/UA.

How WCAG is structured

WCAG is a layered standard. Understanding the layers makes the rest of this much easier to read.

• 4 principles — the top level, known as POUR: Perceivable, Operable, Understandable, Robust.
• 13 guidelines — broad goals under each principle (for example, "Distinguishable" or "Navigable").
• Success criteria (SC) — the testable, specific requirements under each guideline. These are what you actually pass or fail. WCAG 2.2 has 86 of them.
• Conformance levels A, AA, AAA — each success criterion is assigned a level. A is the minimum, AA is the standard most laws require, and AAA is the highest (rarely required wholesale because some AAA criteria cannot be met by all content).

When someone says a document "meets WCAG 2.2 AA," they mean it satisfies every Level A and every Level AA success criterion.

What WCAG 2.2 added

WCAG 2.2 added nine new success criteria over 2.1 and — notably — removed one criterion from 2.1 (4.1.1 Parsing) because it had become obsolete. The new criteria lean heavily toward interaction, input, and cognitive accessibility: making targets easier to hit, reducing memory burden, keeping help in a predictable place, and not trapping focus behind a sticky header.

That focus on interaction is exactly why the relevance to PDFs splits along one line: static document or interactive form? A flat report has no focus, no drag gestures, and no authentication step, so most of the new criteria simply do not apply to it. An interactive PDF — one with form fields, buttons, and navigation — looks much more like a small web application, and several of the new criteria become directly relevant.

The nine new WCAG 2.2 success criteria

Which ones matter most for PDFs

For interactive PDFs (forms, applications, anything users fill in or navigate as a tool), the criteria worth your attention are:

• 2.4.13 Focus Appearance — keyboard users need to see where focus is.
• 2.5.7 Dragging Movements — provide a single-pointer alternative to any drag.
• 2.5.8 Target Size (Minimum) — make clickable controls big enough.
• 3.2.6 Consistent Help — keep help in the same place.
• 3.3.7 Redundant Entry — don't make people retype what they've already entered.
• 3.3.8 Accessible Authentication (Minimum) — provide accessible ways through any login or verification.

For static documents (reports, letters, brochures, archived PDFs), the new 2.2 criteria are mostly not applicable — there is nothing to focus, drag, or authenticate. Your accessibility work on a static PDF is dominated by the older, foundational criteria: tags, headings, reading order, alt text, table structure, contrast, and language. Those are unchanged by 2.2 and remain where most real-world PDF failures live.

How conformance levels map to the law

Across jurisdictions, the practical bar for documents is Level AA — Level A is treated as a floor that is rarely sufficient on its own, and AAA is rarely mandated wholesale.

A few things stand out. First, AA is the consistent benchmark — no major framework requires AAA wholesale. Second, most regulations still reference WCAG 2.1 (or even 2.0), not 2.2. That lag is normal: laws cite a fixed version and update slowly. The Section 508 Revised Standards, for example, still incorporate WCAG 2.0 — see our breakdown of the Section 508 Refresh and Revised Standards.

So why target 2.2 if the law cites 2.1? Because WCAG is largely backwards-compatible: meeting 2.2 AA means you also meet 2.1 AA (the nine additions are extra, not replacements, apart from the one removed criterion). Building to the latest version satisfies the older requirements and future-proofs you against the next regulatory update. (This is general information, not legal advice.)

It is also worth noting that conformance versions interact with the file-level standard. WCAG tells you the content outcomes; PDF/UA tells you how to implement them inside the file, and PDF/UA itself has evolved — compare the editions in PDF/UA-1 vs PDF/UA-2.

Key takeaways

• WCAG is layered: 4 principles → 13 guidelines → 86 success criteria → levels A/AA/AAA, and WCAG 2.2 became a W3C Recommendation in October 2023.
• WCAG 2.2 added 9 new success criteria (and removed the obsolete 4.1.1 Parsing); they focus on interaction, input, and cognitive load.
• The new criteria are most relevant to interactive PDFs (focus appearance, target size, dragging movements, consistent help, redundant entry, accessible authentication) and largely not applicable to static documents.
• For static PDFs, the foundational older criteria — tags, reading order, headings, alt text, tables, contrast, language — still carry the load.
• Level AA is the legal bar across the ADA Title II rule, Section 508, Section 504, EN 301 549, and AODA — and most still cite WCAG 2.1 or 2.0, so building to 2.2 AA keeps you both compliant and ahead.