Section 508 PDF: What Federal Agencies Must Do

Updated · 4 min read

On this page
  1. Who Section 508 actually binds
  2. What the Revised 508 standards require of a PDF
  3. How Section 508 relates to ADA Title II and WCAG versions
  4. What to keep as evidence
  5. Where an automated pass fits

Section 508 requires US federal agencies to publish electronic documents that people with disabilities can use, and the Revised 508 standards incorporate WCAG 2.0 Level AA. That reaches the PDFs an agency posts, not only its web pages. This guide covers who the law binds, what it asks of a PDF, how it relates to ADA Title II and the WCAG versions, and what to keep on file as evidence.

Who Section 508 actually binds

Section 508 was added to the Rehabilitation Act and took its current form in the 2017 refresh known as the Revised 508 standards. It binds federal agencies directly. Every electronic document an agency publishes, including PDFs, is in scope.

It also reaches procurement. When a federal agency buys technology or services, it must ensure the standards are met, which is why contractors and vendors delivering documents or document tooling to an agency are frequently asked to demonstrate conformance. If you sell to the federal government and hand over a PDF, Section 508 is your problem too.

The authoritative source is Section508.gov, which publishes the standards and plain-language guidance on making documents accessible.

What the Revised 508 standards require of a PDF

The standards incorporate WCAG 2.0 Level AA by reference. For a PDF, that translates into concrete properties rather than a single checkbox:

  • A structure tree that carries headings, paragraphs, lists and tables, so assistive technology can announce what each element is
  • A reading order that matches the visual flow of the page
  • Alternative text for meaningful images, and a decision that decorative images are marked as artefacts
  • Table headers marked so a screen reader can relate a cell to its column and row
  • A document language, and a title the reader will announce
  • Text, not an image of text, so content can be read, searched and enlarged

A PDF that is a scan with no text layer fails on the last point before anything else can be assessed. That is why the first question for any archive is which files have a real text layer and which need OCR.

Two of those properties deserve calling out. A correct reading order and meaningful alternative text are the items most often left undone, because neither can be fully automated. A file can carry a complete tag tree and still fail Section 508 if the order is wrong or an image has no description.

How Section 508 relates to ADA Title II and WCAG versions

Three requirements get conflated, and separating them saves a lot of confusion.

RequirementWho it bindsStandard it points toDocument relevance
Section 508Federal agencies and their procurementsRevised 508 standards, incorporating WCAG 2.0 AAPublished and procured electronic documents
ADA Title IIState and local government entitiesWCAG 2.1 AA, per the DOJ ruleDocuments those entities publish, PDFs included
European Accessibility ActServices in scope in the EUEN 301 549, which points to WCAGDocuments within the covered services

The DOJ published an interim final rule in April 2026 extending the ADA Title II web and app accessibility deadlines to 26 April 2027 for public entities serving 50,000 or more people and 26 April 2028 for smaller entities and special district governments. The full detail is on the DOJ web rule. Section 508 has no such deadline, because it has applied for years.

For the WCAG criteria that actually bite in a PDF, see WCAG PDF. For the EU side, European Accessibility Act PDF covers the timeline and the harmonised standard.

What to keep as evidence

Compliance is a paper trail as much as a file property. When someone asks how you know a document is accessible, four things answer the question:

  1. The remediated PDF itself.
  2. A validation report from a recognised checker. PAC 2024 and veraPDF both produce one.
  3. A note of the standard applied, such as WCAG 2.0 AA for Section 508 or 2.1 AA for Title II.
  4. A record of what was left for a human, and why. Automated tools flag images that need alt text and complex tables that need review; documenting those decisions is what shows diligence.

A worked example: a federal office publishes an annual report as a PDF. It remediates the file, runs a validator, and finds the reading order broken across a two-column section. They fix that section manually, re-run the validator, and file both reports with the document. That pair of reports is the evidence that the office did the work, and it is what protects them if a complaint arrives.

Where an automated pass fits

Automated tagging gets a document a long way, but it does not close the loop on Section 508. It cannot write meaningful alternative text, it struggles with complex tables and multi-column reading order, and it cannot touch a scan with no text layer. Treat it as the first pass that makes the routine files usable and the hard files obvious.

TagRight is built for exactly that first pass: upload a PDF, get a tagged copy plus a report of what still needs a human, all in the browser. It is a remediation aid and a triage tool, not a certification, so keep the validator step in your process. For a full checklist before you publish, work through the accessible PDF checklist, and for the wider picture of what an accessible document is, see accessible PDF. You can start with a free document and check the plans and pricing before rolling it out across a team.

Frequently asked questions

Does Section 508 apply to PDFs?

Yes. Section 508 requires federal agencies to make electronic and information technology accessible, and that includes electronic documents such as PDFs. The Revised 508 standards incorporate WCAG 2.0 Level AA, which is the benchmark a published PDF is measured against.

Does Section 508 apply to vendors and contractors?

It can. Agencies must ensure the products and services they procure meet the standards, so a contractor delivering documents or a document-handling tool to a federal agency is often asked to show conformance as part of the contract.

Is Section 508 the same as ADA Title II?

No. Section 508 binds federal agencies and their procurements. ADA Title II, updated by the DOJ's 2026 rule, binds state and local government entities and sets WCAG 2.1 AA with compliance dates in 2027 and 2028. Both reach PDFs, through different routes.

What WCAG version does Section 508 use?

The Revised 508 standards incorporate WCAG 2.0 Level AA by reference. WCAG 2.1 AA is a superset that adds criteria, so meeting 2.1 AA generally satisfies 2.0 AA as well.

What evidence should an agency keep for Section 508?

Keep the remediated file, a validation report from a tool such as PAC 2024 or veraPDF, a note of the standard applied, and a record of what was left for a human. The paper trail is what answers an audit or a complaint.

Tag a PDF free