ADA Title II website accessibility: what local governments need to do
Updated 2026-11-16
In 2024 the US Department of Justice published a rule under Title II of the Americans with Disabilities Act that sets a clear technical standard for the websites and mobile apps of state and local governments. This guide summarises what it requires and the current dates.
Who is covered
State and local governments and their agencies, including cities, counties, school districts, public universities, libraries, transit agencies and special districts such as water, fire and park districts. It covers their websites, mobile apps and the documents they publish online, including content provided through contractors.
The standard
Web content and mobile apps must meet the Web Content Accessibility Guidelines (WCAG) version 2.1, Level AA. In practice that covers things like text alternatives for images, captions for video, enough colour contrast, forms that work with a keyboard and a screen reader, and documents such as PDFs that assistive technology can read.
Compliance dates
| Public entity | Comply by |
|---|---|
| Total population of 50,000 or more | 26 April 2027 |
| Total population under 50,000, and all special district governments | 26 April 2028 |
These dates were set by an interim final rule in April 2026, which moved the original 2026 and 2027 dates back by one year. The technical standard did not change. Dates were correct when this guide was updated; check ADA.gov for any later change.
Exceptions
The rule has a small number of exceptions, for example for some archived web content that is kept only for reference and is not changed, and for some documents created before the compliance date. The conditions are specific, so check the ADA.gov fact sheet before relying on one.
Practical first steps
- Take stock. List your websites, apps, and the PDFs and other documents you publish, including those run by vendors.
- Test. Automated tools quickly find many common problems; a person needs to check the rest. You can check one page free.
- Fix the templates first. A problem in a site-wide header or menu repeats on every page, so fixing it once has the biggest effect.
- Sort out documents. Scanned PDFs without real text are a common problem for small bodies. Decide what to fix, what to convert to web pages, and what can be archived.
- Talk to your vendors. Ask your website provider what they will fix and by when, and put accessibility into contracts.
- Publish an accessibility statement with a way for people to report problems and ask for content in another format.
How we can help
Our Accessibility Readiness Pack crawls up to 200 pages and 50 PDFs, groups repeated issues by template, ranks the top fixes, gives separate lists for your web vendor and content editors, and includes a draft accessibility statement. It describes issues found and is not legal advice or a certificate of compliance.
Questions
Does the Title II rule apply to small towns?
Yes. Public entities with a total population under 50,000, and all special district governments, are covered, with a later compliance date of 26 April 2028.
Which WCAG version does the rule require?
WCAG 2.1 Level AA.