Do Documents on Government Websites Have to Be Accessible?

Under the ADA Title II web rule, documents that state and local governments publish online, including PDFs, Word files, and spreadsheets, must meet WCAG 2.1 AA once the compliance date applies. Some documents posted before that date are exempt, but a document residents use to apply for or access a service, such as a form, is not.
For many small governments, documents are how agendas, minutes, budgets, and permit forms reach residents, and PDFs are the most common source of accessibility failures. The more useful question is which documents to fix first and how to stop creating new problems.
What Does the ADA Title II Rule Say About Documents?
The DOJ’s rule covers the web content and mobile apps of state and local governments, including documents posted online such as PDFs, Word files, and spreadsheets. It sets WCAG 2.1 Level AA as the standard.
The compliance dates depend on population. After DOJ extended them in April 2026, governments serving 50,000 or more residents have until April 26, 2027, and smaller governments and special districts have until April 26, 2028.
A government also remains responsible for content provided through a contractor or vendor, so a PDF that a vendor posts for you counts as yours. Our ADA/Accessibility page and the DOJ’s first steps guidance are good places to start.
Which Documents Are Exempt, and Which Are Not?
Some documents are exempt, but the exceptions are narrower than they first appear. The rule’s exceptions include archived web content kept only for reference or record-keeping, clearly set apart and left unaltered; preexisting documents (PDF, Word, Excel, PowerPoint) posted before the compliance date; content posted by third parties outside a government contract; individualized, password-protected documents; and preexisting social media posts.
The key point is that the preexisting-document exception doesn’t cover documents residents use to apply for, access, or take part in a service, and it doesn’t cover anything new or updated after the date. A current permit application is in scope. Next month’s agenda packet is in scope. An old set of minutes in a designated archive may be exempt.
Confirm how these exceptions apply to your situation with legal counsel, since the details matter.
Why Do So Many PDFs Fail Accessibility Checks?
Most failures come from how the file was made, not from what it says. Common problems include scanned pages with no readable text, missing tags and headings, no document title or language, tables without header rows, images without alt text, form fields without labels, low contrast, and a reading order that jumps around.
Here’s what that means for a resident using a screen reader. Take a scanned council agenda packet. To the software it’s a stack of pictures, so it announces a blank page or reads fragments in the wrong order. The resident can’t tell what’s on the agenda, can’t find the item they came for, and can’t ask a clerk at the counter for help.
How Do You Make Documents Accessible? Start with HTML Where You Can
Start by publishing text-heavy content as a web page, then make whatever documents remain accessible. HTML is easier to keep accessible and usually performs better in search.
For documents that need to stay as files, build accessible source files with real headings, alt text, and table headers, then export to a tagged PDF. Run the accessibility checker in your PDF software, and follow it with a manual read-through using a keyboard or screen reader. For scanned PDFs, run text recognition and recheck the reading order.
Then prioritize. Fix current forms and applications first, then high-traffic documents, then new agendas and minutes going forward. Retire outdated documents instead of remediating everything.
One caution: offering an accessible copy only “on request” is generally not a substitute for making the content accessible, so confirm your approach with counsel.
How Does CivAll Make Document Accessibility Easier?
In two ways. CivAll Sites, our accessible government website CMS, helps you publish agendas, notices, and forms as accessible web content first, so fewer documents exist only as PDFs. It also keeps content organized so outdated files can be retired or archived cleanly.
For the documents that remain, most of which are PDFs, CivAll Documents automates accessibility. Your original files stay unchanged, and an accessible copy is created for each one. Residents can use the resident reader to switch between the Original and Accessible versions, so they don’t have to ask for another format.
You don’t need to change your website platform to use it. CivAll Documents works with any website, and it’s available with Sites or on its own. CivAll serves 200+ government organizations. No tool replaces a review by someone who knows your documents, so keep your own spot checks in place.
Frequently Asked Questions
Are old documents on a government website exempt from the ADA Title II rule?
Often, if they were posted before the compliance date and aren’t used to access a service. Anything new, updated, or tied to a service is covered.
Are scanned PDFs accessible?
Not unless text recognition has been applied and the tags and reading order are checked. To a screen reader, a scan is an image.
Do meeting agendas and minutes have to be accessible?
New ones posted after the compliance date are in scope. Publishing them as web pages, or building them from accessible templates, keeps the workload manageable.
Is HTML better than PDF?
Usually, yes, for text-heavy content. Keep PDFs for fixed-layout or print needs, and make those accessible.
Do we need to change our website platform to fix document accessibility?
No. CivAll Documents works with any website, so you can add it without switching platforms.
Make Accessible Documents a Habit
Accessible documents become manageable when they’re a publishing habit instead of a cleanup project. Starting with current forms and new documents stops the backlog from growing while older files are handled over time. See how CivAll Documents and CivAll Sites support accessible publishing.


