The PDF accessibility compliance guide for local governments
Most guides like this one sit behind a form: give up your email, wait for a download, get a PDF full of general advice. This one doesn't. We tested 275 real documents — agendas, minutes, budgets, and annual financial reports already published by cities and counties — against automated accessibility testing. Here's exactly what we found, and what it means for your documents.
No download, no gate, no email required. Just scroll — it's all here.
What "compliant" means, and by when.
The DOJ's rule under Title II of the ADA sets WCAG 2.1 Level AA as the standard for state and local government web content, including PDFs published on your website. The compliance dates depend on population:
Cities, counties, and other public entities of 50,000 or more people.
Smaller public entities and special district governments.
There are exceptions, including one for certain archived content, but they're narrow — a resident's request for an accessible version can put an "archived" document back in scope. There's runway before the deadline; there isn't a reason to wait for it.
We didn't write this guide from theory. We tested 275 documents.
Across cities and counties already publishing agendas, minutes, budgets, and annual comprehensive financial reports (ACFRs), here's what automated accessibility testing found.
Fail outright
203 of those have no tag structure at all — to a screen reader, the document is unstructured output, not a document. This isn't an edge case. It's the default.
"Tagged" still fail
Someone, or some tool, tried. A tag tree that exists is not a tag tree that works — most tagged documents in the study still fail automated testing.
Files named "ADA" fail too
Files like Budget-Book-ADA-Compliant.pdf, posted in good faith as the accessible version — and still failing. Without verification, no one on staff can tell which version they actually published.
Your desktop checker disagrees
Look nearly clean in Adobe Acrobat's built-in checker while failing automated PDF/UA machine checks hard. The two most common government checking tools tell different stories — only one of them asks the question the way assistive technology does.
Your flagship documents fail worst
The audited annual financial statement — the most scrutinized document a government publishes — fails harder than routine agendas and minutes. The documents that get the most outside attention get the least accessibility treatment.
Progress doesn't carry forward
Of governments publishing two or more years of their ACFR, most regress year over year — several by 10x or worse. Whatever fix went in last year didn't become a standard; next year's document reverts to whatever the toolchain produces by default.
99.2% of every failure in the study — 14.68 million machine-check failures, across all 275 documents — traces to just two causes: content that was never tagged, and tags that exist but aren't bound to the content they describe. These aren't hundreds of separate problems. They're two systemic ones, repeated document after document. Which also means: fixable, at scale, with a repeatable process — not 275 bespoke jobs.
You can't fix everything in week one. Fix these first.
Prioritize by exposure, not by convenience:
1. Your ACFR and budget book
Highest scrutiny, worst failure rate, and the documents an auditor, reporter, or advocacy group downloads first. Fixing your flagship financial documents is also where the "tagged ≠ passing" gap is most visible if someone checks.
2. Anything already labeled "ADA" or "accessible"
A mislabeled document is worse than an unlabeled one — it tells a resident, and a reviewer, that the work is already done. Verify those first; they're your highest legal exposure per document.
3. The weekly stream, not just the backlog
Agenda systems and department uploads publish new PDFs every week. A one-time cleanup without a way to catch new documents is a backlog that starts refilling the day you finish it.
4. Whatever your traffic tells you
If you have web analytics on document downloads, use them. The guide above is a starting order for governments with no data yet — your own usage numbers should always win.
A guide tells you what's wrong. This is how we fix it.
If you'd rather not build this in-house, this is the process PairedUp runs for local governments end to end.
Audit
We inventory the documents already published on your website and test them with automated accessibility tooling. You get a prioritized map of what fails and what residents use most.
Remediate
We rebuild the document's structure so assistive technology can read it: real headings, real tables with working headers, described images, and correct reading order. The pages render exactly as they did before.
Verify twice
Every document is checked two ways: PDF/UA machine checks with veraPDF, plus our implementation of Adobe Acrobat's published accessibility rules, the same checker many government offices use. You can re-run either with tools you trust.
Publish back
Each fixed document comes back ready to replace the original at its existing web address, so links, bookmarks, and search results keep working. One click per document for your team, or give us a limited login and we handle the uploads too.
Confirm live
After the swap we re-test the copy actually being served from your website. A document is marked complete only when the public file is the passing file.
Stay fixed
We keep watching your site. New documents are flagged and queued automatically, including the weekly stream from agenda and meeting systems — the fix from Finding 6 above, built in.
Automated testing is necessary. It isn't sufficient.
Reading order, color contrast, and a handful of other checks still require human judgment — they're part of our process, and we don't count a document done until they're covered. When we say a document passes, we mean it passes the tests we name, and you can re-run those tests yourself.
Every document ships with its proof
Before and after results from automated accessibility testing, plus a private status portal your team can hand to a council member, an auditor, or anyone who asks.
Who this guide is for
City and county clerks, communications teams, ADA coordinators, and IT directors — the people who own the website, the records, and the deadline.
Zero homework to start
No inventory to compile, no files to send. Ask us for a private demonstration built from your own government's published documents — we prepare it before we ever meet, at no cost, from public records.
Still no form. Just a straight answer.
30 minutes: how big the job really is for your government specifically, what it takes to fix and stay fixed, and one clear next step. Or tell us your city or county and we'll run the same testing shown above against your own published documents first — before you talk to anyone.
Book 30 MinutesPick a time. That's it.