Guide

WCAG vs PDF/UA

They are often presented as levels of one ladder. They are not. WCAG describes outcomes for users; PDF/UA describes how a PDF file must be built so software can deliver those outcomes.

Check a PDF for free

Side by side

WCAG 2.2 compared with PDF/UA
WCAG 2.2PDF/UA
PublisherW3CISO (TC 171), maintained with the PDF Association
Current versions2.2 (Recommendation, 2023)ISO 14289-1 (PDF/UA-1, rev. 2014); ISO 14289-2 (PDF/UA-2, 2024, for PDF 2.0)
ScopeWeb content generally, including PDFsPDF files and the software that reads them
FormTestable success criteria at A/AA/AAATechnical file requirements
ExampleSC 2.4.2: pages have titles that describe purposeDocument title in metadata and DisplayDocTitle set to true

Example: the title requirement

A PDF/UA-1 validator can confirm a dc:title value exists and the viewer preference DisplayDocTitle is true. WCAG 2.4.2 additionally asks whether the title describes the topic or purpose. A file titled 'Untitled-3' passes the first test and fails the second.

Why there is no tier ladder

Conformance levels A, AA and AAA exist only within WCAG. PDF/UA has no levels. Section 508 and many other legal frameworks reference WCAG; none of them turn PDF/UA into a 'gold' version of WCAG. Be wary of anyone selling bronze, silver or gold compliance.

Limitations

Machine-checkable PDF/UA failure conditions (catalogued in the Matterhorn Protocol) still leave many conditions that require human judgment. Passing a validator is evidence about tested conditions only.

Sources

Check your own PDF

Run a free automated check to see which of these issues appear in your file and whether any are repairable.

Last updated 2026-10-01