PDF/UA vs WCAG

PDF/UA (ISO 14289) and WCAG (the W3C's Web Content Accessibility Guidelines) are two accessibility standards that are complementary rather than competing, and understanding their relationship is central to document accessibility.

The essential difference is one of approach and scope. WCAG is outcome-based and technology-agnostic: it defines what a person with a disability must be able to perceive, operate, and understand, expressed as testable success criteria at levels A, AA, and AAA, and it applies broadly to web content, applications, media, and — through its published PDF techniques — to documents. It generally describes the required accessible experience without prescribing the precise internal mechanics of any one file format. PDF/UA, by contrast, is prescriptive and format-specific: an ISO standard, maintained by ISO TC 171/SC 2/WG 9 with the PDF Association, that specifies exactly how the internal structures of a PDF must be built — tagging, the structure tree, reading order, alternate text, language, and artifacts. A useful shorthand: PDF/UA audits the file's construction while WCAG audits the experience that construction delivers.

The two overlap heavily in intent. Both require a properly tagged document, correct reading order, text alternatives for images, declared language, and meaningful structure for headings, lists, and tables. Because PDF/UA operationalises so many document-relevant WCAG requirements at the file level, a PDF that genuinely conforms to PDF/UA will typically satisfy most WCAG success criteria relevant to native PDF page content. However, the relationship is not perfectly symmetrical. WCAG includes requirements PDF/UA does not fully address — for example certain colour-contrast criteria, or the accessibility of interactive and multimedia behaviours — so PDF/UA conformance does not by itself guarantee full WCAG conformance. Conversely, a document might appear to satisfy WCAG in practice yet still fail PDF/UA because its tag structure, role mapping, or artifact handling is not technically valid according to the ISO rules.

This is why the two are best applied together: WCAG supplies the user-centred outcome goals and the broad legal reference point (it is the basis for EN 301 549 and much accessibility legislation), while PDF/UA supplies the exact, unambiguous file-level engineering target that makes those outcomes achievable and verifiable in the PDF format. For document accessibility, treat them as a pair — WCAG for the "what" and PDF/UA for the "how."