Is PDF/UA a legal requirement?

PDF/UA is not itself a law, but it is the recognised technical standard for accessible PDFs. The European Accessibility Act requires digital documents to meet EN 301 549, which references PDF/UA as the applicable standard for PDF files. Organisations subject to the EAA are therefore expected to produce PDF/UA-conformant documents.

What is the difference between PDF/UA-1 and PDF/UA-2?

PDF/UA-1 (ISO 14289-1) is the original and most widely adopted version, based on PDF 1.7. PDF/UA-2 (ISO 14289-2), published in 2024, is based on PDF 2.0 and introduces additional requirements around tag namespaces and structure. Most current tooling and compliance frameworks still reference PDF/UA-1.

Can automated tools check for PDF/UA conformance?

Automated validators such as PAC (PDF Accessibility Checker) and Adobe Acrobat's accessibility checker can identify many PDF/UA failures. However, some requirements including alternative text quality, logical reading order, and the correct use of table headers require human review to assess accurately. Automated checks are a starting point, not a complete audit.

How does ComplyLoft help with PDF/UA conformance?

ComplyLoft's PDF Accessibility Remediation product processes your documents to apply the tag structure, reading order, alternative text, and metadata required by PDF/UA. All outputs must be reviewed before sign-off, as automated remediation alone cannot guarantee conformance for every document type.

PDF Accessibility Standards

The PDF/UA Standard Explained

PDF/UA (ISO 14289-1) is the definitive international standard for accessible PDF documents. It sets out exactly what a PDF must contain to be usable by people with disabilities and compatible with assistive technologies such as screen readers.

GET A DEMO

What the standard requires

What is PDF/UA?

PDF/UA stands for PDF Universal Accessibility. Published by ISO as ISO 14289-1, it defines the technical requirements a PDF must meet to be considered accessible. Unlike WCAG, which is written primarily for web content, PDF/UA is designed specifically for the PDF format.

PDF/UA requires all meaningful content to carry semantic tags, so screen readers can interpret headings, paragraphs, lists, tables and figures correctly
Every image and non-text element must have alternative text that conveys its meaning, or be marked as decorative
The document must define a logical reading order that assistive technologies can follow, regardless of visual layout
Tables must include properly scoped header cells so screen readers can associate data with the correct row and column context
The document must carry XMP metadata confirming its PDF/UA conformance, including a document title set to display in the title bar

Human Validation

Passing a basic accessibility check is not the same as PDF/UA conformance

Many automated checkers test for common errors but do not verify full PDF/UA conformance. A document can pass a basic scan and still fail PDF/UA requirements. For example, it may have tags present but in the wrong reading order, or include tables without properly defined header scopes. Full conformance requires both technical validation and human review of the tag structure, reading order, and alternative text quality.

The three technical pillars

What PDF/UA actually checks

PDF/UA conformance is assessed across three core areas. Each one addresses a different aspect of how assistive technologies interact with a document, and all three must be met for a document to be considered fully conformant.

Tag Structure and Semantics

Every element in a PDF/UA document must be tagged with the correct role: H1, P, Table, Figure and so on. Tags allow assistive technologies to understand the meaning and hierarchy of content, not just its visual appearance.

LEARN MORE

Logical Reading Order

The tag tree must reflect the intended reading sequence of the document. If the visual layout and the tag order do not match, screen readers will read content in the wrong order, even if the document looks correct on screen.

LEARN MORE

Metadata and Document Properties

A PDF/UA-conformant document must include a document title, have the title set to display in the viewer title bar, and carry XMP metadata that declares its PDF/UA conformance. These properties are checked by PDF/UA validators.

LEARN MORE

About

How the standards fit together

PDF/UA, WCAG, and EN 301 549: understanding the hierarchy

PDF/UA (ISO 14289-1)

PDF/UA is the format-specific standard. It defines the technical requirements for accessible PDF documents and is the primary benchmark used when auditing or remediating a PDF file.

WCAG 2.1 Level AA

Train staff and integrate your systems

The Web Content Accessibility Guidelines provide broader accessibility principles that apply across digital formats. For PDFs, WCAG success criteria are interpreted in the context of PDF/UA. The two standards complement rather than replace each other.

EN 301 549

EN 301 549 is the European accessibility standard for ICT products and services. It references both WCAG 2.1 and PDF/UA as the applicable technical requirements for documents. Meeting EN 301 549 is a recognised route to demonstrating compliance with the European Accessibility Act.

Frequently asked questions

Get started today

Need to bring your PDFs to PDF/UA standard at scale?

GET A DEMO