PDF/UA: Why Accessible PDFs Are Now Mandatory

In this article, you’ll learn everything about PDF/UA and how adoc Studio helps you create compliant PDFs with a single attribute.

The New Legal Landscape: What You Need to Know

The European Accessibility Act was adopted as an EU directive back in 2019. Starting in 2022, individual EU member states transposed the directive into national law. The transition period for companies ended on June 28, 2025.

Since then, the EAA has been in force across all EU member states. The directive requires companies to make their digital products and services accessible - including PDF documents such as contracts, invoices, terms and conditions, forms, or manuals.

What Penalties Are at Stake?

Enforcement is handled by individual member states. Penalties vary:

• Germany: Fines up to 100,000 euros for non-compliant products, 10,000 euros for missing accessibility statements
• France: Penalties between 5,000 and 250,000 euros, with possible public disclosure
• Spain: Fines between 5,000 and 300,000 euros
• Ireland: Criminal consequences in severe cases

Additionally, daily penalties of up to 1,000 euros can be imposed for ongoing violations.

Who Is Affected?

The EAA applies to companies of all sizes offering products or services in the EU market:

• E-commerce websites and online shops
• Banking and financial services
• Telecommunications services
• Transportation services
• E-books and e-readers
• Publicly accessible PDF documents

What Is PDF/UA?

PDF/UA (Universal Accessibility) is ISO standard 14289 for accessible PDF documents. Published in 2012, it translates the abstract requirements of WCAG 2.2 (Web Content Accessibility Guidelines) into concrete technical rules for the PDF format. The WCAG are continuously evolving to keep pace with new technologies.

The PDF Association provides important reference documents for PDF/UA-1:

• The Tagged PDF Best Practice Guide for correct use of tags and structure tree
• The Matterhorn Protocol 1.1 as a test model with 31 checkpoints and 136 failure conditions

These documents form the reference framework for tools and audits.

The Core Principles of PDF/UA

The standard is based on one central rule:

“Content shall be marked in the structure tree with semantically appropriate tags in a logical reading order.”
PDF Association

This leads to four guidelines:

1. All meaningful content is tagged
2. Tags are semantically appropriate
3. Reading order is clear and logical
4. Text is machine-readable (Unicode, language, metadata)

The Matterhorn Protocol: 31 Checkpoints for Compliance

The Matterhorn Protocol defines 31 checkpoints with a total of 136 failure conditions. Here are the most important ones:

1. Structure Tree Instead of “Visual Layout”

PDF is traditionally designed for printing. The visual arrangement says nothing about how a screen reader should interpret the content. PDF/UA requires a structure tree that reflects the semantic logic:

• Headings as <H1> through <H6>
• Paragraphs as <P>
• Lists as <L> with <LI>, <Lbl>, and <LBody>
• Tables with <Table>, <TR>, <TH>, <TD>

Typical errors:

• “Headings” created by font size instead of <H1> etc.
• Lists with visual bullets but no list tags
• Tables without table structure tags

2. Logical Reading Order

The screen reader reads the structure tree in a defined order. This must correspond to the logical reading order:

• No “jumps” from incorrectly nested tags
• No tables or images in the middle of a heading
• Content spanning page breaks remains logically one element

3. Document Metadata and PDF/UA Flag

PDF/UA requires specific metadata:

• PDF/UA flag in XMP metadata (pdfuaid:part = 1)
• Document title in metadata (dc:title)
• Display setting “Show title instead of filename”
• Document language declared for all content

4. Heading Hierarchy

• Only one logical main heading (<H1>)
• No skipping levels (e.g., from H2 directly to H4)
• No block structures within headings

5. Tables

Tables are particularly critical for screen readers:

• Use table structure (<Table>, <TR>, <TH>, <TD>)
• Header cells as <TH> with correct Scope attribute
• No layout tables for non-tabular content

6. Images and Alternative Text

• Tag graphics as <Figure>
• Alternative text (Alt) for all meaningful images
• Mark decorative images as artifacts

7. Text, Unicode, and Language

• All characters must map to Unicode
• Language changes must be marked
• Symbol fonts need ActualText or ToUnicode tables

8. Navigation and Forms

• Documents should have bookmarks following the heading structure
• Form fields need programmatically accessible names
• Annotations must appear in the structure tree

9. Fonts and Security

• All fonts must be embedded
• Security settings must not block screen readers
• Sufficient color contrast required

PDF/UA in adoc Studio

:ads-pdf-ua:

ads-pdf-ua

When set, PDF exports add accessibility information according to the PDF/UA standard.

In adoc Studio, you activate PDF/UA mode with a single document attribute.

Once you set :ads-pdf-ua:, the PDF export follows the PDF/UA guidelines.

What You Should Consider as an Author

Even though adoc Studio handles the technical side, there are best practices for you:

Alternative text for images:

image::diagram.png[alt="Bar chart showing revenue development: Q1 10M, Q2 12M, Q3 15M, Q4 18M euros"]

Correct heading hierarchy:

= Document Title

== Chapter 1

=== Section 1.1

=== Section 1.2

== Chapter 2

Table headers:

.Product comparison of widgets by price and availability
|===
| Product | Price | Availability

| Widget A | 29.99 euros | In stock
| Widget B | 49.99 euros | On order
|===

Meaningful link text:

// Avoid
For more information, click link:details.html[here].

// Better
Read our link:details.html[complete product documentation].

Testing and Validation

Accessibility experts recommend:

1. Automated testing with tools like PAC (PDF Accessibility Checker)
2. Manual review of the 47 purely manual criteria in the Matterhorn Protocol
3. Screen reader testing for practical verification

Conclusion: Act Now

PDF/UA is no longer an academic detail but a central building block of digital compliance. Rather than painstakingly “fixing” PDFs for accessibility after the fact, it makes more sense to integrate accessibility into the creation process.

adoc Studio’s PDF/UA mode, activated via :ads-pdf-ua:, implements the guidelines technically while you focus on content. You’re just one switch away from compliant PDFs.

This article is for general information purposes and does not constitute legal advice. For specific legal questions about EAA compliance, please consult a qualified attorney.