Publishing guide
PDF/UA accessibility for publishers
Accessible PDFs are moving from nice-to-have to legal requirement. Here is what PDF/UA asks for and how to meet it in production.
PDF/UA, WCAG and the law
WCAG describes accessibility outcomes for digital content in general; PDF/UA specifies how a PDF must be constructed to achieve them. For publishers the practical driver is regulation: the European Accessibility Act extends accessibility obligations to many digital products and publications, so tagged, accessible output is increasingly required rather than optional.
What a PDF/UA-compliant file needs
- Tag structure — every element tagged (headings, paragraphs, lists, figures) with a correct logical reading order.
- Alternative text for images and meaningful graphics; artifacts marked so decorative elements are skipped.
- Tagged tables with proper header associations.
- Document language set, and language changes marked inline.
- Navigation — bookmarks, a document title shown in the window, and no reliance on colour alone.
- Full Unicode text (no image-of-text), so content is selectable and readable.
Producing it at scale
Accessibility is far cheaper when it is built into production, not bolted on. An XML-first workflow (JATS/BITS) carries structure and alt-text through to a tagged PDF and an accessible EPUB from one source, rather than remediating finished files one by one. Where legacy PDFs must be fixed, remediation tags the existing file and validates it against the standard — slower, but necessary for back-catalogue compliance.
How B2K helps
B2K produces PDF/UA-aware, tagged output as part of its XML-first book and STM workflow, and remediates existing PDFs to the standard, with validation before delivery.
“The cheapest accessible PDF is the one you tag at source. Remediating a finished back-catalogue works, but building structure in from the XML is an order of magnitude less effort.”Prashanth Krishna, Practice Head — Content Transformation & Regulatory Operations, B2K
Talk to B2K about your project
Tell us the scope and the deadline, and we will scope the work and commit to a date we can hold.
Start a project →Frequently asked questions
What is PDF/UA?
PDF/UA (ISO 14289) is the international standard for universally accessible PDF. It defines how a PDF must be tagged and structured — reading order, headings, alt text, tagged tables, language and navigation — so assistive technologies such as screen readers can interpret it correctly.
What is the difference between PDF/UA and WCAG?
WCAG sets general accessibility outcomes for digital content; PDF/UA specifies how a PDF file must be built to meet them. In practice they are used together: PDF/UA is the PDF-specific technical standard, WCAG the broader success criteria.
Does the European Accessibility Act require accessible PDFs?
The European Accessibility Act extends accessibility obligations to many digital products and publications, which for publishers increasingly means tagged, accessible output such as PDF/UA and accessible EPUB. Exact scope depends on the product and member-state implementation, so confirm your obligations for each market.
Can existing PDFs be made accessible?
Yes. Legacy PDFs can be remediated — tagged, given reading order and alt text, and validated against PDF/UA — though it is more labour-intensive than building accessibility into the source. For ongoing titles, an XML-first workflow produces accessible output directly.