ADA Title II PDF Deadline: What Public Entities Must Fix

22 October 2026

pdf
accessibility
ocr
ada

US state and local governments that serve 50,000 or more people must make their web content, PDFs included, meet WCAG 2.1 Level AA by April 26, 2027. Smaller entities have until April 26, 2028. A PDF on a public website counts as web content, so scanned, untagged files are the first problem to fix.

When is the ADA Title II PDF deadline?

The Department of Justice's Title II rule sets two dates, based on the population a public entity serves. An interim final rule effective April 20, 2026 pushed both back by a year.

Entity	Compliance date
Serves 50,000 or more people	April 26, 2027
Serves fewer than 50,000 people, and special district governments	April 26, 2028

Some vendor pages still show the older 2026 dates. Check the date against the interim final rule before you plan around it.

Does the rule really cover PDFs?

Yes. A PDF posted on a public entity's website is web content, and the standard is WCAG 2.1 Level AA. The PDF gets no lower bar than an HTML page.

There is a limited exemption for preexisting conventional electronic documents created before the compliance date (28 CFR §35.201). It lasts only while the document is not used to apply for or access a service. A permit form or a benefits notice that people rely on is in scope however old it is. If you are unsure, treat the file as in scope.

What makes a PDF accessible?

Accessibility lives in the file's structure, not in how it looks on screen. A screen reader needs the following:

Real text. A scanned page is a picture of paper, so a screen reader finds nothing to read.
Tags and reading order. Tags mark headings, paragraphs and lists, and set the order in which they are read.
Proper headings and tables. Use real heading tags and marked header cells, not bold text or tab-spaced columns.
Alt text. Charts, maps, seals and photos need a description, including the numbers in a chart.
Labeled form fields. Every fillable field needs a label.
A document title and a language. Both are set in the file's properties.

PDF/UA and Section 508 overlap heavily with WCAG, but neither is an automatic substitute for it.

How do I turn a scanned PDF into text that can be read?

Start with OCR, then check the result by hand. OCR recognises the characters, but it does not add tags, alt text or table structure.

Open the file and try to select a sentence. If you cannot, the page is an image.
Run it through OCR PDF. This is a Pro tool that runs on the server, and it works with English text only.
Search the output for a word you know is on the page, to confirm the text layer exists.
Fix recognition errors, especially in names, numbers and tables, which OCR gets wrong most often.
Add tags, reading order and alt text in an accessibility editor, or rebuild the document from its source file.

If you still have the original Word or design file, rebuilding is often better than repairing. Export from the source with tagging switched on instead of fixing a scan.

Can I fix the title and other document properties for free?

The document title is the quickest fix. Screen readers announce it when the file opens. Without one, many readers fall back to the file name, which is often something like "scan_0042.pdf".

The Edit metadata tool lets you edit document properties such as the title and author. It runs in your browser, so the file is not uploaded. It does not tag the document, add alt text or check WCAG conformance. Treat it as one step in a larger checklist.

What if all I have is a PDF?

When the source file is gone, convert the PDF back to an editable format. PDF to Word is a Pro tool that does this on the server. Then correct the headings, tables and lists in the editor and export again with tagging on. Complex layouts often need cleanup after conversion, so check the output against the original page.

How should a team plan the work?

Start with what people use. Rank files by how often they are downloaded and whether they support an application, a payment or a deadline. Fix those first.

Then stop creating new problems. Every new document published after the compliance date must meet the standard, so set up templates and an export checklist now. Finally, consider replacing short PDFs with web pages, which is sometimes the cheapest route to accessibility.

What should I check before publishing a fixed file?

Run through a short routine for every file. It takes a few minutes and catches most failures.

Open the PDF and confirm the title bar shows a real title, not a file name.
Select text on every page to confirm it is live text and not an image.
Tab through the form fields, if there are any, and confirm each has a label.
Listen to the first page with a screen reader or the browser's read-aloud feature, and confirm the order makes sense.
Compare the page count and figures against the original, so that conversion has not dropped a table or a number.

Keep a dated note of what you checked. If anyone later questions a file, a record of the review shows the work was done in good faith.

Key facts

The deadline for entities serving 50,000 or more people is April 26, 2027.
Smaller entities and special district governments have until April 26, 2028.
The interim final rule extending both dates took effect on April 20, 2026.
The required standard is WCAG 2.1 Level AA.
The exemption for preexisting documents (28 CFR §35.201) ends once a document is used to access a service.
OCR PDF on ilovspdfs is a Pro tool and supports English only.

Frequently asked questions

Does a scanned PDF meet WCAG 2.1 AA?

Not on its own. A scan has no text for assistive technology to read. It needs OCR, then correction and tagging, or a rebuild from the source file.

Are old PDFs exempt from the Title II rule?

Only some are. Documents created before your compliance date are exempt while they are not used to apply for or access your services. Any document you still use for a service is in scope, however old it is.

Is PDF/UA the same as WCAG?

No. They overlap heavily, but PDF/UA is not an automatic substitute for WCAG 2.1 AA. Title II names WCAG 2.1 AA as the standard.

Does OCR make a PDF accessible?

It is the first step, not the last. OCR creates a text layer, but tags, reading order, alt text and table headers still have to be added and checked.

Can I replace a PDF with a web page?

Often, yes. An accessible HTML page can stand in for a PDF, and it is usually easier to keep accessible. Keep the PDF only if people need the printable version.