PDF/UA Explained: ISO 14289 for PDF Files

Updated · 4 min read

On this page
  1. What does PDF/UA require?
  2. What does PDF/UA add over WCAG?
  3. What is the Matterhorn Protocol?
  4. Which PDFs genuinely need PDF/UA?
  5. How do I check conformance with veraPDF?

PDF/UA, formally ISO 14289, is the international standard for accessible PDF files. It defines what a PDF must contain to work with assistive technology: a correct tag structure, a document title, a declared language, text alternatives and a set of rules about how content is encoded. Where WCAG says what accessible content must achieve, PDF/UA says how a PDF file must be built to achieve it, which is why the two are used together.

What does PDF/UA require?

PDF/UA is technical and specific. Its core requirements are:

  • A tag structure that reflects the document’s logical structure, with headings, paragraphs, lists, tables and figures correctly typed.
  • Text alternatives for all meaningful non-text content, and decorative content marked as an artifact.
  • A document title in the metadata and the viewer preference that tells assistive technology to use it.
  • A declared natural language for the document, and for any passage in a different language.
  • Correct encoding of the content, so text is real text rather than an image of text, and so glyphs map to the right characters.
  • A tagged reading order that matches the logical structure.
  • Rules on form fields, annotations and embedded content so none of them is inaccessible.

The point of the standard is that all of this is checkable by a machine against a fixed list of conditions, which is what makes a conformance claim possible at all.

What does PDF/UA add over WCAG?

WCAG 2.1 AA (the WCAG 2.1 specification) is the practical yardstick most organisations are judged against, and it is written for web content generally. PDF/UA is the PDF-specific rulebook. The overlap is large: both require text alternatives, structure and a reading order.

The differences are in emphasis. WCAG includes criteria no automated check can fully confirm, such as whether alt text is meaningful and whether contrast is sufficient in context. PDF/UA is more mechanical, which means it can be validated. That is why a procurement clause or a formal audit will often say “must conform to PDF/UA” rather than “must meet WCAG”, because conformance can be tested. The WCAG and PDFs guide covers the criteria side in detail.

What is the Matterhorn Protocol?

The Matterhorn Protocol is a test framework published by the PDF Association. It breaks PDF/UA down into a list of specific failure conditions, each of which a machine can check. Validators implement it, which is how a tool can produce a line-by-line conformance report instead of a vague verdict. When a validator tells you a figure is missing an alt attribute, or that a structure element is nested incorrectly, it is reporting a Matterhorn condition.

Which PDFs genuinely need PDF/UA?

Not every file does. Two categories are worth separating:

  • Files that just need to be readable. A meeting agenda, a flyer, a press release. Meeting WCAG 2.1 AA, with correct tags and a reading order, is what matters, and that is the bar for most public documents.
  • Files that need PDF/UA conformance. Anything where a contract, a procurement requirement or a regulation names the standard. Binding filings, documents submitted to a formal audit, and vendor deliverables that must conform. Here the claim has to be checkable, so conformance matters in its own right.

The honest advice is to reach for PDF/UA conformance when someone is asking for it by name, and otherwise to aim at a file that reads correctly, which serves users better than chasing a technical badge.

One distinction is worth keeping straight: PDF/UA conformance is about the file, and usability is about the experience. A file can be technically conformant and still contain alt text that says nothing useful, because the standard cannot judge meaning. A conformance claim and a usability test are complements, not substitutes, which is why the PDF accessibility testing guide still matters for a file that passes a validator.

How do I check conformance with veraPDF?

veraPDF is free and open source and validates PDF/UA conformance directly against the Matterhorn conditions. The flow is short:

  1. Run the file through veraPDF and read the conformance verdict.
  2. Note each failed condition and what it refers to: structure, metadata, annotations or encoding.
  3. Fix the failures, either by hand or with a remediation tool, then re-run.
  4. Confirm the readable result with PAC 2024, which gives a human-friendly report, and with a screen reader.

A worked example of a veraPDF failure line and its fix: “Structure element H2 is not permitted as a child of a Figure” means a heading was nested inside an image’s structure, which breaks the outline; the fix is to move the heading out so it sits in the reading order at the right level. Failures like this are common after a rough automatic pass and are quick to correct once named.

TagRight writes the tag structure, reading order, language and title into a PDF you did not author and returns a report of what needs a human, which clears many of the structure failures a validator reports; it is a remediation aid, not a PDF/UA certification, so the file should still be confirmed with veraPDF or PAC. The accessible PDF checklist lists the items to verify, how to remediate a PDF covers the fixing steps, and the free tier is on the pricing page. To see the report on a file of your own, you can tag a PDF free.

Frequently asked questions

What is PDF/UA?

PDF/UA, formally ISO 14289, is the international standard for accessible PDF files. It defines what a PDF must contain to be usable by assistive technology, including a correct tag structure, a document title, a language and text alternatives, and it is the PDF-specific counterpart to WCAG.

What is the difference between PDF/UA and WCAG?

WCAG is written for web content and applies to any document published on the web, including PDFs. PDF/UA is written specifically for PDF files and gives the technical requirements a PDF must meet. A file that conforms to PDF/UA generally satisfies the PDF side of WCAG 2.1 AA, but the two are separate documents.

What is the Matterhorn Protocol?

It is a test framework published by the PDF Association that lists the ways a PDF can fail PDF/UA, as a set of machine-checkable conditions. Validators such as veraPDF implement it, which is how they produce a conformance report.

How do I check if a PDF conforms to PDF/UA?

Use a validator. veraPDF is free and open source and checks PDF/UA conformance directly. PAC 2024 is a free Windows checker from the PDF/UA Foundation that gives a readable pass or fail. Both report; neither repairs the file.

Does every PDF need to conform to PDF/UA?

No. Most documents just need to be readable and to meet WCAG 2.1 AA. PDF/UA conformance matters when a contract, a procurement or a regulation specifically requires it, which is common in government and in formal accessibility audits.

Tag a PDF free