What Is PDF/UA and Do I Need It?

PDF/UA is the ISO standard family for accessible PDF documents. It provides technical requirements for PDF structure and semantics. Whether it is the required target for your organization depends on the applicable policy, procurement terms and legal obligations.

What does PDF/UA cover?

Accessible PDF work includes appropriate structure tags, coherent reading order, meaningful image descriptions, language and metadata, usable character mappings and correct table relationships. These features help software convey the document's content and structure.

Adding tags is not enough: their meaning must match the source. A diagram tagged as a paragraph, a table with incorrect header associations or a fluent but inaccurate description can still create barriers.

Automated and human checks serve different purposes

The PDF Association's Matterhorn Protocol lists PDF/UA-1 failure conditions and distinguishes checks that software can establish from those needing human judgment. It explicitly describes the need for human judgment in many areas.

Use a validator that supports the target standard and record its version and results. Then assess meaning, structure, reading order and applicable user tasks. A clean machine report cannot establish every required human judgment.

How does it relate to WCAG?

PDF/UA is a PDF-specific technical standard; WCAG addresses accessibility requirements for covered content and interactions. PDF/UA can support an institution's document-accessibility work, but it does not by itself determine compliance with every WCAG criterion or legal duty.

For US public institutions, consult the DOJ Title II guidance for the applicable WCAG 2.1 AA obligations, compliance cohort and exceptions. For Australian education providers, assess the DDA/DSE obligations and the institution's procurement standards. Do not infer a universal legal requirement for PDF/UA from a general need for accessible documents.

Choose the version deliberately

PDF/UA-1 and PDF/UA-2 have different underlying PDF versions and requirements. Confirm the exact target, validator support, export path and receiving environment with the accessibility team. Avoid declaring that a particular version is universally sufficient or that all tools have the same coverage.

Evaluate a remediation workflow on saved outputs

Keep the original alongside the resulting PDF. Verify that text, mathematics, figures and tables preserve their intended meaning, then inspect the relevant structural and usability checks. Record unresolved issues and the responsible reviewer.

Aelira Core is beta. Its supported PDF checks and partial changes are documented in the format-by-format remediation reference. These capabilities do not establish full PDF/UA certification. Some PDFs need manual work or cannot produce a downloadable remediated file.

Start with authorized representative documents, including difficult cases. Record the software version, configuration, validator findings, manual findings, failures and review time. Use that evidence to decide whether the workflow is suitable for the institution's target rather than relying on a scanner score alone.