ADA Title II web rule: WCAG 2.1 AA deadlines for state and local governments

Who must comply with the Title II web rule?

The rule applies to all state and local governments, which the ADA calls public entities. The Department of Justice names, among others:

• counties, cities, towns and state agencies;
• special purpose districts, for example transit, utility, water and sewer or mosquito abatement districts;
• public schools, including course content in a learning management system;
• public universities and colleges;
• public libraries, treated like any other public entity;
• public hospitals, including a patient portal;
• Amtrak and commuter authorities.

Vendors and contractors are not a way out. When a government uses a contractor or another arrangement to provide web content or an app, the government is still responsible for its accessibility. For a web agency this means: a government client will expect WCAG 2.1 AA in the contract.

How is the population size determined?

The deadline depends on the population of the public entity, taken from U.S. Census Bureau data:

• in general, the 2020 decennial Census;
• independent school districts use the 2022 Small Area Income and Poverty Estimates;
• an entity without its own Census population uses the population of the government it belongs to — a state university counts the population of its state;
• special district governments have no Census population and get the later date.

The number of employees or of people served does not matter.

What are the compliance dates?

The final rule of 24 April 2024 gave governments three or four years. On 20 April 2026 the DOJ published an interim final rule that moved both dates by one year:

Only the dates changed. The standard and the exceptions are the same as in 2024.

What does the rule require?

Web content and mobile apps that a state or local government provides or makes available, directly or through others, must conform to WCAG 2.1 Level AA. That covers the 50 success criteria of levels A and AA: text alternatives, captions, colour contrast, keyboard access, visible focus, form labels and error messages, reflow at 320 px and more. The criteria are explained in plain words in our WCAG guide and the differences to the newer version in WCAG 2.1 vs 2.2.

What are the five exceptions?

1. Archived web content: created before the compliance date, kept only for reference or recordkeeping, stored in a special archive area and not changed since. All four conditions must be met.
2. Preexisting conventional electronic documents: PDF, word processing, presentation and spreadsheet files posted before the compliance date — unless they are still used to apply for or access a service.
3. Content posted by third parties, such as public comments, when the third party is not posting under a contract or other arrangement with the government.
4. Individualized, password-protected documents about a specific person, property or account, for example a bill for one account.
5. Preexisting social media posts made before the compliance date.

Everything new — pages, forms, documents people need to use a service — has to meet WCAG 2.1 AA.

Which other provisions matter?

• Fundamental alteration and undue burden: as elsewhere in Title II, a government does not have to take actions that would fundamentally alter a service or impose an undue burden.
• Conforming alternate versions are allowed only where a technical or legal limitation prevents making the content itself accessible.
• Equivalent facilitation: another solution is acceptable if the government can show that it provides the same or more accessibility and usability.
• Minimal-impact noncompliance: a government that misses WCAG 2.1 AA in a way that has minimal impact on access may not be in violation, but it cannot use this rule to avoid trying to meet WCAG 2.1 AA.

How does Title II differ from Title III and Section 508?

Private businesses are covered in ADA website compliance; the federal rules in Section 508.

What should agencies building government sites do now?

1. List what you run for public clients: websites, portals, apps, forms, PDFs that people need to use a service.
2. Check the templates first: header, navigation, forms and footer appear on every page, so one fix repairs hundreds of pages.
3. Test automatically and by hand: an automated scan finds part of the problems; keyboard, screen reader and zoom tests find the rest. The ADA website checklist lists both.
4. Fix new content first: the exceptions protect only older content; everything published after the date counts.
5. Document conformance: many public buyers ask for an accessibility conformance report — see VPAT and ACR.
6. Write accessibility into contracts: WCAG 2.1 AA as acceptance criterion, with retesting after changes.

How Pandus helps

Pandus checks pages automatically against WCAG 2.2 AA. WCAG 2.2 AA contains every WCAG 2.1 AA criterion except the removed 4.1.1 Parsing, so the result also covers the automatable part of the Title II standard. Agencies get weekly monitoring of all client sites, reports in plain words and white-label reports for their clients. Try one page in the free ADA compliance checker. It is an automated check, not a full audit, and not legal advice; it does not make any site meet the ADA by itself.

Frequently asked questions

When is the ADA Title II web deadline?

After the interim final rule of 20 April 2026: 26 April 2027 for public entities with a population of 50,000 or more, and 26 April 2028 for smaller ones and all special district governments.

Which standard does the Title II rule require?

WCAG 2.1 Level AA, for web content and for mobile apps that a state or local government provides or makes available.

Does the Title II rule apply to private businesses?

No. It applies to state and local governments. Private businesses fall under Title III, for which the Department of Justice has not issued a web regulation. See ADA website compliance.

Are vendors and contractors covered?

The government stays responsible for web content and apps that vendors or contractors provide for it, so agencies that build or run government sites have to deliver WCAG 2.1 AA.

Is there an official ADA Title II compliance checker?

No. No federal agency runs or certifies a checker. Automated tools test the part of WCAG 2.1 AA that software can detect; manual testing is still needed. Our ADA compliance checker is such an automated check.

Sources

• ADA.gov: Fact sheet on the Title II web and mobile app rule
• ADA.gov: First steps toward complying with the Title II web rule
• Federal Register: Extension of compliance dates, interim final rule of 20 April 2026
• ADA.gov: Guidance on web accessibility and the ADA (Title III)
• Section508.gov: Laws and policies and Revised 508 Standards fact sheet

Last checked: 14 October 2026. This page is general information, not legal advice.