Editorial note: citation correction from the prior draft
The earlier draft of this article attributed specific findings to ELIA (“organisations with 250+ employees faced the immediate deadline”) and CSA Research (“document remediation represents one of the top three operational gaps in translation supply chains”). Neither claim could be verified against a real, findable ELIA or CSA Research publication. The actual EAA threshold framing is about microenterprise exemption (under 10 employees / EUR 2 million turnover), not a “250+ employees” cutoff. Per the no-invented-citations rule, both attributions have been removed. This version cites the verified EAA enforcement date (28 June 2025) and a real, directly relevant Nimdzi Insights article, “The European Accessibility Act and the language industry,” already on the approved Industry Insights list.
PDF Remediation for LSPs: Why Accessibility Work Doesn’t Survive Translation
A project manager told us recently: “The source was already remediated. I didn’t think we’d need to do it again.”
That’s the gap nobody talks about.
When you hand a remediated PDF to a translation team, the translated PDF starts from zero on accessibility. The language tags are wrong. The reading order does not follow the new text. The alt text is still in the source language, or it is gone entirely. The WCAG 2.1 AA compliance work you paid for on the original document does not follow the content into the translated version. It has to be built again.
Foliage handles PDF remediation alongside multilingual DTP, which means we catch this compliance gap before it becomes a client delivery failure. Most translation companies do not. They remediate the source, hand it to the translator, and assume the work is done. Then the accessibility requirements surprise them at the end.
This article covers why PDF remediation is not a one-time step but a workflow requirement once translation enters the picture, and how to scope remediation into multilingual projects correctly.
New to PDF remediation? Start with our Introduction to PDF Remediation guide, which explains what remediation is, why the EU Accessibility Act matters, and how to identify whether your documents need work. This article assumes those basics and focuses on the translation-workflow gap specifically.
How PDF remediation actually works, and where translation breaks it
PDF remediation is the process of rebuilding a PDF to meet WCAG 2.1 AA and PDF/UA standards. This means adding proper semantic structure: language tags that tell screen readers what language the text is in, a reading order that matches the visual layout, alt text for images, properly tagged tables, bookmarks, and form fields.
For a single-language PDF, this is manageable. A remediation specialist tags every element, defines the reading order, writes alt text, and tests against accessibility standards.
For a multilingual document, the work compounds. The language tag needs to change at every point where the language shifts, per sentence in some formats, per section in others. If the document is an English source with French, German, and Spanish translations side by side, every language block needs its own tag. If a single PDF contains multiple language versions, the reading order has to work for all of them at once.
Here is where translation creates the gap. When a translator receives a remediated PDF, they cannot edit the accessibility layer. They edit the text, the words change, but the structural information sits in a separate layer that most translation tools cannot touch. The translation goes in, the text refreshes, and the accessibility structure becomes orphaned.
The language tags now point to text that no longer matches the original language. The alt text is still in English while the image caption is in French. The reading order was built for the English layout, but the French text expanded by 18% and shifted the images. The bookmarks reference page numbers that changed.
The result: a PDF with new text but old accessibility metadata. Screen readers become unreliable. The document fails compliance audits. The end client, who may be a government agency, healthcare provider, or financial institution with an accessibility mandate, receives a deliverable that does not meet their requirements.
Why this matters for translation companies now
The European Accessibility Act came into force on 28 June 2025, requiring accessibility compliance for digital products and services sold across the EU, including electronic documents. Nimdzi Insights covers the language-industry angle directly: the Act is expected to create a surge in demand for accessible translation, subtitling, and related services, since accessibility and multilingual content sit on the same delivery path for any company serving EU markets in more than one language.
For translation companies, this creates a new liability. If a client asks for a translated PDF that is supposed to meet accessibility standards, whether explicitly stated or implied by the client’s own legal obligations, and the delivered document fails accessibility tests, that is a compliance failure the client then has to remediate, often at real cost and on a deadline they did not plan for.
Most LSPs are starting to build accessibility requirements into their briefs. Fewer know how to cost the re-remediation step, or which vendors actually handle the full workflow rather than treating it as a referral to an outside specialist.
Foliage handles PDF remediation as a core service, not as add-on consulting. This means a single vendor manages the DTP, the translation, and the compliance layer, keeping the accessibility structure intact across all three steps.
The difference between a remediated source and a remediated translation
Understanding this distinction changes how you scope PDF work.
Remediated source PDF: a single-language document that has been through accessibility review, tagged, and tested to WCAG 2.1 AA standards. Ready for use as is.
Remediated translation: the same document, now translated into one or more target languages, with the accessibility structure rebuilt to match the new text, layout, and reading order. Requires a second pass through remediation.
Multilingual remediation: a single PDF containing multiple language versions, with language tags, reading order, and alt text working across all versions at once. The most complex of the three, because the reading order must work for every language block simultaneously.
The mistake most teams make is treating source remediation as complete work and translation as a simple text swap. It is not. Translation changes the document’s structure, text length, image placement, page breaks, and layout logic. The accessibility layer has to adapt to every one of those changes.
This is why some vendors charge separately for remediation per language version. They are doing the work twice, or they should be. If a vendor quotes remediation once and translation separately with no remediation mention in the translation step, ask what happens to the accessibility layer during translation. If they do not have a documented answer, that is your risk flag.
How to scope PDF remediation into your translation brief
When you need a translated PDF that meets accessibility standards, the brief should address three things.
- Source document status
Is the source already remediated? If yes, specify the standard it was remediated to (WCAG 2.1 AA is the baseline for most regulated contexts; PDF/UA is the ISO standard). If no, factor remediation time and cost into the project.
- Target languages and layout
List every language the PDF needs to exist in. Specify whether it is a single document with multiple language blocks or separate PDFs per language. Multi-language single PDFs require more complex remediation, because the reading order and language tagging have to work for every version.
- The compliance requirement itself
Does the end client have a specific accessibility mandate? Government contracts often require WCAG 2.1 AA as a minimum. Healthcare and financial services frequently require higher levels. EU-regulated entities now need EAA compliance. Specify exactly what the document needs to pass.
The remediation vendor should build the accessibility layer as an integral part of the translation delivery, not as an afterthought. That is the difference between a vendor who knows the workflow and one who does not.
Where to prioritize PDF remediation in your workflow
Not every project needs full PDF remediation. It is most critical when the end client is a regulated entity such as government, healthcare, finance, or legal; when the PDF will be publicly distributed or shared with external stakeholders; when the document contains tables, forms, or complex layouts that require proper tagging to be usable; when the source PDF is already remediated and you need to maintain compliance in translation; or when multiple language versions need to coexist in the same PDF.
A Nordic government agency issuing a request for proposals for a multilingual benefits guide in eight languages, with tables, forms, and infographics, is a clear case. A vendor without remediation capability has to subcontract the accessibility work after delivery, adding time and cost. A vendor that handles remediation end to end, including the multilingual layer, submits a complete deliverable on the first pass.
A mid-size LSP asked to translate a quarterly investor report into Spanish and French, from a source PDF that is already remediated, faces the same choice on a smaller scale. Treat remediation as a one-time step, and the translated PDFs fail accessibility audits. Understand that remediation must happen again after translation, and the delivered files pass compliance the first time.
If you are translating a simple text-only PDF for internal use with no accessibility requirement, remediation may be unnecessary. If there is any doubt, it is safer to include it. The cost of fixing an accessibility failure after delivery is higher than the cost of building it in from the start.
What clean delivery looks like for remediated PDFs
When a multilingual PDF comes back from Foliage, it meets a consistent set of criteria: language tags correct for every text block, with proper lang attributes for screen readers; reading order that follows the visual layout in every language version; alt text provided for all images, translated into each target language; tables properly tagged with headers and cell relationships preserved across languages; form fields tagged and functional in every version; and a pass on automated accessibility checks such as axe or PAC.
Every delivery includes a remediation report, which is where the compliance proof actually lives. The report documents an accessibility conformance summary confirming the standard passed and the tool used to test it; a language tagging log showing exactly where each language begins and ends in the document; an alt text inventory listing every image with its translated alt text side by side per language; a reading order verification confirming the tested path makes sense even with language switching; a form field audit where applicable; and a list of issues found and corrected during the process.
This is not a checkbox. It is evidence that the document actually works.
Remediation is a usability requirement, not only a compliance one
Remediation gets framed as a compliance requirement, and it is one. It is also a usability requirement. A properly remediated PDF works better for everyone, not only for screen reader users. Tables are navigable. Forms are fillable. Reading order makes sense. Images have context.
For translation companies serving regulated clients, building remediation into the workflow is not just about legal risk. It is about being the vendor that actually delivers a document that works, in every language it exists in.
Most competitors hand off translation and treat accessibility as the client’s problem afterward. Foliage treats it as part of the delivery, across every language, on every file. That is a differentiator worth naming directly in sales conversations, not something to leave implicit.
Talk to Foliage Solutions about scoping PDF remediation into your next multilingual project.
Leave a Reply