What is PDF/UA, and how does it relate to WCAG?
PDF/UA, short for Universal Accessibility and published as ISO 14289, is the international standard for how an accessible PDF file must be built. WCAG sets what readers must be able to do with the content; PDF/UA sets how the PDF has to be constructed so assistive technology can deliver it. The two are complementary, and neither replaces a human review.
or drop it here. Free: up to 30 pages and 20 MB, no sign-up. The file is deleted as soon as the check finishes.
Accessibility report
Why did my PDF fail? The common failures in plain English
Technical PDF/UA-1 results (veraPDF)
Fix this PDF
After the fix
What is PDF/UA?
PDF/UA is the ISO 14289 family of standards for accessible PDF files. Its first part, ISO 14289-1:2014 (PDF/UA-1), applies to files that follow ISO 32000-1 (PDF 1.7); ISO 14289-2:2024 (PDF/UA-2) is a revised standard for PDF 2.0 (ISO 32000-2), based on the PDF Association’s WTPDF specification.
The PDF feature that carries the information assistive technology needs, such as sections, paragraphs, lists and tables, is called Tagged PDF, and PDF/UA states the technical features an accessible PDF must have. It does not cover how to convert a document or reach conformance. Last reviewed 2026-11-20.
How does PDF/UA relate to WCAG?
PDF/UA and WCAG are complementary: WCAG sets accessibility requirements for the content, and PDF/UA sets requirements for constructing the PDF file. The PDF Association says PDF/UA provides a means of making PDF files that conform to WCAG and may be used together with WCAG 2.x.
WCAG 2.1 success criteria are written as testable statements that are not technology-specific, and W3C publishes PDF techniques that show ways to meet them in PDF, such as technique PDF1 for text alternatives on images (WCAG 1.1.1).
- In PDF/UA but not in WCAG: for example the PDF/UA metadata identification, according to a 2021 PDF Association gap analysis by Dual Lab.
- In WCAG but not in PDF/UA: for example detailed requirements for text contrast (WCAG 1.4.3), the same gap analysis says.
Which WCAG 2.1 success criteria can a machine check in a PDF?
A machine can check that the structure and metadata behind most of these WCAG 2.1 criteria are present, but not whether they are right. PDF Checkup reports the checks below against these criteria; the details are on the WCAG 2.1 AA checklist for PDFs.
| WCAG 2.1 success criterion | What a machine check tests | What needs a person |
|---|---|---|
| 1.1.1 Non-text Content (A) | Images have alt text and it is not a placeholder | Whether the alt text is accurate |
| 1.3.1 Info and Relationships (A) | The document is tagged; tables have header cells; no untagged content | Whether the tag types are correct |
| 1.3.2 Meaningful Sequence (A) | Not fully testable by a machine | Reading order, with a screen reader or the Reading Order tool |
| 1.4.3 Contrast (AA) | Not covered by PDF/UA | A person or a contrast tool |
| 2.4.2 Page Titled (A) | A document title is set and shown in the title bar | Whether the title is descriptive |
| 2.4.4 Link Purpose (A) | Link annotations have a description | Whether the visible link text makes sense |
| 3.1.1 Language of Page (A) | A document language is set | Whether it matches the text |
| 4.1.2 Name, Role, Value (A) | Form fields have a name | Whether the name and instructions make sense |
What does PDF/UA conformance not guarantee?
Conformance to PDF/UA does not by itself ensure that a document’s content is accessible. The PDF Association lists cases it does not cover: colour or contrast used in an inaccessible way, scripts that produce inaccessible results, and text that is hard to use for people with certain cognitive impairments.
Reading order and the accuracy of alt text are also human checks in PDF Checkup’s reports. Treat a clean machine check as a to-do list that is finished, not as proof of compliance.
How do I check whether a PDF meets PDF/UA-1?
Run it through a PDF/UA validator. veraPDF is an open-source validator with a PDF/UA-1 profile, and PDF Checkup runs the full PDF/UA-1 machine-checkable rule set with veraPDF in the browser, free for files up to 30 pages and 20 MB, with the pages affected and the WCAG 2.1 criteria each failure maps to.
PDF Checkup tests PDF/UA-1 only. For other free options, see the comparison of free PDF accessibility checkers.
How much does PDF Checkup cost?
PDF Checkup is free to check a PDF of up to 30 pages and 20 MB, and fixing a PDF costs $29 for a 50-page pack or $99 for a 300-page pack, paid once and valid 12 months.
Free checker
$0
- WCAG 2.1 AA and PDF/UA-1 report on screen
- Issues by page, in plain English
- Up to 30 pages and 20 MB per file
- No account, files deleted after the check
Remediation packs
- Automatic fixes: title, language, link descriptions, tab order, tagged flag
- AI-suggested alt text for images, reviewed by you before it is written into the file
- Downloadable compliance report PDF (WCAG 2.1 AA and PDF/UA-1 results; the report itself passes PDF/UA-1)
- Files up to 500 pages and 60 MB. One credit per page, charged once per document
- No subscription. 14-day refund if you change your mind
Frequently asked questions
Does a PDF/UA PDF automatically meet WCAG?
No. The PDF Association says conformity to PDF/UA does not necessarily ensure the accessibility of a document’s content, and a gap analysis it hosts notes that WCAG has requirements, such as detailed text contrast, that PDF/UA does not.
Is the PDF/UA standard free to read?
The PDF Association offers ISO 14289-1 at no cost as part of its PDF/UA bundle, according to its ISO 14289-1 page read on 2026-11-20.
What is the difference between PDF/UA-1 and PDF/UA-2?
PDF/UA-1 is ISO 14289-1:2014 and applies to PDF 1.7 files. PDF/UA-2 is ISO 14289-2:2024, completely revised for PDF 2.0 and based on the PDF Association’s WTPDF specification.
Is PDF/UA required by law?
A 2021 PDF Association presentation said that WCAG validation is a legal requirement while PDF/UA is not. Rules differ by country and sector and change, so check the one that applies to you; this site does not give legal advice.
Does passing this checker make my PDF ADA or WCAG compliant?
No automated tool can prove that. Machine checks catch missing tags, titles, language, alt text and many PDF/UA errors, but a person still has to confirm reading order, alt text quality, colour contrast and meaningful link text. Use the report as your to-do list and keep a human review step. This site does not give legal advice.