On this page
What PDF/UA is and why it exists
WCAG was written for the web. PDFs aren't — they have their own structural model, tag tree, and metadata rules. WCAG tells you the goals, not how to do it in a PDF.
PDF/UA (PDF/Universal Accessibility) fills that gap. It defines the tag types, structure tree, metadata, language, alt text, and viewer behavior that make a PDF testable and usable with assistive technology.
PDF/UA-1 — the working standard
ISO 14289-1:2014 is the version almost every PDF accessibility workflow uses today.
What PDF/UA-1 requires:
- A real structure tree. Every meaningful piece of content has to be tagged with the right structural type — paragraph, heading, list, table, figure, and so on.
- Logical reading order. The order of items in the structure tree has to match the order a sighted reader would follow.
- Alternate text on figures. Every meaningful graphic needs a description; decorative graphics must be marked as artifacts.
- Properly tagged tables. Header cells and row/column relationships identified.
- Document metadata. Title, primary language, and viewer-display preference all set.
- Embedded fonts mapped to Unicode. So extracted text actually represents the characters readers can see.
- No accessibility-hostile features. Security settings cannot block screen readers; flashing content is forbidden.
PDF/UA-1 is what Section 508 references directly and what most PDF accessibility checkers validate by default. If you need one compliance target in 2026, use this.
PDF/UA-2 — the modernized standard
ISO 14289-2:2024 was published on March 15, 2024. It updates PDF accessibility for PDF 2.0.
Key differences from PDF/UA-1:
- Smaller, cleaner tag set. PDF/UA-2 trims redundant or rarely-used structure types and aligns the remaining ones more closely with HTML5 semantics.
- Namespaces. Tags can identify the rules they follow, which helps complex and multilingual PDFs.
- Better handling of complex content. Math (via MathML), multimedia, and richly nested tables are described more precisely.
- Reading order via structure only. The legacy "reading order via content stream order" path that PDF/UA-1 still tolerates is removed. Structure is the single source of truth.
PDF/UA-2 is not yet the US legal target, but it is where tools and authoring workflows are moving.
We test PDF/UA-2 alongside PDF/UA-1 and WTPDF in the same pass, so files are built for current and emerging expectations.
WTPDF — the free, open spec
WTPDF means Well-Tagged PDF. Published by the PDF Association on March 11, 2024, it is the free tagging specification aligned with PDF/UA-2.
The difference is scope:
- PDF/UA-2 is the formal ISO accessibility standard.
- WTPDF covers the tagging rules that authoring software, AI tools, and document pipelines need.
For compliance, target PDF/UA. For clean structure in modern document pipelines, WTPDF is the open spec to track.
The Matterhorn Protocol — how PDF/UA is tested
The Matterhorn Protocol is the PDF Association's methodology for verifying PDF/UA conformance.
Matterhorn Protocol 1.1 defines:
- 31 checkpoints
- 136 failure conditions
- 89 machine-checkable conditions
- 45 human-checkable conditions, including meaningful alt text, reading order, and color independence.
The 89/45 split is why a passed automated check is not the same as an accessible PDF. A complete workflow covers both.
Our checker covers the 89 machine-checkable Matterhorn conditions plus broader PDF/UA, WTPDF, and WCAG tests. Uncertain pages needing judgment go to specialists when needed.
Common validators include PAC 2024, Adobe Acrobat Pro, callas pdfaPilot, and platform validation engines.
How PDF/UA relates to WCAG
WCAG and PDF/UA cover different layers:
| Requirement | WCAG 2.1 AA | PDF/UA-1 | WTPDF |
|---|---|---|---|
| What it defines | Accessibility goals across all digital content | How a PDF must be built to meet those goals | How a PDF 2.0 must be tagged |
| Scope | Web pages, apps, documents, video | PDF files only | PDF 2.0 tagging only |
| Published by | W3C (June 5, 2018) | ISO (2014) | PDF Association (March 11, 2024) |
| Cost to read | Free | Paid (ISO) | Free |
| Referenced by US law | Yes — ADA Title II, Section 508 | Yes — Section 508 references it directly | Not yet |
For PDFs, the reliable path is PDF/UA-1 structure, Matterhorn validation, and human review for the 45 judgment-based conditions.
For more on the WCAG side, see our WCAG 2.1 AA guide.
Which one should you target?
If your goal is current compliance (Section 508, ADA Title II, state procurement)
Target PDF/UA-1. It is what the law cites, what auditors check against, and what every major tool validates. PDF/UA-2 and WTPDF are bonuses, not substitutes.
If you are unsure
Default to PDF/UA-1. Add PDF/UA-2 and WTPDF checks when your tools support them.
One upload is designed to remediate PDFs to PDF/UA-1, PDF/UA-2, and WTPDF in the same workflow.
Primary sources to verify
Use these standards references when you review PDF/UA, WTPDF, and Matterhorn claims.
How ADAComply handles PDF/UA & WTPDF
ADAComply is designed to remediate PDFs to PDF/UA-1, PDF/UA-2, WTPDF, and WCAG 2.1 AA. Standard-layout pages move through the remediation pipeline, uncertain pages route to specialists, and reports stay in the dashboard.
Send your site for a free audit dashboard, sorted by likely exempt and needs work.
Frequently asked questions
What does PDF/UA stand for?
PDF/Universal Accessibility. It is the ISO standard that defines what makes a PDF accessible — the tag types, structure tree, metadata, and behavior rules.
What is the difference between PDF/UA-1 and PDF/UA-2?
PDF/UA-1 (ISO 14289-1:2014) is the version the law and most tools currently use. PDF/UA-2 (ISO 14289-2:2024) modernizes the standard for PDF 2.0, simplifies the tag set, adds namespaces, and improves complex-content handling. PDF/UA-1 is the operative target for 2026 compliance.
Is WTPDF the same as PDF/UA-2?
Almost. WTPDF and PDF/UA-2 share the same tagging rules — that is the whole point of the alignment. WTPDF is free and covers just the tagging side. PDF/UA-2 is the paid ISO standard and adds the metadata, security, and viewer-behavior pieces needed for full compliance certification.
What is the Matterhorn Protocol?
The PDF Association's testing methodology for PDF/UA. Version 1.1 defines 31 checkpoints and 136 failure conditions — 89 machine-checkable and 45 human-checkable. Almost every PDF accessibility checker on the market is built on it.
Can a PDF pass automated checks and still be inaccessible?
Yes. Forty-five of the 136 Matterhorn failure conditions are judgment-based checks: meaningful alt text, sensible reading order, color independence, and similar issues. That is why a credible remediation workflow combines automated checks with documented specialist review when needed.
Where can I read these standards?
PDF/UA-1 (ISO 14289-1:2014) and PDF/UA-2 (ISO 14289-2:2024) are sold by ISO. WTPDF and the Matterhorn Protocol are published free by the PDF Association at pdfa.org.