7 min read

PDF/UA Explained: The ISO 14289 Standard in Plain English

PDF/UA stands for "PDF/Universal Accessibility." It is the international standard — published as ISO 14289-1 — that defines what makes a PDF accessible to people using assistive technology. If WCAG is the general rulebook for digital accessibility, PDF/UA is the PDF-specific implementation of those rules.

What PDF/UA requires

At its core, PDF/UA requires that a PDF be fully and correctly tagged so that assistive technology can understand its structure and content. The headline requirements are:

  • All real content is tagged, and decorative content is marked as an artifact.
  • Content has a logical, defined reading order.
  • Document structure uses appropriate semantic tags (headings, lists, tables, figures).
  • Images and other non-text content have alternative descriptions.
  • Tables use proper header cells and associations.
  • The document declares its primary language and has a meaningful title.
  • Fonts are embedded so text can be extracted reliably.
  • The file is flagged as PDF/UA conformant in its metadata.

How PDF/UA relates to WCAG

WCAG (Web Content Accessibility Guidelines) is technology-neutral — it applies to web pages, apps, and documents alike. PDF/UA takes the relevant WCAG principles and specifies exactly how to satisfy them within the PDF format. In practice the two overlap heavily: a PDF that conforms to PDF/UA will satisfy most applicable WCAG 2.1 success criteria, and vice versa.

A useful way to think about it: WCAG tells you the goal (perceivable, operable, understandable, robust); PDF/UA tells you the specific PDF mechanics that get you there.

The Matterhorn Protocol

Because ISO 14289 is written for software implementers, the PDF Association created the Matterhorn Protocol — a set of 31 "checkpoints" broken into 136 failure conditions — to make PDF/UA testable. Accessibility checkers map their tests to these checkpoints, which is why a checker report often reads like a list of specific, granular failures.

How to make a PDF PDF/UA compliant

  1. 1Tag the document completely (auto-tag, then correct it) or export tags from a well-structured source file.
  2. 2Verify and fix the reading order so it matches the visual flow.
  3. 3Add alt text to meaningful images and artifact the decorative ones.
  4. 4Give tables proper header cells and associations.
  5. 5Set the document title and primary language, and embed all fonts.
  6. 6Validate against PDF/UA with an automated checker, then confirm with a screen reader.

You can run a free PDF/UA and WCAG 2.1 AA check on this site to see exactly which checkpoints a document passes or fails before you invest time in remediation.

Check your PDF for free

See exactly which PDF/UA and WCAG 2.1 AA issues your document has — instant, no signup.

Check My PDF

Frequently asked questions

What does PDF/UA stand for?
PDF/UA stands for "PDF/Universal Accessibility." It is published as ISO 14289-1 and defines how a PDF must be structured so people using assistive technology can access it.
Is PDF/UA the same as WCAG?
No, but they overlap heavily. WCAG sets technology-neutral accessibility goals; PDF/UA specifies exactly how to meet them inside the PDF format. A PDF that conforms to PDF/UA will satisfy most applicable WCAG 2.1 success criteria.
How do I make a PDF PDF/UA compliant?
Tag the document completely, fix the reading order, add alt text and artifact decorative images, give tables proper header cells, set the title and language, embed all fonts, then validate with an automated checker and confirm with a screen reader.
What is the Matterhorn Protocol?
It is a set of 31 checkpoints broken into 136 failure conditions, created by the PDF Association to make the PDF/UA standard testable. Accessibility checkers map their tests to these checkpoints, which is why their reports read as granular pass/fail lists.

Related how-to fixes