PDF Remediation & Document Accessibility Services

A PDF that looks fine on screen can be completely unusable to someone relying on a screen reader — no reading order, untagged headings, images with no description, tables that read as a jumble. For government agencies, schools, and their vendors, that’s now a compliance problem as well as an access one.

Taika Translations remediates the documents organizations actually publish — PDFs, Word, and PowerPoint — so they meet WCAG 2.1 AA, Section 508, and the PDF/UA standard for accessible PDFs, with a VPAT or conformance report available on request. One file that needs fixing? Get a remediation price — one short form, and if you run it through the free PDF accessibility checker first, the results travel with you. A backlog is cheaper to scope as a whole: start with the free accessibility assessment and a sample of your documents, and Taika will scope the remediation; for web pages, media, and broader program work, see Section 508 remediation and the full accessibility and compliance services.

Not sure where a document stands? Run it through our free PDF Accessibility Checker — upload a PDF and get an instant Section 508, ADA, and WCAG audit with pass/fail results and remediation guidance. Your file is analyzed in your browser and never uploaded.

Accessibility services for legal documents

Legal documents are the hardest category of PDF to remediate, and the one where a failure is most visible. A brief, an exhibit bundle, or a contract typically arrives as a mix of born-digital text and scanned pages with no text layer at all — and a scan is not a document to a screen reader, it is a picture. Before anything can be tagged, the scan needs optical character recognition and a human check against the original, because OCR that silently misreads a figure in a damages table has introduced an error into the record rather than fixing an access problem.

The structures that make legal documents legally useful are also the ones that break most often:

• Footnotes and endnotes, which must be reachable from the point of reference rather than stranded at the end of the reading order.
• Bates numbering and running headers, which should be marked as artifacts so a screen reader does not announce a number between every sentence.
• Exhibit and appendix tables, where a missing header-cell association turns a structured table into an unordered stream of values.
• Signature blocks, notary sections and attestations, which carry meaning from their layout and lose it when the tag tree flattens them.
• Redactions, which must be genuine removals in the content stream — a black rectangle drawn over text leaves the text underneath, readable to anyone with a screen reader or a copy-paste.
• Cross-references and internal citations, which should remain navigable links rather than becoming plain text.

Taika remediates court filings and exhibit sets, contracts and agreements, policies and public notices, discovery productions, and the administrative records that public bodies publish. Where the same document also needs to reach limited-English-proficient readers, remediation and certified translation can run as one project — which matters, because a translated document is a new file and inherits none of the tagging from the original. Doing them separately means paying to remediate twice.

Which standard actually applies to you

These are routinely conflated, including by vendors. They are different standards with different triggers, and getting this wrong is how organisations remediate to the wrong target.

Section 508 of the Rehabilitation Act — federal agencies and their contractors. The Access Board’s ICT Accessibility Standards incorporate WCAG 2.0 Level A and AA by reference: E205.4 provides that “Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.” ⚠ Section 508 is a WCAG 2.0 AA obligation, not 2.1 — a widely repeated error. It is an ongoing obligation with no future compliance date, because it is already in force.

ADA Title II — state and local government. The Department of Justice’s 2024 web and mobile accessibility rule sets WCAG 2.1 Level AA, and the dates were extended by the April 2026 interim final rule. Public entities serving 50,000 or more people must comply by April 26, 2027; public entities under 50,000 and special district governments by April 26, 2028. Title II reaches state and local government bodies, which includes state court systems, public universities, school districts and municipal agencies.

Section 504 — recipients of HHS federal financial assistance, including most hospitals and clinics. Also WCAG 2.1 Level AA, also extended in 2026: recipients with 15 or more employees by May 11, 2027, and those with fewer than 15 by May 10, 2028.

PDF/UA (ISO 14289-1) is not a legal mandate but the technical specification for what an accessible PDF is — the tag structure, the semantics, the metadata. WCAG tells you the outcome; PDF/UA tells you how a PDF has to be built to get there. A file can pass an automated WCAG checklist and still be unusable, which is why conformance should be stated against both.

Private law firms sit in a genuinely unsettled area, and anyone telling you otherwise is overselling. ADA Title III covers places of public accommodation, and whether — and how far — it reaches a private firm’s documents and website has been litigated inconsistently across circuits without a controlling federal web rule. What is not unsettled: a firm filing with a federal agency, contracting with the government, or serving a public-entity client inherits that client’s obligation through the work product. In practice that is what drives most law-firm remediation, not Title III.

What “tagged” means, and why an untagged PDF fails

A tagged PDF carries a structure tree — a parallel, invisible description of what each piece of content is: this is a level-2 heading, this is a list item, this is a table header cell governing this column, this image is decorative and should be skipped. Assistive technology reads that tree, not the visual layout.

An untagged PDF has no tree, so a screen reader falls back to guessing from the order objects were written into the file — which is frequently not the order a human reads them. That single root cause produces most of what an audit reports downstream: no heading navigation, columns read across instead of down, tables announced as a run of unlabelled values, images silently skipped or read as a filename.

This is testable before you buy anything. Taika’s free PDF accessibility checker runs 14 checks in your browser — the file never leaves your machine — and returns a scored report citing the specific WCAG success criteria and Section 508 provisions each failure maps to. An untagged file typically comes back in the 30–40% range with missing tag structure named as the root cause.

What remediation does not cover

Remediation makes an existing document accessible. It does not rewrite the document, and there are limits worth stating plainly before a project starts:

• A document whose meaning depends on a complex diagram may need a text alternative or a long description that only the author can write accurately. Taika will identify where one is required.
• Scanned pages of poor quality may not OCR reliably. Where text cannot be recovered with confidence, that is reported rather than guessed at.
• A conformance report describes the file as delivered. Editing a remediated PDF afterwards — even adding a page — can break the tag tree, so re-checking after any change is part of maintaining conformance, not a separate defect.
• No vendor can certify that an organisation is “ADA compliant.” Conformance is assessed per document against a named standard; an organisation’s overall legal posture involves its whole programme and is a question for its counsel.