5 min read

PDF/UA vs WCAG: How They Differ and Overlap

PDF/UA and WCAG come up together constantly, and it is easy to assume you have to choose between them. You do not — they address PDF accessibility from two complementary angles, and a well-made PDF satisfies both.

WCAG: the technology-neutral goals

WCAG (Web Content Accessibility Guidelines) defines what accessible content must achieve — perceivable, operable, understandable, robust — across web pages, apps, and documents alike. It is the standard most laws reference, but it is not specific to PDFs.

PDF/UA: the PDF-specific mechanics

PDF/UA (ISO 14289) takes those goals and specifies exactly how to meet them inside the PDF format — how to tag content, mark artifacts, structure tables, and flag conformance. It is the implementation detail WCAG leaves open.

Where they overlap

  • Both require meaningful structure and tags.
  • Both require alt text for images and proper table headers.
  • Both require a logical reading order and a defined language.
  • A PDF that conforms to PDF/UA will satisfy most applicable WCAG 2.1 AA criteria.

A simple way to remember it: WCAG tells you the goal; PDF/UA tells you the PDF mechanics that get you there. Aim for both.

Which one do you need?

Most legal regimes reference WCAG 2.x Level AA, so that is the compliance target. PDF/UA is how you reliably hit it in a PDF, and checkers test against both at once.

Run a free check on this site to see your document scored against PDF/UA and WCAG 2.1 AA together.

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

Do I need both PDF/UA and WCAG?
Effectively yes, and meeting one largely gets you the other. WCAG is the compliance target most laws reference; PDF/UA is the implementation standard that tells you how to reach it inside a PDF. Accessibility checkers test against both at once.
What is the main difference between PDF/UA and WCAG?
WCAG is technology-neutral and describes what accessible content must achieve across web, apps, and documents. PDF/UA (ISO 14289) is PDF-specific and describes exactly how to tag, artifact, and structure a PDF to meet those goals.
If my PDF is PDF/UA compliant, is it WCAG compliant?
It will satisfy most applicable WCAG 2.1 AA success criteria, because PDF/UA implements the same requirements in PDF terms. A few WCAG criteria still rely on human judgment (such as whether alt text is meaningful), so a short manual review is still worthwhile.

Related how-to fixes