PDF remediation – PDF/UA-compliant files from a single document to entire archives

PDF remediation: what it involves and what EU and US rules require of your documents

Legal status as of November 10, 2026. US deadlines and the European standard for documents are both in motion; we update this section when they change.

PDF remediation means repairing an existing PDF so that people who use screen readers, magnification or keyboard navigation can work with it. If you still have the Word or InDesign source and publish new editions regularly, fixing the template is often the better investment; our PDF/UA guide describes that route. Remediation is for everything else: the archive, files whose source is long gone, and volumes no team can rebuild by hand.

What PDF remediation actually involves

• Structure: a complete tag tree in which headings, lists, tables, footnotes and links are marked up as what they are.
• Reading order: columns, sidebars, captions and footnotes are read in the order the author intended.
• Tables: header cells are linked to their data cells, so a row still makes sense when read aloud.
• Images and charts: alternative text conveys what an image says; decorative elements are marked as artifacts so screen readers skip them.
• Forms: labeled fields, a logical tab order and instructions that are announced.
• Metadata: document title, document language and changes of language within the text.
• Visual criteria: color contrast and information conveyed by color alone. PDF/UA does not cover these, WCAG does.

Scanned pages need text recognition first. Some problems cannot be fixed inside the PDF at all: if a chart only works in color, the honest answer is to change the chart in the source, and a good remediation service tells you so.

Automated vs. human-reviewed remediation

Software is very good at the mechanical part: detecting structure, generating tags, applying one fix across thousands of pages and checking machine-testable PDF/UA criteria. It cannot decide whether an alternative text describes what matters in a chart, whether the reading order makes sense of a complicated layout, or whether a bold line is a heading or just emphasis. That is not the weakness of one tool: 60–70% of WCAG criteria cannot be tested automatically.

That is why Access Doc works in two stages. Automated conversion to PDF/UA provides speed and consistency; people then review the document wherever judgment is needed. Fully automatic “instant compliance” sounds attractive, but it leaves every judgment call to the person least able to absorb a mistake: the reader who depends on a screen reader.

What you receive: PDF/UA-compliant files and a conformance report per document

For every document, you get back a PDF/UA-compliant file that has been checked against WCAG criteria, together with a conformance report for that document. The report records what was checked, with what result, and where a point needs a decision from you. Alternative texts can be reviewed and edited in the alt text editor before you publish.

Be clear about what such a report is: the documented test result for one file. It is not a certificate, it does not prove legal compliance, and it says nothing about your website or software. There is no official ADA certificate for documents either, which is why you will not find that promise here.

Volumes and workflows: single files, bulk and API

The process is the same for one contract or an entire archive, and single files are uploaded and downloaded directly. For larger inventories, depending on the plan, a document library, bulk operations and an approval workflow let a team assign, review and release documents. Organizations that publish continuously can connect their document or publishing systems through the API and webhooks, so new files are remediated before they go online.

Before you remediate everything, sort. Most inventories we see contain outdated versions, duplicates and files nobody opens. I would split documents into three groups: those people need to use a service (applications, forms, terms, statements), current information, and archive material. Remove what nobody needs, start with the first group, and use the free Access Read check to see where the rest stands.

For US buyers: Section 508, ADA Title II and Section 504

Where US federal rules set a standard, the yardstick for documents is WCAG, not PDF/UA. The version depends on the rule:

• Section 508 (federal agencies, and vendors through procurement): the Revised 508 Standards require WCAG 2.0 Level A and AA, including for documents; four criteria (Bypass Blocks, Multiple Ways, Consistent Navigation, Consistent Identification) do not apply to non-web documents (the W3C’s WCAG2ICT guidance explains how WCAG applies to them). The Access Board did not accept PDF/UA-1 as an alternative, because WCAG 2.0 can serve as the sole standard for PDF files and PDF/UA-1 cannot. A PDF/UA pass alone is not the 508 test. More on our Section 508 page.
• ADA Title II (state and local government): WCAG 2.1 Level AA under the DOJ rule of April 2024, documents included. An interim final rule of April 20, 2026 moved the deadlines to April 26, 2027 (population of 50,000 or more) and April 26, 2028 (smaller entities and special districts). The National Federation of the Blind sued against the delay on May 21, 2026; no decision was known as of November 10, 2026. Older documents can be exempt, but according to the DOJ fact sheet not if people still use them to apply for or access a service, and not once they are updated. See our ADA Title II page.
• Section 504 (recipients of HHS funding): WCAG 2.1 Level AA, with deadlines on May 11, 2027 (15 or more employees) and May 10, 2028. When extending them, HHS cited counties reporting that “time-consuming and costly remediation of PDF documents” remained an obstacle (interim final rule, May 2026).

For private businesses under ADA Title III, the regulations set no technical standard: the DOJ’s 2022 guidance calls WCAG “helpful guidance”, and in February 2026 the DOJ told a court it does not endorse WCAG as the necessary standard under Title III. More on what the ADA and Section 508 actually require of PDFs. Federal buyers usually ask for an Accessibility Conformance Report (ACR) based on the ITI VPAT template; for websites and apps, Access Ready documents its audit results as an ACR on request.

For EU buyers: EAA, national laws and PDF/UA

Since June 28, 2025, the European Accessibility Act has applied to consumer services such as e-commerce, banking, e-books and passenger transport, including providers outside the EU that serve EU consumers. Documents that form part of a covered service are included; only office file formats published before June 28, 2025 are exempt. How far this reaches for each document type is still an open legal question. National laws such as Germany’s BFSG implement the act; public bodies are covered by the Web Accessibility Directive (EU) 2016/2102.

The technical reference is EN 301 549, which has its own chapter for non-web documents such as downloadable PDFs. Under the Web Accessibility Directive, the harmonized version is V3.2.1, based on WCAG 2.1 AA; under the EAA, no harmonized standard had been cited as of November 10, 2026. Version 4.1.1, published on September 2, 2026, adopts WCAG 2.2 AA; it gives a presumption of conformity only once it is cited in the Official Journal of the EU. PDF/UA (ISO 14289) is not named in the EAA. It defines the internal structure of a PDF and is what checkers such as PAC test against. That is why Access Doc checks both: PDF/UA for the file, WCAG criteria for what the reader experiences.

How to choose a PDF remediation service

• Which standard, which version? PDF/UA alone, or WCAG criteria too, and WCAG 2.0, 2.1 or 2.2, depending on the rules you answer to?
• Who reviews, and in which language? Alternative text and reading order can only be judged by someone who understands the content.
• What does the report show? A result per document and per criterion is useful. A blanket badge is not.
• Can you test a sample? Send your most difficult file and check the result yourself with a screen reader such as NVDA, JAWS or VoiceOver and with a PDF/UA checker.
• Does the provider tell you when not to remediate? Sometimes fixing the template is the better deal.

Be wary of promises of instant or automatic compliance. The FTC has acted against such claims: in 2025, an overlay vendor agreed to pay USD 1 million over unsubstantiated claims that its tool made websites WCAG-compliant. The same honesty applies to documents.

The simplest start: check a file for free with Access Read, then book a demo to talk about your inventory. For your website itself, start Access Score®.