The ADA Title II Deadline Moved to April 2027. What Did Not Change

What did not change

Everything that determines how much work there is stayed where it was. The Justice Department’s fact sheet and the regulation at 28 CFR part 35, subpart H describe the same obligations they did before the extension.

If your team already planned to WCAG 2.1 AA, the plan is still right. If you planned to WCAG 2.2 AA, that still covers 2.1 AA; the W3C keeps the 2.1 criteria essentially the same in 2.2 apart from removing 4.1.1 Parsing. The differences are set out in WCAG 2.1 vs 2.2.

Documents deserve a second look in light of the new date. The preexisting-document exception covers word processing, presentation, PDF and spreadsheet files posted before your compliance date, unless they are still used to apply for, access or take part in a service. Moving the date one year later also moves that cutoff, but any form people use today to request a permit, pay a bill or enroll in a program is covered regardless of when it was posted. Those documents are usually the slowest part of the work, because each one has to be rebuilt or remediated and then checked by hand.

Why waiting for the new date is still a risk

The extension buys time, not less work. Three things make the last few months before a deadline the worst time to start:

• Remediation takes longer than it looks. An automated scan finds repeated template errors quickly, but keyboard, focus and screen reader issues need manual testing, and every fix needs a retest.
• Procurement runs on its own clock. Content provided through contractors is covered, so vendor portals and hosted tools need contract language and vendor fixes, which follow budget and renewal cycles.
• Content keeps arriving. Every new page, PDF and app release after the compliance date is covered. The preexisting-document exception applies only to files posted before your date and not used to access services.

The starting point is not encouraging. In our scan of 95 California government homepages, 66.3% had at least one automatically detected WCAG 2.1 A/AA failure, and automated tools find only part of what a full audit does.

One clarification that gets lost: the extension is about governments. Businesses open to the public are under Title III, and the Justice Department’s 2022 web guidance says the ADA’s requirements apply to the goods and services public accommodations offer on the web. There is no Title III date to wait for. The distinctions are in Section 508 vs ADA vs WCAG.

What to do this quarter

1. Confirm your population tier and write the date on the project plan.
2. Inventory every site, portal, app and in-use document, including vendor-hosted ones.
3. Run an automated pass with our accessibility checker and sort failures by template.
4. Fix shared templates first: navigation, forms, footers, page layouts.
5. Add WCAG 2.1 AA (or 2.2 AA) conformance and test evidence to contracts at renewal.
6. Publish an accessibility statement with a way to report barriers.

The criteria to test against are listed one by one in the WCAG 2.2 checklist, and our accessibility audit and remediation service covers the manual testing tools cannot do.

Frequently asked questions

About the work

Webvello is a web development and AI search optimization company founded in 2024, based in Roseville, California, with 50+ projects across 37+ cities. We test our own site with the same automated tooling we use in audits. Founder George Shvaya came to the web from cybersecurity and systems engineering.

This page is general information, not legal advice. Dates are from the Federal Register interim final rule (91 FR 20902) as checked on October 17, 2026; read the current regulation before relying on them.