What Is PDF/UA? The Accessible PDF Standard Explained
PDF/UA (ISO 14289) is the standard for universally accessible PDFs. Learn what it requires, how it differs from tagged PDF, and why it matters for accessibility compliance.
PDF/UA — where UA stands for Universal Accessibility — is the ISO standard (ISO 14289-1) that defines what makes a PDF file accessible to people with disabilities, particularly those using assistive technologies such as screen readers. It builds on the concept of Tagged PDF by specifying not just that tags exist, but how they must be structured and what they must contain.
What Accessibility Means for PDFs
An accessible PDF is one that can be reliably read and navigated by assistive technology. For a screen reader like NVDA, JAWS, or VoiceOver, it needs to be able to determine the reading order of content, understand which text is a heading vs body paragraph vs figure caption, read alternative text for images, and navigate form fields. Without proper structure, a screen reader may read content in the wrong order, skip content entirely, or output meaningless sequences of characters.
Core PDF/UA Requirements
- The document must be fully tagged with a logical structure tree
- All tags must follow the correct hierarchy: document → section → paragraph, not flat or arbitrary nesting
- All images and non-text content must have meaningful alternative text (not just filename or empty alt)
- All headings must use proper heading tags (H1, H2, H3) in a logical order
- Reading order in the structure tree must match visual reading order
- Tables must have header cells tagged as TH with scope attributes
- Forms must have labels associated with every form field
- No content must be present only as background (artifact vs actual content must be correct)
- Document language must be specified
- No security settings that prevent assistive technology access
PDF/UA vs. Tagged PDF
Tagged PDF is a prerequisite for PDF/UA, but not sufficient on its own. A PDF can be "tagged" — meaning it has a structure tree — but still fail PDF/UA if the tags are wrong, in the wrong order, or missing required attributes. Think of Tagged PDF as the foundation and PDF/UA as the full accessibility specification built on top of it. Most PDFs exported from Microsoft Word or Adobe InDesign are tagged, but may not be PDF/UA compliant without additional remediation work.
Why PDF/UA Matters Legally
In many jurisdictions, documents published by government agencies and large organizations must meet accessibility standards. In the US, Section 508 of the Rehabilitation Act requires federal agencies to ensure their electronic documents are accessible. The EU Web Accessibility Directive (EN 301 549) extends similar requirements to public sector bodies. PDF/UA compliance is increasingly used as the benchmark for demonstrating that a PDF meets these legal requirements. Failure to comply can result in complaints, investigations, and legal penalties.
How to Create PDF/UA Compliant Files
Start with well-structured source documents using proper heading styles in Word or paragraph styles in InDesign. Export using the accessibility-focused PDF export settings. Then use Adobe Acrobat Pro's Accessibility Checker to find and fix remaining issues — often this involves adding alt text to images, fixing reading order, and correcting table structure. The PAC (PDF Accessibility Checker) tool, available free from the Access For All foundation, provides the most thorough PDF/UA validation available.
Try Edit Pages Now — Free
Browser-based, private, and instant. No account or software required.
Open Edit Pages