ADA and Section 508: what they mean for PDFs and documents

Three groups, three different rules

When people say "ADA compliant PDF" or "508 compliant PDF," they usually mean a document that meets WCAG, the Web Content Accessibility Guidelines published by W3C. Which law applies, and which WCAG version, depends on who publishes the document.

• Federal agencies: Section 508 of the Rehabilitation Act.

• State and local governments: Title II of the Americans with Disabilities Act (ADA), and its 2024 web and mobile app rule.

• Businesses open to the public: Title III of the ADA, which has no detailed web standard from the Department of Justice (DOJ).

This guide summarizes what the official sources say. It is general information, not advice about your situation. For that, talk to a qualified professional or your organization's accessibility or compliance office.

Section 508: federal agencies

Section508.gov explains that Section 508 was added to the Rehabilitation Act in 1998 and "applies to all federal agencies when they develop, procure, maintain, or use" information and communication technology.

The detailed requirements are the Revised 508 Standards, published by the U.S. Access Board. For documents, the key rule is E205.4: electronic content "shall conform to Level A and Level AA Success Criteria and Conformance Requirements in WCAG 2.0." Non-web documents, such as PDFs and Word files, are excused from four specific WCAG 2.0 criteria that do not fit documents.

Under E205.2, this applies to public-facing content.

Section508.gov's PDF page adds a policy point worth knowing: federal policy asks agencies to prioritize HTML and use PDFs only when necessary. It links to a PDF testing and remediation guide, testing checklists and a video series on testing PDFs in Adobe Acrobat.

Who else should care: contractors and vendors who supply documents or software to federal agencies are often asked to meet the same standards in their contracts.

ADA Title II: state and local governments

In 2024 the DOJ published a rule for the websites and mobile apps of state and local governments. According to ADA.gov:

• The technical standard is WCAG 2.1, Level AA.

• Web content is defined to include "text, images, sound, videos, and documents," so posted PDFs are covered unless an exception applies.

• A 2026 interim final rule extended the compliance dates. Governments with a population of 50,000 or more now have until April 26, 2027. Those under 50,000, and special district governments, have until April 26, 2028.

Dates like these can change again, so check the ADA.gov fact sheet (opens another site) for the current position.

The exceptions people ask about

ADA.gov lists several exceptions. Two matter most for documents:

• Archived web content: exempt only if all conditions are met. It was created before the compliance date, is kept only for reference, research or recordkeeping, sits in a clearly marked archive area, and "has not been changed since it was archived."

• Preexisting conventional electronic documents: PDFs, word processing files, presentations and spreadsheets posted before the compliance date usually do not need to meet WCAG 2.1 AA. But this does not apply to documents that are posted or updated after the date, or to documents people currently use to apply for or access services.

That last point catches many organizations. A permit application, a fee schedule or a program enrollment form that the public uses today likely falls outside the exception, even if it was first posted years ago.

ADA.gov also notes that even where an exception applies, the ADA's duties to provide effective communication and reasonable modifications still apply. If someone asks for a document in an accessible format, that request still has to be handled.

ADA Title III: businesses

For businesses open to the public, the DOJ's web guidance says the ADA applies to the goods and services they offer, including online. But the DOJ "does not have a regulation setting out detailed standards." It points to WCAG and the Section 508 Standards as helpful technical guidance.

In practice, many businesses use WCAG 2.1 AA or 2.2 AA as their target. Some states have their own accessibility laws on top of federal law, so the picture varies by state.

What the standards ask of a PDF

Whichever rule applies, the practical checklist looks similar:

1. Real text, not scanned images (run OCR on scans).

2. Tags that mark headings, lists, tables and figures.

3. A reading order that follows the logic of the page.

4. Alt text for meaningful images; decorative items marked as artifacts.

5. Table header cells identified.

6. A real document title and the document language set.

7. Form fields with labels.

8. Enough color contrast, and color never the only signal.

A sample situation

Here is a fictional example. The Town of Northgate (population about 38,000) has 600 PDFs on its website. Under the dates on ADA.gov, its deadline is April 26, 2028.

A sensible first pass:

• List every PDF and note whether it is still used to apply for or access a service.

• Move documents kept only for records into a clearly labelled archive section and leave them unchanged.

• Prioritize forms, fee schedules, meeting agendas and anything updated regularly.

• Consider whether some documents would work better as web pages, which is the approach section508.gov encourages for federal agencies.

• Set up a way for people to request an accessible version of any document.

Whether a given document qualifies for an exception is a judgment for the town's own counsel or compliance staff.

Questions to ask a vendor or remediation service

• Which standard do you test against: WCAG 2.0, 2.1 or 2.2, and PDF/UA?

• Do you test with a screen reader, or only with an automatic checker?

• Who writes the alt text, and how do we review it?

• What report do we get for each file?

• How do you handle forms and complex tables?

Get the heavy lifting started on your files

EasyToDecode is launching soon with a tool that will take an untagged PDF and return a tagged version with headings, reading order and table structure, draft alt text for your review, and a report of what still needs a person. It does not certify compliance. See how it works or join the waitlist to hear when it opens.