WCAG 2.2 PDF Accessibility: The Complete Guide
The Web Content Accessibility Guidelines (WCAG) 2.2 define the technical standard for digital accessibility worldwide. Published by the W3C in October 2023, WCAG 2.2 is now the benchmark for ADA compliance, Section 508, and the European Accessibility Act. This guide covers what WCAG 2.2 means specifically for PDF documents.
WCAG 2.2 Status
According to the W3C Web Accessibility Initiative, WCAG 2.2 was published as a W3C Recommendation on October 5, 2023, and is now an ISO standard (ISO/IEC 40500:2025). It contains 86 success criteria—77 from WCAG 2.1 plus 9 new criteria.
The Four POUR Principles
According to the official WCAG 2.2 specification, all success criteria are organized under four foundational principles:
1. Perceivable
Information and user interface components must be presentable to users in ways they can perceive. For PDFs, this means text alternatives for images, proper document structure, and sufficient color contrast.
2. Operable
User interface components and navigation must be operable. In PDFs, this includes keyboard navigation through form fields, logical tab order, and appropriately sized interactive targets.
3. Understandable
Information and operation of the user interface must be understandable. PDFs must have document language specified, predictable reading order, and clear form field labels.
4. Robust
Content must be robust enough to be interpreted by a wide variety of user agents, including assistive technologies. This requires proper PDF tagging that screen readers can parse correctly.
WCAG Conformance Levels
WCAG defines three conformance levels:
- Level A: 30 criteria addressing the most basic accessibility requirements. Minimum barrier removal.
- Level AA: 24 additional criteria (54 total). This is the legally required standard for most regulations including ADA Title II, Section 508, and EAA.
- Level AAA: 32 additional criteria (86 total). Enhanced accessibility, but not typically required for legal compliance.
According to Level Access, "WCAG 2.2 Level AA is the recommended standard for legal compliance."
What's New in WCAG 2.2
According to the W3C, WCAG 2.2 adds nine new success criteria focused on users with cognitive disabilities, low vision, and motor disabilities. Six are Level AA (legally relevant):
New Level AA Criteria in WCAG 2.2
2.4.11 Focus Not Obscured (Minimum)
When a component receives keyboard focus, at least a portion of it must remain visible and not be hidden by other content.
2.5.7 Dragging Movements
Functionality requiring dragging must be achievable with a single pointer without dragging, unless dragging is essential.
2.5.8 Target Size (Minimum)
Interactive targets must be at least 24×24 CSS pixels, with some exceptions. Critical for form fields and links in PDFs.
3.2.6 Consistent Help
Help mechanisms must appear in the same relative order across multiple pages.
3.3.7 Redundant Entry
Information previously entered should not need to be re-entered. For PDF forms, this means supporting auto-fill.
3.3.8 Accessible Authentication (Minimum)
Cognitive function tests (like CAPTCHAs) cannot be required for authentication without alternatives.
According to AudioEye, "WCAG 2.2 introduces nine new success criteria. These focus on accessibility for web users with low vision, cognitive and learning disabilities, and motor disabilities."
Key WCAG Success Criteria for PDFs
According to Continual Engine, the following WCAG criteria are most relevant for PDF accessibility:
1.1.1 Non-text Content (Level A)
According to the W3C Understanding document, all non-text content must have a text alternative that serves an equivalent purpose.
For PDFs, this means:
- All images must have meaningful alt text
- Decorative images must be marked as artifacts
- Charts and diagrams need extended descriptions
- Complex images may require both short and long descriptions
1.3.1 Info and Relationships (Level A)
Information, structure, and relationships conveyed through presentation must be programmatically determined. For PDFs:
- Headings must use proper heading tags (H1, H2, H3, etc.)
- Lists must use list structure tags (L, LI, LBody)
- Tables must have properly associated header cells
- Form fields must have programmatically associated labels
1.3.2 Meaningful Sequence (Level A)
Content must be presented in a meaningful reading order that can be programmatically determined. In PDFs, this means the tag tree reading order must match the intended reading sequence.
1.4.3 Contrast (Minimum) (Level AA)
Text must have a contrast ratio of at least 4.5:1 against its background. Large text (18pt or 14pt bold) requires at least 3:1.
2.4.2 Page Titled (Level A)
PDFs must have a document title in the metadata that describes the document's topic or purpose.
3.1.1 Language of Page (Level A)
The primary language of the PDF must be specified in the document metadata. This allows screen readers to use the correct pronunciation.
4.1.2 Name, Role, Value (Level A)
For all user interface components, the name and role must be programmatically determined. In PDF forms, this means all form fields must have accessible names.
PDF-Specific WCAG Requirements Checklist
Based on guidance from WebAIM's WCAG Checklist and Accessible.org:
| Requirement | WCAG Criterion | Level |
|---|---|---|
| Document is tagged | 1.3.1, 4.1.2 | A |
| Images have alt text | 1.1.1 | A |
| Reading order is logical | 1.3.2 | A |
| Headings properly nested | 1.3.1 | A |
| Tables have headers | 1.3.1 | A |
| Document language set | 3.1.1 | A |
| Document title exists | 2.4.2 | A |
| Color contrast 4.5:1 | 1.4.3 | AA |
| Form fields labeled | 1.3.1, 4.1.2 | A |
| Bookmarks for long docs | 2.4.5 | AA |
WCAG 2.2 vs PDF/UA
WCAG 2.2 and PDF/UA (ISO 14289) are complementary standards:
- WCAG 2.2: General web accessibility guidelines that apply to all digital content including PDFs
- PDF/UA: Technical specification specifically for accessible PDF files
A PDF that meets PDF/UA will generally satisfy WCAG requirements, though some WCAG criteria (like color contrast) require additional verification beyond what PDF/UA mandates.
Legal Status of WCAG 2.2
According to AllAccessible:
- ADA Title II: The DOJ's April 2024 rule references WCAG 2.1 Level AA, but courts increasingly look to WCAG 2.2
- Section 508: Currently requires WCAG 2.0 AA, but updates to incorporate WCAG 2.2 are expected
- European Accessibility Act: EN 301 549 is expected to adopt WCAG 2.2 in 2025
- ISO Standard: WCAG 2.2 is now ISO/IEC 40500:2025
Backward Compatibility
According to the W3C:
"Content that conforms to WCAG 2.2 also conforms to WCAG 2.0 and WCAG 2.1. If you're WCAG 2.1 AA compliant, you only need to implement the 6 new Level AA criteria."
One notable change: Success Criterion 4.1.1 Parsing was removed in WCAG 2.2 as modern browsers no longer need it. This means WCAG 2.2 has 86 criteria total (77 from 2.1 minus 1 removed, plus 9 new).
Common WCAG Failures in PDFs
Based on accessibility audit findings:
- Missing tags: Document has no tag structure (fails 1.3.1, 4.1.2)
- Improper reading order: Multi-column layouts read incorrectly (fails 1.3.2)
- Images without alt text: No text alternative provided (fails 1.1.1)
- Scanned PDFs without OCR: No selectable text layer (fails 1.1.1, 1.3.1)
- Table structure missing: Data tables lack header associations (fails 1.3.1)
- Form fields unlabeled: Fields have no accessible names (fails 4.1.2)
- No document title: Title field is empty (fails 2.4.2)
- Language not set: Screen reader can't determine pronunciation (fails 3.1.1)
Testing PDFs for WCAG Compliance
Comprehensive WCAG testing for PDFs requires both automated and manual checks:
Automated Testing Tools
- PAC 2024: Tests against PDF/UA and WCAG criteria
- Adobe Acrobat Accessibility Checker: Built-in checking (limited scope)
- CommonLook PDF Validator: Comprehensive standards validation
- axesCheck: Online PDF/UA validator
Manual Testing Required
- Verify alt text accurately describes images
- Check reading order matches visual layout
- Confirm table headers are correct
- Test with screen readers (JAWS, NVDA, VoiceOver)
- Verify color contrast with color contrast analyzer
How AdaRemediation Ensures WCAG 2.2 Compliance
AdaRemediation automates WCAG compliance for your PDF documents:
- Complete tagging: Proper document structure for all WCAG 1.3.x criteria
- AI-generated alt text: Meaningful descriptions reviewed by humans
- Reading order correction: Logical sequence for screen readers
- Table remediation: Proper header associations for complex tables
- Form field labeling: Accessible names for all form controls
- Metadata completion: Document title and language specification
- Standards validation: Testing against WCAG 2.1 AA, Section 508, and PDF/UA
Check your PDFs against WCAG 2.2
Get a free accessibility audit to identify WCAG compliance issues in your documents.
Get free audit