Section 508 PDF Compliance: How to Make, Check and Remediate a 508-Compliant PDF

Most organizations discover Section 508 the hard way: a complaint about a form a screen-reader user couldn’t complete, a grant condition that references “accessible electronic content,” or a procurement officer asking for a conformance report nobody has. The rule itself is not that complicated — but the PDFs it applies to have been piling up for years, and that backlog is where the real work lives.

This guide explains what Section 508 PDF compliance actually means, which documents it covers (and which it doesn’t), how to make a PDF 508 compliant, how to check one, and how to prioritize remediation when you can’t fix everything at once. If you already know you need the work done rather than explained, go straight to Section 508 remediation services.

What Section 508 actually is

Section 508 of the Rehabilitation Act requires that information and communication technology developed, procured, maintained, or used by federal agencies be accessible to people with disabilities. In practice, “electronic content” means exactly the files organizations produce every day: PDFs, Word documents, web pages, presentations, forms, and multimedia.

The standard a 508-compliant PDF is actually tested against

This is the part most guides blur, and it decides what “compliant” means for your files.

• WCAG 2.0 Level A and AA is the legal test. Provision E205.4 of the Revised 508 Standards says electronic content “shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0.” A PDF is electronic content, so that is the bar.
• Four WCAG criteria don’t apply to a PDF. The same provision exempts non-web documents from 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation and 3.2.4 Consistent Identification — criteria written for sets of web pages that make little sense inside a single file. Everything else at Level A and AA still applies.
• PDF/UA is not the legal test, but it is the right build standard. The Revised 508 Standards name PDF/UA-1 (ISO 14289-1) in provision 504.2.2 — and that provision governs authoring tools, requiring software that exports PDF to be able to export PDF/UA. The document itself is still measured against WCAG. PDF/UA matters because it is the technical specification for how an accessible PDF is structured, so remediating to WCAG and PDF/UA is the professional norm.
• If you’re also covered by ADA Title II or Section 504, remediate to WCAG 2.1 AA once. Those rules adopt WCAG 2.1 AA, which contains everything in 2.0 AA plus more. Fixing a file to 2.0 now and 2.1 later means paying to touch the same file twice. Section 508 vs ADA vs WCAG sets out how the three fit together.

Which PDFs have to comply — and which don’t

Section 508 does not sweep in every file an agency has ever produced. The scoping is specific:

• Public-facing content must conform (E205.2) — anything published to the public, whatever the format.
• Non-public official communications are covered too, but only in nine defined categories under E205.3 — among them emergency notifications, decisions adjudicating an administrative claim, notices of benefits or eligibility, survey questionnaires, templates and forms, and educational or training materials. An internal draft that fits none of the categories is not in scope.
• The legacy safe harbor (E202.2). Existing content that complied with the original 508 standards and has not been altered on or after January 18, 2018 does not have to be brought up to the revised standards. The catch: edit and republish that file, and the safe harbor is gone for it.
• Ask whether it should be a PDF at all. Section508.gov states that federal policy requires agencies to prioritize HTML and use PDFs only when necessary. A web page is often cheaper to keep accessible than a PDF — which matters when you’re deciding what to remediate and what to retire or convert.

Who has to comply — not just federal agencies

Section 508 is a federal-agency rule on its face, but the obligation reaches much further:

• Federal contractors and vendors must deliver 508-conformant electronic content, because the agency purchasing it is bound by 508. FAR 39.2 and Section 508 covers what a vendor actually has to deliver.
• State and local governments are covered by a broader rule: the Department of Justice’s ADA Title II web accessibility regulation, which requires WCAG 2.1 AA.
• Recipients of federal financial assistance — including many healthcare providers under Section 504 — face a parallel HHS requirement.
• School districts, universities, and healthcare organizations frequently inherit these standards through funding conditions, state policy, or contract terms.

Both the DOJ and HHS deadlines were extended in spring 2026, and the dates now differ by the size of the entity. We keep them in one place so they are never out of date: see the ADA Title II and Section 504 compliance deadlines.

The practical takeaway: if your organization receives public funding, sells to government, or serves the public as a government entity, the question is not whether your documents need to meet an accessibility standard — it’s by when, and how far behind you already are.

What makes a document or PDF accessible

An accessible PDF isn’t simply one you can open and read on screen. It’s one that assistive technology — a screen reader, a braille display, voice navigation — can move through the way a sighted reader moves through the visual layout. That requires:

• A tag structure that defines the logical reading order, so content is announced in the order a human would read it, not the order it happens to sit on the page.
• Properly marked headings, lists, and data tables, so relationships (this is a heading; these cells belong to this row) are exposed, not just visually implied.
• Alternative text for images, charts, and figures that conveys the meaning, not “image1.jpg.”
• Accessible, labeled form fields that can be completed with a keyboard alone.
• Document metadata — the document’s language and title set correctly.
• Adequate color contrast and no information conveyed by color alone.

A document can look perfect and still fail every one of these. Accessibility lives in the structure underneath the visual layer, and that structure is exactly what remediation adds. What is actually inside a remediated PDF walks through the tags, reading order and roles in detail.

How to make a PDF 508 compliant

The cheapest 508-compliant PDF is one that was built accessible rather than fixed afterwards. In order:

1. Fix the source file, not the PDF. In Word or PowerPoint, use real heading styles rather than bold text, add alternative text to meaningful images, mark table header rows as headers, use real lists, and set the document title and language. Every one of these carries into the PDF if the export is done properly — and none of them has to be rebuilt by hand later.
2. Export with tagging switched on. Save or export to PDF using the option that keeps document structure tags. A “print to PDF” route usually throws the structure away and hands you an untagged file.
3. Check the result — see the next section. Exports are rarely perfect: reading order, complex tables and form fields are the usual casualties.
4. Remediate what the export couldn’t carry. Fix the tag tree, reading order, table structure and form labels in the PDF itself, then re-test.

If there is no accessible source — a scanned document, a file from a vendor, a PDF whose original is long gone — you are in remediation from step one.

How to check if a PDF is 508 compliant

Section508.gov’s own PDF testing training is unambiguous on the order of operations: before using Acrobat’s accessibility check tools, the PDF must be visually verified to identify issues that cannot be detected by the automated testing tool. A practical checklist that follows it:

1. Document properties — title set, language set, the file is tagged, and security settings don’t block assistive technology.
2. Real text — select the text; if you can’t, it’s a scanned image and needs OCR.
3. Tags and reading order — headings nest logically, lists are lists, and the reading order matches the visual order.
4. Keyboard — tab through the whole file; focus moves in a logical order and every control is reachable.
5. Alternative text — meaningful images describe their meaning; decorative ones are marked as artifacts.
6. Tables — header cells are tagged as headers, with scope set where the table needs it.
7. Forms — every field has a label (tooltip) and a sensible tab sequence.
8. Links — link text makes sense out of context.
9. Color and contrast — nothing relies on color alone, and text contrast meets the ratio.
10. Automated check last — run the full automated check to catch what a person misses, not instead of the person.

For a fast first read on a specific file, our free PDF accessibility checker analyzes a document in your browser — the file isn’t uploaded to a server — and shows you what’s missing. For a documented, file-by-file result across a document library, that is what a PDF accessibility audit is for.

What remediation involves

Remediation is the process of taking an existing file and building in the structure above. How much work that takes depends entirely on how the file was created:

• A well-authored PDF exported from Word with real headings may need light tagging and a reading-order check.
• A complex form or report with data tables often needs its tag tree rebuilt and its tables reconstructed cell by cell.
• A scanned PDF is not text at all — it’s a picture of text — so it first needs OCR to become real, selectable content before any tagging can begin.

This is detailed, manual work. The “Make Accessible” auto-tag buttons built into common PDF tools are a starting point at best: they routinely get reading order wrong, generate meaningless alt text, and mishandle complex tables. A file that passes an automated checker can still be unusable with a real screen reader — which is why genuine remediation always ends with manual keyboard and screen-reader verification, not just a green checkmark.

Section 508 compliant documents beyond PDF

The same WCAG 2.0 A and AA standard applies to Word files, PowerPoint decks and Excel workbooks. The techniques differ — slide titles and reading order in PowerPoint, header rows and named ranges in Excel — but the test is the same. If your program is fixing only the PDFs, the Office files published alongside them are usually the next finding. PDF and document accessibility covers the other formats.

Prioritize by impact — you don’t have to fix everything at once

A backlog of thousands of PDFs is paralyzing if you treat it as one job. It isn’t. A sensible remediation order:

1. High-traffic, high-stakes documents first — applications, notices of rights, benefits forms, anything a person must be able to read to access a service.
2. Documents tied to a legal deadline or obligation — content explicitly named in a grant, contract, or the ADA Title II scope.
3. The long tail, over time — and, critically, fix your authoring process so that every new document is born accessible. Otherwise you remediate the backlog while quietly creating next year’s backlog.

That last point is where most programs succeed or fail. Remediation without an accessible authoring workflow is bailing a boat without patching the hole.

Keep documentation for procurement and audits

For procurement, compliance, and any response to an Office for Civil Rights (OCR) complaint, keep a record of conformance. A VPAT or accessibility conformance report for remediated materials is the artifact procurement and compliance teams need for their files — and the thing an auditor or agency will ask for first. What is a VPAT explains what one contains. There is no official Section 508 certification for a PDF, a person or a vendor; the documented test results are the evidence.

Common mistakes that cause findings

• Relying on the auto-tag button and assuming a passing automated score means conformance.
• Remediating the website but ignoring the PDFs — the published back-catalog of forms and reports is usually the larger, quieter gap.
• Editing a legacy file and assuming the safe harbor still covers it — it doesn’t once the file is altered.
• Treating remediation as a one-time project instead of an ongoing pipeline for new content.
• Getting the deadline wrong — the ADA Title II and Section 504 dates were extended in spring 2026, so content framed around the original dates is out of date. Check the current dates.
• Forgetting language access — organizations serving multilingual communities often owe both translated vital documents and 508 remediation, and handling them as two disconnected projects doubles the cost and the coordination.

Getting help

Section 508 remediation is specialized work, and doing it well is the difference between conformance and a file that merely scores well on a checker. Taika Translations remediates PDFs, Word files, and other electronic content to WCAG 2.1 AA, Section 508, and PDF/UA, verified with the same tools auditors use plus manual screen-reader testing, with conformance documentation and VPATs available on request.

Because language access and disability access so often arrive as a single obligation, the same team can translate your vital documents into the languages your community speaks and remediate them to Section 508 in one workflow.

• Ready to scope the work? See Section 508 & document remediation services or request a free accessibility assessment — send a sample of your documents and we’ll tell you exactly what fails, what remediation involves, and what to prioritize.
• Want the broader picture? Start with accessibility & compliance services or the deep-dive on PDF & document accessibility.

Related reading: WCAG & ADA compliance tips.