The Department of Justice's 2024 rule under Title II of the ADA (28 CFR part 35, subpart H) requires state and local governments to make their web content and mobile apps meet WCAG 2.1 Level AA. That includes the PDFs, Word files and spreadsheets they post. This page explains what that means for a small public body's document library, in plain English.
This is general information, not legal advice. Check the current rule text and talk to your attorney or ADA coordinator about your situation.
Who is covered and when
Every state and local government entity is covered: cities, towns, villages, counties, public school districts, public colleges, libraries, transit agencies, courts, and special districts such as water, sewer, fire, park and hospital districts. In April 2026 the DOJ issued an interim final rule pushing the compliance dates back one year:
| Entity | Compliance date |
|---|---|
| Population of 50,000 or more | April 26, 2027 |
| Population under 50,000, and all special district governments | April 26, 2028 |
Which date applies to you
It depends on your government structure and population, not on enrollment or service area:
- School districts don't automatically get the special-district date. A city or county school district uses the city's or county's population. An independent school district uses its most recent Census Small Area Income and Poverty Estimates (SAIPE) population. At 50,000 or more, the date is April 26, 2027; below that, April 26, 2028.
- Departments use their parent government's population. A city library or city fire department is part of the city, so it follows the city's date.
- Special district governments, as the rule defines them (a separate government with one or a few functions whose population the Census doesn't calculate), have April 26, 2028.
Definitions: 28 CFR 35.104 ("special district government", "total population"). Plain-English explanation: DOJ small entity compliance guide.
The extension changed the dates, not the standard. The general duty to make services accessible to people with disabilities applies already, regardless of the dates.
Which documents are covered
Anything you post on your website or apps going forward, including meeting agendas, minutes, packets, public notices, budgets, annual reports, newsletters, maps, applications and forms. There are exceptions in 28 CFR 35.201, and two of them matter most for document libraries:
Preexisting conventional electronic documents
Word, PDF, presentation and spreadsheet files posted before your compliance date generally don't have to be fixed, unless they are currently used to apply for, access or take part in your services. A 2019 permit application that people still download is covered; last decade's minutes usually are not.
Archived web content
Old content kept only for reference, research or recordkeeping, not changed since it was archived, and kept in a clearly marked archive area. All four parts of the definition must hold.
Exceptions don't apply if someone with a disability asks for a document; you still owe them an accessible version in a timely way. And anything you post or update after the compliance date has to conform.
A practical plan for a document backlog
- Inventory. List every document on the site with its posting date and whether people use it to get a service (forms, applications, current fees, schedules, notices).
- Triage. Fix documents people use to access services first, then everything new. Move true archive material to a clearly labeled archive section.
- Fix the template, not just the files. Most new PDFs come from Word. A Word template with real heading styles, alt text habits and a set document title makes future exports nearly accessible by default.
- Consider HTML instead of PDF. Agendas, notices and short reports are often easier to make accessible, and easier to read on a phone, as a web page.
- Check, then check by hand. Automated checkers catch missing tags, titles and alt text; a person has to confirm the reading order, table headers and that alt text says something useful.
The checklist a PDF has to pass
- It is a tagged PDF with a structure tree, not just an image or untagged text.
- The document language is set, and the title is set and shown instead of the file name.
- Headings are tagged in order (one top-level heading, no skipped levels).
- Lists are tagged as lists; tables have header cells, and simple layouts don't use tables.
- Every informative image, chart and map has alt text that gives its information; decorative images are marked as artifacts.
- The reading order matches the visual order, including multi-column pages.
- Text has enough contrast, and color is never the only way information is shown.
- Scanned pages are OCR'd into real text and tagged.
- Forms have labeled, keyboard-reachable fields.
- Links describe where they go.
Try the free quick check on one of your PDFs to see which of the basics it already has. It runs in your browser and doesn't upload the file.
Want the backlog done for you?
I rebuild documents as tagged PDFs plus accessible web pages, checked against WCAG 2.1 AA by automated pre-checks and a manual checklist. A free 2-page sample comes first, so you can verify the result in your own checker. Typical pricing is a few dollars a page. Hire me on Upwork or email aaron.signalfeed@gmail.com.
Sources
- 28 CFR part 35, subpart H (eCFR), including the exceptions in 35.201
- ADA.gov fact sheet on the web rule
- April 2026 interim final rule extending the dates
- WCAG 2.1 (W3C)
Free template: start from an accessible meeting agenda template for Word whose example PDF passes veraPDF PDF/UA-1, or get the full template pack ($24): agenda, minutes, notice and budget.