Germany Standardises on PDF/UA for Government Documents

By Michael Peters · Published March 28, 2026

← Back to Blog

What Happened

Germany has formally standardised on PDF/UA (ISO 14289) for government digital documents. The decision, reported by the PDF Association, means that official German government PDFs must now conform to the PDF/UA accessibility standard — ensuring that digital documents are readable by people with disabilities using assistive technologies such as screen readers.

This is one of the most significant government-level endorsements of PDF/UA to date. Duff Johnson, who has been involved in developing and maintaining the PDF/UA standard since 2004, described the decision as a major milestone for the accessibility community.

What is PDF/UA?

PDF/UA (Universal Accessibility) is the ISO standard that defines requirements for accessible PDF documents. Published as ISO 14289-1, it specifies how PDF files must be structured so that assistive technologies — screen readers, magnifiers, and alternative input devices — can correctly interpret and present the content to users with disabilities.

Key requirements of PDF/UA include:

• Tagged structure: Every piece of content must be enclosed in semantic structure tags (headings, paragraphs, lists, tables, figures) that define what each element is, not just how it looks.
• Reading order: The logical reading order must be explicitly defined and correct, independent of the visual layout on the page.
• Alternative text: All non-text content (images, charts, diagrams) must have alternative text descriptions.
• Table markup: Data tables must have properly defined header cells and row/column associations.
• Language specification: The document language must be declared, and language changes within the text must be tagged.
• Navigation: Bookmarks must be provided for documents with more than one page, reflecting the document structure.

For a deeper dive into these requirements, see our comprehensive guide to PDF accessibility.

Why This Matters Beyond Germany

Germany is the largest economy in the European Union, and its government procurement decisions have a ripple effect across the continent. When Germany mandates a standard for its own documents, organisations that work with German government agencies — contractors, suppliers, consultants, and international partners — must also comply.

This decision follows a broader European trend. The European Accessibility Act (EAA), which comes into full effect in June 2025, requires that digital products and services across the EU be accessible. PDF/UA is the definitive technical standard for achieving this in PDF documents. Germany’s explicit adoption sends a clear signal: PDF/UA is not optional for organisations operating in the EU public sector.

Other countries and regulatory bodies are likely to follow. The United States already requires accessible documents under Section 508, and PDF/UA is increasingly referenced as the technical benchmark for compliance. The UK’s public sector has similar requirements under the Public Sector Bodies Accessibility Regulations 2018.

What This Means for Your Organisation

If you produce PDFs for government agencies, regulated industries, or public-facing distribution, PDF/UA compliance is increasingly becoming a requirement rather than a nice-to-have. Here’s what you should be doing:

1. Audit Your Existing Documents

Start by checking whether your current PDFs meet PDF/UA requirements. Many organisations are surprised to discover that their documents — even those produced by professional design teams — fail basic accessibility checks because they lack proper tagging, reading order, or alternative text.

2. Fix Your Document Creation Workflow

The most effective approach to PDF/UA compliance is to fix the source. Documents exported from Microsoft Word, Adobe InDesign, or other publishing tools can produce tagged, accessible PDFs — but only if the source document uses proper styles, heading levels, and image alt text. Retrofitting accessibility into an untagged PDF is significantly more expensive than building it in from the start.

3. Automate What You Can

For organisations producing large volumes of PDFs, manual accessibility remediation is not scalable. Automated tools for bookmark creation, table of contents generation, and metadata management can handle the structural requirements at scale. Mapsoft’s Bookmarker and TOCBuilder plugins automate two of the most common PDF/UA requirements — bookmarks and navigation structure — directly within Adobe Acrobat.

4. Validate Before Publishing

Run every PDF through an accessibility checker before distribution. Adobe Acrobat Pro includes a built-in accessibility checker (Tools > Accessibility > Full Check), and veraPDF provides an open-source validation option. For batch validation, our free Check PDF Standards plugin can scan entire folders.

The Role of PDF/UA-2

It’s worth noting that an updated version of the standard — PDF/UA-2 (ISO 14289-2) — was published in 2024. PDF/UA-2 is based on PDF 2.0 (ISO 32000-2) and aligns with WCAG 2.1 guidelines. The new version adds requirements for mathematical content (MathML), improved table semantics, and better handling of complex document structures. Organisations starting new accessibility programmes should aim for PDF/UA-2 where tooling supports it.

Further Reading

• PDF Accessibility: Creating Accessible Documents — our comprehensive guide to tagged PDFs, WCAG, and PDF/UA
• PDF/A: The Archival PDF Standard — often required alongside PDF/UA for government documents
• Tagged PDFs: Definition, Usage and Examples — understanding the foundation of PDF accessibility
• PDF Association: German Government Standardizes on PDF/UA — the original announcement