ADA Title II web accessibility rule: deadlines, WCAG 2.1 AA and what to check
The Department of Justice rule that requires state and local government websites and mobile apps to meet WCAG 2.1 Level AA: who it covers, when it applies, what is exempt, and how to check your site.
The short version
| Who must comply | State and local government entities under ADA Title II, including special district governments |
|---|---|
| Standard | WCAG 2.1 Level A and Level AA (Level AAA is not required) |
| Covers | Websites and mobile apps, including content provided through vendors and contractors |
| Deadline: population of 50,000 or more | April 26, 2027 |
| Deadline: under 50,000, and special districts | April 26, 2028 |
| Rule published / in effect | April 24, 2024 / June 24, 2024 |
| Extension | DOJ interim final rule of April 20, 2026 moved each original deadline back one year |
General information, not legal advice. The dates above reflect the DOJ’s April 2026 extension as described in the sources listed at the end of this page. Confirm current dates and rule text on ada.gov before you rely on them.
Who the rule covers
The rule applies to state and local governments: for example cities, counties, public school districts, public colleges and universities, and special district governments. It does not apply to private businesses, which are covered by ADA Title III instead (see the guide to ADA website lawsuits).
It reaches beyond content you host yourself. If a vendor or contractor provides a payment portal, permit system or meeting-agenda tool on your behalf, that content is covered too.
What the standard requires
Web content and mobile apps must meet the Level A and Level AA success criteria of WCAG 2.1, unless the entity can show that compliance would fundamentally alter the service or impose an undue financial and administrative burden. Level AAA is not required.
In practice that means things like text alternatives for images, sufficient color contrast, full keyboard operation, labeled form fields, captions on prerecorded video, and a page structure that screen readers can follow.
What is exempt
The rule lists five exceptions. Each is narrower than it sounds, so read the conditions before you rely on one.
- Archived web content. Only if it is kept solely for reference, research or recordkeeping, stored in a clearly labeled archive area, and meets the rule’s other conditions. Calling a page “archived” is not enough.
- Preexisting documents. PDF, Word, PowerPoint and Excel files posted before the compliance date are generally exempt, unless people currently use them to apply for or access your services. A file you change after the compliance date loses the exemption.
- Third-party content. Content posted by members of the public, such as comments on a message board, unless it exists through a contract or other arrangement with you.
- Password-protected individualized documents. Documents about a specific person, property or account that are secured by a password. HTML pages do not qualify, and you must still provide an accessible version when someone needs one.
- Preexisting social media posts. Posts made before the compliance date. Posts made after it must comply.
A practical checklist
- Inventory. List every website and mobile app, including the ones run by vendors on your behalf.
- Start with services. Find the forms, PDFs and portals people use to apply for or access services. Those matter most.
- Scan. Run an automated scan across the whole site and its documents, and fix Level A and AA failures first.
- Test by hand. Check key pages using only a keyboard, with a screen reader, at 200% zoom, and check that video has captions.
- Fix the contracts. Require WCAG 2.1 AA from vendors and ask for a current Accessibility Conformance Report (VPAT).
- Retest and keep records. Keep a dated record of what you found and what you fixed.
- Monitor. New pages and documents break things again. Rescan on a schedule.
What an automated scan can and cannot do
A scanner finds the problems software can decide: missing alternative text, low color contrast, unlabeled form fields, empty links, and similar. It cannot judge whether alternative text is meaningful, whether the reading order makes sense, or whether a flow works with a screen reader. Use a scan to find and prioritize the mechanical failures, then test the rest by hand. A clean scan is not proof of conformance.
Checking your site with WCAGScan
WCAGScan crawls your pages and linked documents, tests them against WCAG 2.0, 2.1 and 2.2, and emails you an interactive report and a PDF. Every issue lists the page URL, the success criterion, its level (A, AA or AAA), the failing code and an example of a fix, and items that need a human check are labeled as such.
- Free scan: up to 5 pages, no account needed.
- Starter: $49 per scan, up to 50 pages.
- Growth: $149 per scan, up to 500 pages.
- Monthly monitoring: from $39 per month, with the score change emailed to you.
Run a free scan of your homepage or see pricing.
Common questions
Does the Title II rule apply to private businesses?
No. It covers state and local government. Private businesses fall under Title III, which has no web-specific regulation, although courts and plaintiffs commonly use WCAG 2.1 AA as the benchmark.
Is WCAG 2.2 required?
The rule names WCAG 2.1 Level AA. WCAGScan also tests the newer 2.2 criteria, which you can treat as an additional margin.
Do old PDFs have to be fixed?
Generally not, if they were posted before your compliance date and nobody currently uses them to apply for or access your services. Any file you update afterwards is no longer exempt.
Sources
- UNC School of Government, Coates’ Canons, Understanding the New ADA Web Accessibility Requirements for State and Local Governments (January 2026, with an update on the April 2026 extension).
- Clockwork Web Design, ADA Title II Web Accessibility Deadline Extended to April 2027.
- U.S. Department of Justice, ada.gov, for the rule text and current dates.