1. What is PDF/UA?
PDF/UA stands for PDF/Universal Accessibility. It is an international standard published as ISO 14289-1, first released in 2012, that defines the technical requirements for making PDF documents accessible to people with disabilities.
While WCAG provides broad guidelines for digital accessibility, PDF/UA is laser-focused on the PDF format. It specifies exactly how a PDF's internal structure — its tags, metadata, fonts, and content streams — must be constructed to be interpretable by assistive technologies like screen readers and braille displays.
The "UA" in PDF/UA stands for Universal Accessibility, reflecting the standard's goal: every PDF should be usable by every person, regardless of ability. Unlike WCAG, which provides principles and success criteria that require human judgment to evaluate, PDF/UA defines requirements that are largely machine-verifiable. A tool can check a PDF against the PDF/UA specification and definitively report whether it conforms or not.
This makes PDF/UA the backbone of automated accessibility validation. When organizations need to verify that thousands of documents are accessible, PDF/UA provides the testable criteria that make large-scale validation possible.
2. Why PDF/UA Matters
PDF/UA matters because it transforms accessibility from a subjective judgment into an objective, verifiable standard. Here is why that matters in practice:
Legal Protection
When the ADA Title II final rule requires WCAG 2.1 AA conformance for documents, PDF/UA provides the technical specification for how that conformance is achieved in PDFs. A PDF/UA-conformant document is strong evidence of compliance. Conversely, a document that fails PDF/UA validation is demonstrably non-compliant — which is exactly what a plaintiff or the DOJ would present in an enforcement action.
Scalable Validation
Because PDF/UA requirements are machine-testable, you can validate thousands of documents automatically. Manual accessibility review of every document is impractical at scale; PDF/UA validation makes it possible to verify compliance across your entire document library programmatically.
Interoperability
PDF/UA-conformant documents work reliably across different screen readers, operating systems, and PDF viewers. Without PDF/UA conformance, a document might work with JAWS on Windows but fail with VoiceOver on macOS. The standard ensures consistent behavior across all assistive technologies.
International Recognition
As an ISO standard, PDF/UA is recognized internationally. The European Union's EN 301 549 references PDF/UA, as do accessibility regulations in Canada, Australia, and other countries. Achieving PDF/UA compliance positions your documents for global accessibility requirements, not just U.S. law.
3. PDF/UA vs WCAG
PDF/UA and WCAG are complementary standards, not competitors. They address accessibility from different angles, and understanding their relationship is essential for anyone managing document compliance.
| Aspect | WCAG 2.1 | PDF/UA |
|---|---|---|
| Scope | All digital content (web, documents, apps) | PDF documents only |
| Published by | W3C (World Wide Web Consortium) | ISO (International Organization for Standardization) |
| Nature | Principles and guidelines | Technical specification |
| Testability | Mix of automated and manual | Primarily machine-verifiable |
| Content quality | Addresses alt text quality, readability | Requires alt text presence, not quality |
| Legal reference | ADA Title II, Section 508, EN 301 549 | Referenced by WCAG techniques for PDFs |
In practice, you need both. WCAG defines what your documents need to achieve (alternative text that conveys meaning, logical reading order, sufficient contrast). PDF/UA defines how to achieve it technically (specific tag structures, metadata properties, font embedding rules). A PDF can pass PDF/UA validation but still fail WCAG if its alt text is present but meaningless. Conversely, a document with excellent alt text but no proper tag structure fails both standards.
The W3C's official PDF techniques for WCAG explicitly reference PDF/UA as the technical implementation standard. When a regulator or auditor evaluates your PDF compliance, they are likely to use PDF/UA validation as the starting point and then manually review content quality criteria from WCAG.
4. Technical Requirements of PDF/UA
PDF/UA-1 (ISO 14289-1) defines specific technical requirements for PDF files. These requirements address every layer of a PDF's internal structure. Here are the major categories:
Tagged Structure
Every piece of content in the document must be included in the tag tree or marked as an artifact. The tag tree must use standard PDF structure types (Document, Part, Sect, H1-H6, P, L, LI, Table, TR, TH, TD, Figure, etc.) that map to their semantic roles. Custom tags are allowed only if they are mapped to standard roles. No content may exist outside the tag tree unless it is a page artifact (headers, footers, page numbers, watermarks).
Alternative Text
Every Figure tag must have an Alt attribute containing a text description. Decorative images must not be tagged as Figures — they must be marked as artifacts. The standard requires that alt text be present but does not define quality criteria; WCAG handles content quality. Complex images may also use the ActualText attribute or a longer description linked via the LongDesc attribute.
Document Metadata
The document must have a Title set in both the document info dictionary and XMP metadata, and they must match. The DisplayDocTitle viewer preference must be set to true so the title (not the filename) appears in the viewer title bar. The document language must be set in the catalog's Lang entry. The PDF must declare itself as PDF/UA-conformant via an XMP metadata property (pdfuaid:part = 1).
Font Requirements
All fonts must be embedded in the document. Every glyph used must have a Unicode mapping so that text can be extracted and interpreted correctly by assistive technologies. Fonts that do not map to Unicode (some symbol fonts, custom barcode fonts) require ActualText attributes on their containing spans to provide the text equivalent.
Table Structure
Tables must use Table, TR, TH, and TD tags. Header cells (TH) must have a Scope attribute indicating whether they are row headers or column headers. For complex tables with multiple header levels, cells must use the Headers attribute to explicitly associate data cells with their header cells. Every table must have at least one header row or column.
Lists
Lists must be tagged with L (list), LI (list item), Lbl (label/marker), and LBody (list item body) elements. Nested lists must be properly nested within parent list items. Bulleted lists, numbered lists, and definition lists each have specific tagging requirements to ensure screen readers announce them correctly.
Links and Annotations
Hyperlinks must be tagged as Link structure elements containing an OBJR (object reference) to the link annotation. The link annotation must have a Contents entry or the Link tag must contain text content that describes the link destination. Link annotations must not overlap or interfere with the document's tag structure.
5. How to Validate PDF/UA Compliance
One of PDF/UA's greatest strengths is that compliance can be verified programmatically. Several tools exist for this purpose, ranging from free open-source options to commercial products.
veraPDF
Open Source / Industry Standard
veraPDF is the industry-reference open-source PDF/UA validator, endorsed by the PDF Association. It checks PDF files against the complete ISO 14289-1 specification and produces detailed machine-readable reports listing every rule that passed or failed. veraPDF runs as a Java CLI tool or library, making it ideal for integration into automated pipelines. It is the validator used by CASO Comply in our remediation pipeline.
PAC (PDF Accessibility Checker)
Free / Swiss Foundation
PAC is a free desktop tool developed by the Swiss Foundation for Access for All. It provides a graphical interface for checking PDF/UA conformance and includes a unique "screen reader preview" that shows how a document will be interpreted by assistive technologies. PAC is excellent for manual spot-checking and understanding specific failures, though it is Windows-only and less suited for batch automation.
Adobe Acrobat Pro
Commercial / Adobe
Adobe Acrobat Pro includes an accessibility checker that tests for many PDF/UA requirements. It is useful for both checking and fixing issues, as you can address problems directly in Acrobat. However, Acrobat's checker is not a complete PDF/UA validator — it misses some requirements that veraPDF and PAC catch. Use it as a first step, not a final validation.
For organizations with large document libraries, the practical approach is to use veraPDF in an automated pipeline for bulk validation and PAC for manual review of edge cases or complex documents. The combination provides both coverage and depth.
6. PDF/UA-2: The Newer Standard
PDF/UA-2 (ISO 14289-2) was published in December 2023. It is the next generation of the PDF/UA standard, aligned with PDF 2.0 (ISO 32000-2) and WCAG 2.1/2.2.
Key changes in PDF/UA-2 compared to PDF/UA-1:
- Based on PDF 2.0 — PDF/UA-2 requires PDF 2.0 as its base format, which introduces new structure types like DocumentFragment, Aside, and enhanced support for MathML annotations.
- Aligned with WCAG 2.1/2.2 — The standard explicitly maps its requirements to WCAG success criteria, making the relationship between the two standards clear and formal.
- Namespaces for structure types — PDF 2.0 introduces namespaced structure types, allowing for richer semantic markup including HTML-like elements.
- Enhanced pronunciation support — Improved mechanisms for specifying pronunciation of specialized terms, abbreviations, and non-standard words.
- Better mathematical content — Native support for MathML annotations within PDF structure, improving accessibility of scientific and technical documents.
Currently, most regulatory requirements reference PDF/UA-1, and the majority of tools and workflows target PDF/UA-1 conformance. PDF/UA-2 adoption is growing but is not yet the dominant standard. Organizations should achieve PDF/UA-1 conformance now and plan to transition to PDF/UA-2 as tool support matures and regulations update their references.
7. Common PDF/UA Failures
Based on validation of thousands of government and enterprise PDFs, these are the most frequently encountered PDF/UA failures:
No PDF/UA Identifier
The document does not declare itself as PDF/UA-conformant in its XMP metadata. Even documents that are structurally compliant often lack this declaration, which is required for formal conformance.
Content Outside the Tag Tree
Real content (text, images) exists in the page stream but is not referenced by any tag and is not marked as an artifact. This "orphaned" content is invisible to assistive technologies. Common with headers, footers, and watermarks that were not properly artifacted.
Figure Tags Without Alt Text
Images are tagged as Figure elements but lack the required Alt attribute. This is a clear PDF/UA violation — every Figure must have alt text. Alternatively, purely decorative images should not be tagged as Figures at all but marked as artifacts.
Missing or Mismatched Document Title
The document lacks a title, or the title in the document info dictionary does not match the XMP metadata title. DisplayDocTitle is not set to true. These are among the simplest PDF/UA requirements to fix but are consistently overlooked.
Table Headers Not Identified
Tables use TD tags for all cells, including header cells that should be TH. The Scope attribute is missing from header cells. This makes it impossible for screen readers to associate data values with their column and row headers.
Fonts Without Unicode Mapping
Glyphs in the document cannot be mapped to Unicode characters. This typically happens with symbol fonts, decorative fonts, or fonts embedded without proper encoding tables. Affected text cannot be extracted or read by assistive technologies.
8. How CASO Comply Ensures PDF/UA Compliance
CASO Comply's remediation pipeline is built around PDF/UA as the definitive technical standard. Every document we process goes through a pipeline designed to produce PDF/UA-conformant output.
AI-Powered Structural Tagging
Our PDF remediation engine uses Adobe Auto-Tag API combined with Claude AI to build a complete, correct tag tree for every document. Tags are mapped to standard PDF structure types, ensuring PDF/UA conformance. Complex layouts, multi-column pages, and nested tables are handled automatically.
veraPDF Validation on Every Document
Every remediated document is validated against the full PDF/UA-1 specification using veraPDF before delivery. Documents that fail validation are flagged for additional processing or manual review. You receive a validation report for every document, providing an auditable compliance record.
Metadata and Font Compliance
CASO Comply automatically sets all required PDF/UA metadata — document title, language, PDF/UA identifier, DisplayDocTitle — and ensures all fonts are properly embedded with Unicode mappings. These are the "easy fixes" that are nonetheless missed in the vast majority of PDF documents.
Free Compliance Scan
Want to know how your current documents measure up against PDF/UA? Our free compliance scan identifies every PDF on your website and runs automated accessibility checks to show your current status. No commitment required.
Verify your PDF/UA compliance.
Find out which of your PDF documents pass PDF/UA validation and which need remediation. Our free scan provides a complete compliance report for your entire document library.