Understanding WCAG, PDF/UA & Section 508
A plain-English guide to the standards that govern PDF accessibility — what they require, how they apply to your documents, and how to measure whether remediation worked.
The Four Standards That Matter
These four frameworks define what "accessible" means for PDFs. They overlap significantly — meeting WCAG 2.1 AA generally satisfies the others.
WCAG 2.1 AA
Web Content Accessibility Guidelines 2.1 Level AA
Scope
All web content including PDFs published online
Authority
W3C (World Wide Web Consortium)
Deadline
Ongoing - but ADA Title II public-entity deadlines now run in 2027 and 2028
Key Requirements
- 50 success criteria at Level A and AA
- Applies to web content, including documents served on the web
- Referenced by legislation in 40+ countries
- The de facto global accessibility standard
PDF-Specific Requirements
- Tagged PDF with semantic structure
- Alt text for all non-decorative images
- Logical reading order
- Document language specified
- Heading hierarchy (H1-H6)
- Table row/column headers
- Colour contrast ratios met
- Bookmarks for documents > 20 pages
Enforced By
ADA (US), EAA (EU), Accessibility Act (UK), AODA (Canada)
PDF/UA-1
ISO 14289-1: Universal Accessibility for PDF
Scope
All PDF documents intended for accessible consumption
Authority
ISO (International Organization for Standardization)
Deadline
No standalone deadline — referenced by other regulations
Key Requirements
- Complete tag tree covering all content
- Proper StructTreeRoot with ParentTree
- BDC/EMC marked content operators in content streams
- Role mapping for custom tag types
PDF-Specific Requirements
- Every content element must be tagged or marked as artifact
- Figures require alt text (/Alt entry)
- Tables require TH cells with Scope attribute
- Document catalog must include /MarkInfo with /Marked true
- All fonts must be embedded
- Natural language must be specified
- No reliance on colour alone for information
- Security settings must not interfere with assistive technology
Enforced By
Referenced by Section 508, EN 301 549, procurement standards
Section 508
Section 508 of the Rehabilitation Act (Revised 2018)
Scope
US federal agencies and recipients of federal funding
Authority
US Access Board / GSA
Deadline
Already enforced — no new deadline
Key Requirements
- Incorporates WCAG 2.0 Level AA by reference (effectively WCAG 2.1 AA in practice)
- Applies to all ICT developed, procured, or used by federal agencies
- Extends to state agencies receiving federal funds
- Includes electronic documents (PDFs, Word, Excel, etc.)
PDF-Specific Requirements
- All WCAG 2.1 AA requirements apply to PDFs
- Documents must be usable with assistive technology
- Must pass Trusted Tester methodology
- Forms must have programmatically associated labels
- No CAPTCHA or time-based barriers
- Equivalent access must be provided for all content
Enforced By
Office of Civil Rights complaints, DOJ enforcement, procurement requirements
ADA Title II
Americans with Disabilities Act — Title II (2024 Final Rule)
Scope
State and local government entities
Authority
US Department of Justice
Deadline
April 26, 2027 (50K+ population) / April 26, 2028 (smaller and special district governments)
Key Requirements
- All web content and mobile apps must meet WCAG 2.1 AA
- Includes PDFs and documents published on government websites
- Public entities serving 50K+ people: April 26, 2027 deadline
- Smaller entities and special district governments: April 26, 2028 deadline
PDF-Specific Requirements
- All PDFs on government websites must be WCAG 2.1 AA compliant
- Retroactive — existing documents must be remediated
- Includes archived content if still publicly available
- No exemption for "historical" or "legacy" documents
- Must provide accessible alternative if original cannot be remediated
Enforced By
DOJ enforcement, private right of action, complaint investigations
WCAG 2.1: The POUR Principles
WCAG is organised around four principles — Perceivable, Operable, Understandable, Robust — each containing guidelines with testable success criteria.
Perceivable
Information and user interface components must be presentable to users in ways they can perceive.
| Guideline | Name | How It Applies to PDFs | Level |
|---|---|---|---|
| 1.1 | Text Alternatives | Alt text for images, charts, and decorative elements | A |
| 1.2 | Time-based Media | Captions/transcripts for embedded audio/video in PDFs | A/AA |
| 1.3 | Adaptable | Semantic structure (headings, lists, tables with headers) | A |
| 1.4 | Distinguishable | Colour contrast (4.5:1 for text), text resizing, reflow | AA |
Operable
User interface components and navigation must be operable by all users.
| Guideline | Name | How It Applies to PDFs | Level |
|---|---|---|---|
| 2.1 | Keyboard Accessible | Tab order through form fields, links, and interactive elements | A |
| 2.4 | Navigable | Document title, heading hierarchy for navigation, link purpose | A/AA |
| 2.5 | Input Modalities | Touch targets, pointer gestures for interactive PDF forms | AA |
Understandable
Information and operation of the user interface must be understandable.
| Guideline | Name | How It Applies to PDFs | Level |
|---|---|---|---|
| 3.1 | Readable | Document language tag, language of parts for multilingual content | A/AA |
| 3.2 | Predictable | Consistent navigation, consistent identification of elements | A/AA |
| 3.3 | Input Assistance | Form field labels, error identification, instructions | A/AA |
Robust
Content must be robust enough to be interpreted by a wide variety of assistive technologies.
| Guideline | Name | How It Applies to PDFs | Level |
|---|---|---|---|
| 4.1 | Compatible | Valid tag structure, complete tag tree, proper role mappings | A/AA |
How to Measure Remediation Success
Compliance isn't a checkbox — it's a measurable outcome. Here are the six methods you should use to verify that your remediated PDFs actually work for people with disabilities.
Method 1
Automated Tag Validation
Software checks the PDF tag tree for structural completeness and correct role mappings.
Coverage
Catches ~60-70% of issues automatically
What It Checks
Verifies: tag tree exists, all content tagged or artifacted, correct nesting, role map present, language set.
Tools
Method 2
Screen Reader Testing
A real user or tester navigates the document using JAWS, NVDA, or VoiceOver.
Coverage
The gold standard — catches all UX issues
What It Checks
Verifies: reading order makes sense, alt text is meaningful, tables are navigable, headings create a usable outline.
Tools
Method 3
Matterhorn Protocol
A comprehensive 136-checkpoint test suite that maps PDF/UA requirements to testable conditions.
Coverage
136 checkpoints total — the most thorough test
What It Checks
Covers every requirement of ISO 14289-1 (PDF/UA). 89 checkpoints can be automated; 47 require human judgment.
Tools
Method 4
Trusted Tester (Section 508)
A standardised testing methodology developed by the US DHS for consistent 508 evaluation.
Coverage
The federal government standard
What It Checks
Tests 32 conditions across documents: structure, images, tables, forms, multimedia, and more.
Tools
Method 5
Colour Contrast Analysis
Measures the luminance ratio between foreground text and background colours.
Coverage
Essential for low-vision users
What It Checks
WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text (18pt or 14pt bold).
Tools
Method 6
Reading Order Verification
Confirms that the tag tree reading order matches the intended visual reading flow.
Coverage
Critical — wrong order = wrong information
What It Checks
Multi-column layouts, sidebars, footnotes, and headers must be sequenced logically — not left-to-right across the page.
Tools
Recommended Post-Remediation Testing Workflow
Run PAC 2024
2 minutesFree tool from the PDF/UA Foundation. Open remediated PDF → check for Matterhorn errors. Target: zero failures.
Quick Screen Reader Test
5 minutesOpen in NVDA (free) or JAWS. Press H to jump headings, T to jump tables. Verify reading order and alt text make sense.
Check Tag Tree in Acrobat
3 minutesIf available, View → Navigation → Tags. Verify heading hierarchy, table structure, and artifact markers.
Verify Compliance Certificate
1 minutepdfaa.ai generates a certificate with each remediation. Archive it alongside the original and remediated files.
Spot-Check Colour Contrast
2 minutesUse TPGi Colour Contrast Analyser on any text-heavy pages. Verify 4.5:1 ratio for body text.
Meet All Four Standards in One Step
pdfaa.ai remediates your PDFs to satisfy WCAG 2.1 AA, PDF/UA-1, Section 508, and ADA Title II requirements - automatically. Test it with a document that matters.
$2/page · No subscription · WCAG 2.1 AA + PDF/UA + 508 + ADA covered