ADA- and Section 508-compliant PDFs? What the rules actually require

Legal status as of November 10, 2026. US accessibility rules are moving quickly: the deadlines under ADA Title II and the HHS Section 504 rule were extended in spring 2026, and a lawsuit against these extensions is pending. This page describes the rules on that date. It is general information, not legal advice – for your situation, please talk to a US attorney.

Is there such a thing as an “ADA-compliant PDF”?

Short answer: not in the sense most people hope for. The Americans with Disabilities Act of 1990 does not mention websites or PDFs, and neither the ADA nor its regulations provide for a certificate or seal for a PDF. When a tool or a vendor offers to make a document “ADA-certified”, that is marketing, not a legal status.

What does exist are concrete yardsticks. Which one applies depends on who you are:

• Federal agencies (Section 508): WCAG 2.0 Level A and AA – explicitly also for documents.
• State and local governments (ADA Title II): WCAG 2.1 Level AA for web content, including PDFs.
• Recipients of HHS funding (Section 504): WCAG 2.1 Level AA as well.
• Private businesses (ADA Title III): no technical standard in any regulation.

For private businesses, the Department of Justice (DOJ) said in its guidance of March 18, 2022 that the ADA applies to what they offer on the web, but that it has no regulation setting out detailed standards; WCAG is “helpful guidance”. In a court filing in February 2026, the DOJ stated that it does not endorse WCAG as the necessary standard under Title III. Still, WCAG is the most useful measure you have, because the binding federal rules all use it.

So the honest translation of “ADA compliant PDF” is: a PDF that has been checked against the WCAG level that applies to you, criterion by criterion, by tools and by people – with a written result. For the bigger picture, see our overview of digital accessibility law in the US.

Section 508: WCAG 2.0 Level AA – also for documents

Section 508 of the Rehabilitation Act covers information and communication technology that federal agencies develop, procure, maintain or use. The Revised 508 Standards (36 CFR Part 1194), applicable since January 18, 2018, incorporate WCAG 2.0 Level A and AA by reference – for web pages and for electronic content such as PDFs, word processing files and presentations (E205.4). This covers all public-facing content, plus internal content that is official business in one of nine categories, for example emergency notifications, notices of benefits, templates and forms, or training materials.

Which WCAG criteria do not apply to documents

For documents, wherever WCAG says “Web page” or “page”, the 508 Standards read “document”. Four success criteria do not apply to non-web documents: 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation and 3.2.4 Consistent Identification – all four deal with moving through a set of web pages. Everything else applies in full. The W3C’s WCAG2ICT note explains how the criteria are read for documents; it is guidance, not a requirement.

Why PDF/UA alone is not the Section 508 path

PDF/UA (ISO 14289-1) defines how a PDF has to be built so that assistive technology can interpret it: tags, structure, metadata. It is the right technical foundation, and our remediation work is built on it. But it is not the Section 508 yardstick. The U.S. Access Board originally proposed PDF/UA-1 as an alternative to WCAG 2.0 and removed it from the final rule. Its reasoning: WCAG 2.0 can serve as the sole standard for PDF files, PDF/UA-1 cannot – it does not address scripting, for example, or PDFs used as a container for video. PDF/UA-1 now appears in the 508 Standards only for authoring tools, which must be able to export PDF/UA-1 files.

The Board added that PDF/UA-1 can still be useful when you assess a PDF for WCAG conformance. That matches what I see in our projects: a PDF/UA-compliant file is the best starting point, but a passed PDF/UA check does not tell you whether the alternative text is meaningful or whether the colors in a chart can be told apart. For Section 508, you need the WCAG result.

What this means for vendors

If you create documents for a federal agency, Section 508 reaches you through procurement. Section508.gov states that federal policy requires agencies to prioritize HTML and use PDFs only when necessary – so expect to be asked why a document needs to be a PDF at all. The usual proof in procurement is an Accessibility Conformance Report (ACR) based on the ITI VPAT template; more in our guide to Section 508 for agencies and vendors.

ADA Title II and Section 504: PDFs on government and HHS-funded websites

Under the DOJ’s final rule of April 2024 (28 CFR Part 35, Subpart H), state and local governments must make their web content and mobile apps conform to WCAG 2.1 Level AA. The rule names PDFs explicitly as “conventional electronic documents”, alongside word processing, presentation and spreadsheet files. Services provided through contractors are covered, too – if you produce documents for a city, a county or a state agency, the requirement can reach you via your contract.

The deadlines were moved by an interim final rule of April 20, 2026: April 26, 2027 for entities with a total population of 50,000 or more, and April 26, 2028 for smaller entities and special district governments. The substantive requirements did not change. On May 21, 2026, the National Federation of the Blind sued against the delay; as of November 10, 2026, no decision is known.

For recipients of HHS funding, the Section 504 rule of May 2024 sets the same standard, WCAG 2.1 Level AA. Its deadlines are now May 11, 2027 for recipients with 15 or more employees and May 10, 2028 for smaller ones. More on the government side in our guide to ADA Title II for state and local governments.

The exception for older documents – and where it ends

Both rules contain an exception that matters for every document archive: PDFs and other conventional electronic documents that were available on your website or app before your compliance date do not have to meet WCAG 2.1 AA – unless they are currently used to apply for, gain access to or participate in your services, programs or activities. An old annual report that nobody needs in order to use a service will often fall under the exception. A permit application that people still download and fill in does not, however old the file is.

Further exceptions cover archived content (created before your compliance date, kept unchanged and only for reference, research or recordkeeping, in a clearly marked archive area), content posted by third parties without an arrangement with you, and individualized, password-protected documents about a specific person, property or account. Three limits apply:

• Every new document counts. What you publish after your compliance date is not pre-existing.
• Exempt does not mean off the hook. The ADA’s effective communication obligation remains. According to the DOJ, a government would likely still need to provide exempt content to a person with a disability who needs it, in a format that works for them.
• “On request” is not a strategy for covered content. The Title II rule allows conforming alternate versions only where technical or legal limitations make it impossible to meet the standard directly.

Checklist: what a PDF needs to meet WCAG

These are the points where documents fail most often in our audits. They apply under Section 508 (WCAG 2.0) as well as under Title II and Section 504 (WCAG 2.1).

• Tags and structure: The PDF is tagged, and headings, lists, paragraphs and links carry the right tags. Text that only looks like a heading is not a heading (1.3.1).
• Reading order: The tag order follows the logical order of the content – also in multi-column layouts, sidebars, footnotes and text boxes (1.3.2).
• Tables: Header cells are marked as headers, and layout tables are not tagged as data tables. In our experience, tables are the most common source of errors (1.3.1).
• Forms: Every field has a label that a screen reader announces, the tab order is logical, errors are described in text, and everything works with the keyboard alone (2.1.1, 2.4.3, 3.3.1, 3.3.2, 4.1.2).
• Language: The document language is set, and passages in other languages are marked (3.1.1, 3.1.2).
• Alternative text: Informative images and charts have alternative text that conveys their content; decorative elements are marked as artifacts (1.1.1).
• Contrast and color: Text has a contrast ratio of at least 4.5:1 (3:1 for large text), and information is never conveyed by color alone – around 8% of men have red-green color blindness (1.4.3, 1.4.1). WCAG 2.1 adds 3:1 for graphical objects such as chart lines or form field borders (1.4.11).
• Title and links: The document title is displayed instead of the file name, and link texts make sense in context (2.4.2, 2.4.4).

What an automated checker can and cannot tell you

Tools such as PAC or the Acrobat accessibility checker test the machine-testable rules of PDF/UA. But 60–70% of WCAG criteria cannot be tested automatically. No tool can tell you whether an alternative text describes what a chart actually shows or whether a form instruction is understandable. That is why every document that matters should also be read once with a screen reader such as NVDA, JAWS or VoiceOver – by someone who knows what to listen for.

From document inventory to a documented result

In our projects, it is rarely one PDF; it is hundreds or thousands. This order has worked for us:

1. Prioritize. Forms and documents people need in order to use a service come first, then everything you publish new, then frequently downloaded files.
2. Check for free. Access Read checks your PDFs against PDF/UA in the browser and shows the order in which a screen reader presents them.
3. Remediate with human review. Access Doc remediates PDFs to PDF/UA, with a conformance report for each document, checked against WCAG criteria.
4. Fix the source. Templates with real heading styles, alternative text and a set document language prevent many problems before export. Our step-by-step guide to PDF/UA shows how.

One thing a report cannot do: certify anything. It documents what was tested and with what result, and its value depends entirely on the testing behind it – which is exactly why we don’t put a “compliant” seal on it.