Section 508 Document Remediation Services

Federal, state, and local agencies, along with schools and other organizations that receive public funding, are required to make their electronic documents and information accessible. Taika Translations remediates PDFs, Word documents, and other electronic content to meet Section 508 and WCAG 2.1 AA — the technical standard referenced in the Department of Justice’s ADA Title II accessibility rule. This page focuses on Section 508 conformance for federal agencies, contractors, and publicly funded organizations; if you need a website or web app brought to ADA/WCAG conformance — especially a private business or state/local site — start with ADA & WCAG website accessibility instead.

Have one document that has to be fixed? Get a remediation price — one short form and a fixed cost for that file. For a backlog, start with the free accessibility assessment — tell us about your document types and volume, and Taika will scope exactly what it takes to bring your content into conformance, with document remediation and braille and alternative formats available from the same accountable vendor.

What Section 508 actually requires — and which WCAG version applies

Section 508 of the Rehabilitation Act (29 U.S.C. § 794d) is not advisory, and it does not read the way most procurement summaries describe it. The binding technical text is the Revised 508 Standards at 36 CFR Part 1194, and three provisions decide almost every document question an agency has:

• E205.2 — Public facing. Electronic content published to the public must conform. This is the clause behind nearly every PDF complaint.
• E205.3 — Agency official communication. Content that is not public facing still has to conform when it is official business communicated as an emergency notification; an initial or final decision adjudicating an administrative claim or proceeding; an internal or external program or policy announcement; a notice of benefits, program eligibility, employment opportunity or personnel action; a formal acknowledgement of receipt; a survey questionnaire; a template or form; educational or training materials; or intranet content designed as a web page. So “it’s internal, 508 doesn’t apply” is wrong for anything on that list — which is exactly where most agencies’ unremediated backlog lives.
• E205.4 — Accessibility standard. Electronic content shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.

That last line is the one that quietly wrecks remediation scoping, because Section 508 adopts WCAG 2.0 AA while the DOJ’s ADA Title II rule adopts WCAG 2.1 AA. If you are a federal agency, 2.0 AA is your legal floor. If you are a state or local government — or a federally funded organization that will also answer to Title II — remediating to 2.0 AA now means paying to touch the same files again later. WCAG 2.1 AA is a superset of 2.0 AA, so the sane decision is to remediate once, to 2.1 AA, and satisfy both. Taika scopes to 2.1 AA by default and documents conformance against whichever standard your auditor names. The Title II dates are set out in the ADA Title II deadlines explainer.

There are also six general exceptions, not the two that get repeated — E202.2 Legacy ICT, E202.3 National Security Systems, E202.4 Federal Contracts, E202.5 ICT Functions Located in Maintenance or Monitoring Spaces, E202.6 Undue Burden or Fundamental Alteration, and E202.7 Best Meets. None of them is a budget exception. The two invoked most often come with obligations attached: E202.6.2 requires the responsible agency official to document the basis in writing, and E202.6.3 requires the agency to provide access by an alternative means anyway. Legacy ICT is the narrowest of all — it reaches only content that already complied with the earlier Section 508 standard and has not been altered on or after 18 January 2018.

Section 508 PDF remediation: the ten defects that get a file sent back

Use this as a 508 remediation checklist before you send documents to any vendor, including us. These ten account for the overwhelming majority of files that fail a review after someone has already “made them accessible”:

1. An image-only scan with no text layer. There is nothing to tag. OCR has to come first — and OCR output has to be proofread, not trusted. A mis-recognized digit in a benefits table is a worse failure than no text at all.
2. Auto-tagged, reading order never repaired. Acrobat’s autotag produces a tag tree and a false sense of completion. Multi-column layouts, sidebars and pull quotes get announced in the order the objects were drawn, not the order a person reads them.
3. Decorative images given alternative text. Rules, dividers, watermarks and background shapes belong in artifact tags. Describing them makes a screen reader announce furniture on every page.
4. Data tables with no header cells and no scope. A table needs real header cells with row or column scope. Without them a screen-reader user hears sixty unlabelled numbers and has to guess which column each came from.
5. Form fields with no accessible name and no deliberate tab order. Interactive PDF forms are where agency documents fail most often. Every field needs a name a screen reader can announce, and the tab order has to follow the document structure rather than the order the fields happened to be drawn.
6. No document title and no document language set. Two fields in the document properties, thirty seconds of work, and two of the most common automated failures anywhere. A file with no language set gets pronounced in whatever language the reader’s screen reader defaults to.
7. Running heads, page numbers and rules left in the content tree. They have to be artifacts, or the reader hears the header and footer again on every single page.
8. Nested tables and merged cells that survived the conversion. Layout tables and merged cells rarely convert cleanly. They usually need restructuring in the source file, not patching in the PDF.
9. No bookmark structure in a long document. Not an automated failure, which is why it survives — but a 120-page manual with no bookmark tree is unnavigable, and WCAG’s multiple-ways criterion expects a second route to the content.
10. Meaning carried by color alone, and link text that reads “click here.” Both survive remediation because neither is a tagging problem. They are authoring problems, and they have to go back to the author.

The reason a checklist beats a score: an automated checker will clear a file that a human tester rejects. Reading order, whether alternative text conveys the right meaning, and whether a table’s structure matches its logic are not machine-decidable. Automated testing tells you what is definitely broken; it cannot tell you a file is usable. That is why every Taika remediation is verified with both, and why the verification record names the criteria it was tested against.

If you want to know which of the ten you are facing before you talk to anyone, run a file through the free PDF accessibility checker — 14 checks in your browser, a scored report, and the standard behind each failure.

508 remediation services, scoped to what you actually have

“Document remediation” covers wildly different amounts of work depending on how the file was made, so Taika’s 508 remediation services are scoped by format and condition rather than by a flat per-file assumption:

• Native PDFs exported from Word or InDesign — the cheapest case. Structure usually exists and needs correcting rather than building from nothing.
• Scanned, image-only PDFs — OCR, proofread, then tagged from zero. The most labor per page, and the case most often underestimated.
• Word documents — remediated in the source, so every future export inherits the structure. Fixing the .docx is almost always cheaper than fixing the PDF it produced, and it is the only fix that holds.
• PowerPoint — slide reading order, layout placeholders instead of free-floating text boxes, and alternative text on charts that conveys the chart’s point rather than its file name.
• Excel — header rows and named ranges exposed, sheet names meaningful, and no information carried by cell fill color alone.
• Interactive forms — field names, tooltips, tab order, required-field indication, and error messaging a screen reader actually reaches.
• Video and audio — captions, transcripts and audio description; see accessible video and captioning and subtitling.
• Braille, large print and other alternative formats — see braille and alternative formats.
• Templates — the highest-leverage item on this list. Remediate the template once and the next two hundred documents that come out of it are conformant by default.

Four things move the scope and almost nothing else does: page count, whether there is a real text layer, table and form density, and whether the file has to exist in more than one language. That is why the free accessibility assessment asks for a sample rather than a description — a sample answers all four in one pass. If it is a single document, get a remediation price instead and skip the conversation.

One vendor instead of two

Most agencies solve this problem twice. An accessibility firm remediates the English PDF. Then a translation agency produces the Spanish version — and hands back a file that is untagged, has no reading order, and fails the same standard the original was just fixed to meet. So the remediation gets paid for twice, on two contracts, with neither vendor accountable for the other’s output.

That happens because the two capabilities almost never sit in one company. Accessibility specialists do not staff linguists. Translation companies do not do tag structure, reading order, or PDF/UA conformance.

Taika does both, on the same file, under one scope of work:

• Remediate, then translate, then re-verify — the translated document is checked against the same WCAG 2.1 AA and PDF/UA criteria as the source, not assumed to have inherited them.
• Tag structure survives the language change — reading order, alt text, table headers, and form labels are rebuilt for the target language rather than carried over broken.
• Right-to-left and expanding languages handled deliberately — Arabic and Hebrew reading order, and the 20–30% text expansion typical of Spanish or German, are layout problems that break naive conversions.
• 300+ languages, so the language your community actually speaks is not “unsupported.”
• One accountable vendor for a single obligation. Title VI language access and ADA/Section 508 disability access usually arrive in the same audit finding, the same OCR complaint, and the same procurement.

Purchasable on contracts you already hold

Public buyers rarely need a new solicitation for this. Taika is a GSA Schedule holder and a NASPO ValuePoint contract holder for language services, is SAM.gov registered, and is veteran-owned (VOSB) — which also carries socio-economic credit on federal awards. See GSA translation services, NASPO ValuePoint, or government language services for the vehicle details.