PDF/UA-2 is the second part of the ISO standard for accessible PDF and the first written for PDF 2.0. It answers a question PDF/UA-1 could not, because PDF/UA-1 predates PDF 2.0 by five years: what does a fully accessible PDF 2.0 file look like? This guide explains what the standard contains, how it relates to PDF/UA-1 and to the free WTPDF specification it was built from, and what practical difference it makes to a team that has to produce or buy accessible documents in 2026.
Where PDF/UA-2 comes from
According to the PDF Association, PDF/UA-1 was introduced in 2012 and last revised in 2014, providing accessibility requirements based on ISO 32000-1, which is PDF 1.7. PDF 2.0 (ISO 32000-2) was released in 2017 and updated in 2020 with what the Association calls "numerous enhancements relevant to Tagged PDF". In February 2024 the Association published WTPDF, the Well-Tagged PDF specification, defining accessibility and reuse requirements for PDF 2.0. ISO 14289-2 elevated those same requirements to an International Standard; the Association announced its arrival on March 15, 2024, noting that ISO 14289-2 must be purchased while WTPDF is freely available. The normative text was developed by the Association's PDF/UA and PDF Reuse technical working groups together with ISO TC 171/SC 2/WG 9.
What it adds over PDF/UA-1
The PDF Association summarises the enhancements to core tagged PDF requirements as comprehensive requirements for structure element attributes, comprehensive requirements for the use of annotations, and examples of semantically significant attribute usage. Building on PDF 2.0 itself, PDF/UA-2 and WTPDF then add:
- comprehensive requirements for the new structure element types introduced in PDF 2.0;
- rules governing the inclusion of structure elements defined in PDF 1.7 as well as PDF 2.0;
- detailed requirements for math, including support for MathML;
- requirements for intra-document links using the structure destinations feature;
- use of the Associated Files feature to integrate non-PDF content.
The math provision is the one most people notice. PDF/UA-1 could only require that a formula be tagged and given alternative text; PDF/UA-2 provides for MathML, which is what screen readers and braille displays need to navigate an equation rather than hear a description of it. That is why the LaTeX Project's tagged PDF work targets PDF/UA-2 rather than PDF/UA-1; see accessible PDFs from LaTeX.
PDF/UA-1 is not withdrawn
Because the two parts are written against different PDF versions, PDF/UA-2 does not replace PDF/UA-1. A PDF 1.7 file claims PDF/UA-1; a PDF 2.0 file claims PDF/UA-2. The PDF Association notes that PDF/UA-1 has been broadly implemented in software and is referenced directly and implied in regulations around the world, which will remain true for years. A document produced as PDF 1.7 with a correct tag structure is not made less accessible by the existence of the newer standard.
What the law asks for
No major accessibility regulation names PDF/UA-2 as a requirement. The ADA Title II web rule requires WCAG 2.1 Level AA for web content including documents; the European standard EN 301 549 applies WCAG-derived requirements to non-web documents in its clause 10; the UK's public sector regulations point at WCAG 2.2 AA. PDF/UA in either part is a technical means to reach those outcomes and a strong form of evidence, particularly for procurement, but a PDF/UA identifier in a file is not compliance with any of them. The PDF/UA versus WCAG guide explains the relationship.
Tool support in 2026
| Tool | PDF/UA-2 support | Source |
|---|---|---|
| LaTeX (kernel tagging) | Targets ua-2 through \DocumentMetadata{pdfstandard=ua-2} | LaTeX Project usage instructions |
| WeasyPrint | Accepts --pdf-variant pdf/ua-2; output not guaranteed valid | WeasyPrint API reference |
| Prince | Documents PDF/UA-1 only | Prince PDF output documentation |
| veraPDF | Publishes PDF/UA-2 and WTPDF validation profiles | veraPDF validation profiles wiki |
| Matterhorn Protocol | Covers PDF/UA-1; there is no equivalent published protocol for PDF/UA-2 in the sources checked | PDF Association, Matterhorn Protocol 1.1 |
Viewer and screen reader support for PDF 2.0 structure, and for MathML inside PDF in particular, is the weak link. A file can be valid PDF/UA-2 and still be read poorly by a viewer that only understands PDF 1.7 structure. Until that changes, test PDF/UA-2 output with the assistive technology your readers use, following how to test a PDF with a screen reader, and consider providing an HTML alternative for math-heavy content.
When to choose it
- Choose PDF/UA-2 when the producer already writes PDF 2.0, when equations must be navigable rather than described, or when a buyer names it.
- Stay on PDF/UA-1 when the toolchain and validators are built around PDF 1.7, which is still most of the remediation market, and when the content has no need of PDF 2.0 features.
- In both cases the human checks are the same: reading order, heading logic, table headers, alternative text quality, and a screen reader pass.
Frequently asked questions
What is PDF/UA-2?
PDF/UA-2 is ISO 14289-2, published in 2024, the standard for accessible PDF files based on PDF 2.0 (ISO 32000-2). It was built from the PDF Association's free WTPDF specification and adds comprehensive rules for structure element attributes and annotations, PDF 2.0 structure types, MathML for math, structure destinations for internal links, and Associated Files. PDF/UA-1 remains the standard for PDF 1.7 files.
Is PDF/UA-2 backward compatible with PDF/UA-1?
The two parts are written against different PDF versions, so a file conforms to one or the other rather than both: PDF/UA-1 for PDF 1.7 and PDF/UA-2 for PDF 2.0. PDF/UA-2 does not withdraw or replace PDF/UA-1, and PDF/UA-1 remains widely implemented and referenced.
Do I need PDF/UA-2 to comply with accessibility law?
No regulation checked for this guide names PDF/UA-2. The ADA Title II rule, EN 301 549, and the UK public sector regulations all require WCAG-based outcomes. PDF/UA-2 is a technical route to those outcomes and useful procurement evidence, particularly for math-heavy documents, but a PDF/UA identifier is not compliance on its own.
Sources
The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.
- PDF Association, March 15, 2024: ISO 14289-2 (PDF/UA-2), the gold standard for accessibility in PDF 2.0, has arrived . Publication, relationship to WTPDF and PDF/UA-1, and the list of enhancements quoted here.
- PDF Association: ISO 14289-2 (PDF/UA-2) resource page
- LaTeX Project: Using LaTeX to produce accessible PDF
- WeasyPrint documentation: API reference
- Prince documentation: PDF output and profiles
- veraPDF validation profiles: PDF/UA Part 2 rules
- eCFR: 28 CFR Part 35, Subpart H, Web and Mobile Accessibility . The Title II rule names WCAG 2.1 Level A and AA.
Keep reading
PDF/UA versus WCAG
What each standard measures, where automated validation stops, and what a defensible claim requires.
Read the guide →The Matterhorn Protocol explained
What the Matterhorn Protocol is, how its 31 checkpoints and 136 failure conditions test PDF/UA-1, which ones a machine can decide, and how to read a checker report built on it.
Read the guide →Accessible PDFs from LaTeX in 2026
How to produce tagged, PDF/UA-2 targeted output from LaTeX with \DocumentMetadata, which engine to use, how to add alt text and tagged math, and where package support still limits results.
Read the guide →