Legal & Compliance

DOJ Pushes ADA Title II Web Deadlines to 2027 and 2028

The DOJ extended its ADA Title II web accessibility compliance dates to 2027 and 2028, but the underlying nondiscrimination duties still apply now.

Khushwant Parihar
6 min read

The U.S. Department of Justice has extended the compliance deadlines for its 2024 ADA Title II web and mobile accessibility rule. Under an Interim Final Rule effective April 20, 2026, state and local government entities serving populations of 50,000 or more now have until April 26, 2027 to comply, while smaller entities and all special district governments have until April 26, 2028. The technical standard has not changed: covered entities must still meet WCAG 2.1 Level AA. Critically, the extension moves only the compliance date. Every other nondiscrimination obligation remains in full force today.

What the DOJ changed

In April 2024, the DOJ finalized a rule under Title II of the Americans with Disabilities Act requiring public entities to make their websites and mobile applications accessible. The new Interim Final Rule leaves that framework intact but pushes back the dates by which entities must demonstrate conformance.

  • Population of 50,000 or more: compliance now due April 26, 2027.
  • Population under 50,000, and all special district governments: compliance now due April 26, 2028.
  • Technical standard: unchanged at WCAG 2.1 Level AA.

The DOJ also signaled that it may pursue further rulemaking to revisit the technical standards themselves, per the Federal Register notice. For now, WCAG 2.1 AA remains the benchmark.

The obligations did not go away

It would be a mistake to read the extension as a reprieve. The ADA already prohibits public entities from discriminating against people with disabilities, and that prohibition applies to digital services right now. Extending the fixed compliance date does not create a safe harbor. Public entities can still receive complaints and face litigation over inaccessible websites and apps in the interim, and courts have long held that inaccessible digital services can violate the ADA independent of the 2024 rule.

Disability advocates were quick to object to the delay. The American Association of People with Disabilities (AAPD) criticized the extension, warning that pushing back the timeline prolongs the barriers that people with disabilities encounter when trying to access essential government services online.

The signal about possible future rulemaking adds a further wrinkle. The DOJ has indicated it may revisit the technical standards down the road, which introduces some uncertainty about what the long-term benchmark will be. That uncertainty is not a reason to wait, however. WCAG 2.1 AA is the standard on the books today, it is widely supported by tools and expertise, and conformance work done against it is unlikely to be wasted even if the standard is later refined. Building accessible pages remains the right investment regardless of how the rulemaking evolves.

Litigation risk has not paused

Because the extension moves only the fixed compliance date, it does nothing to shield public entities from the complaints and lawsuits that can arise under the ADA’s general nondiscrimination mandate. An inaccessible benefits portal or an unusable public-meeting page can still draw a complaint today. Entities that treat the new dates as a green light to stop work may find themselves defending litigation with no remediation progress to show. The safer posture is to keep documenting your accessibility efforts as you go, so that you can demonstrate good-faith, ongoing work rather than a stalled program.

What this means for you

For public entities and their vendors, the practical takeaway is simple: treat the original deadlines as the real target and keep remediating now. Accessibility work takes time, and an extra year is easily consumed by audits, procurement cycles, and content backlogs. Waiting until 2027 or 2028 to start invites both legal exposure and a last-minute scramble.

  1. Keep working against WCAG 2.1 AA today. A structured WCAG checklist helps you track conformance across pages, documents, and apps.
  2. Prioritize the services people rely on most: benefits applications, permitting, tax payment, emergency notifications, and public meeting information.
  3. Address existing barriers now, because complaints and lawsuits can still proceed before your compliance date arrives.
  4. Build accessibility requirements into every new contract, so third-party platforms and content do not reintroduce barriers.

For deeper background, see our overviews of ADA compliance and Section 508, and our detailed guide to the Title II deadline extension.

The bottom line

The DOJ has bought public entities more time to reach the finish line, but it has not moved the line itself or relaxed the standard. WCAG 2.1 AA is still the target, discrimination is still prohibited today, and litigation risk remains. Organizations that keep remediating steadily will be far better positioned than those that read the extension as permission to pause.

This article is general information, not legal advice.

Sources

Written by
Khushwant Parihar

Khushwant Parihar is the founder of Accessibility.build and an accessibility specialist, consultant, and developer with more than four years of professional accessibility and software testing experience. His work covers WCAG auditing, keyboard and screen-reader testing with NVDA, JAWS, and VoiceOver, accessible frontend implementation, remediation workflows, and team enablement.

Found this useful? Share it.

Prefer Accessibility.build on Google

Add us as a preferred source and Google will show our new articles and research more often in your Top Stories and AI Overviews.

Add as a preferred source on Google

Essential Accessibility Resources

Comprehensive tools, checklists, and guides to help you create inclusive digital experiences

Top Pick

Accessibility Laws by Jurisdiction

Global tracker of accessibility laws comparing WCAG requirements, penalties, and enforcement across 21 jurisdictions
ada title ii
accessibility compliance
View resource

Accessibility Lawsuit Tracker

Updated statistics on ADA and accessibility lawsuits by year, industry, and jurisdiction with settlement cost data
accessibility legal
ada compliance
View resource

ADA Compliance: Website Requirements & Legal Protection

Complete ADA compliance guide for websites including legal requirements, WCAG standards, implementation steps, and protection from accessibility lawsuits.
compliance:
legal
compliance
View article

Other posts filed under Legal & Compliance.

  • NFB v. DOJ: Could a Court Restore the Original Title II and Section 504 Web Deadlines?

    The National Federation of the Blind is asking a Maryland federal court to throw out the one-year extensions DOJ and HHS gave to the Title II and Section 504 web accessibility deadlines. We read the docket, the complaint and both interim final rules: what “good cause” means, what vacatur would do to dates that have already passed, and why you should not plan around the extension.

    Nov 18, 2026 · 14 min read

  • Website ADA Suits Keep Failing on Standing. That Does Not Make Your Site Accessible.

    A Chicago federal judge threw out a website accessibility suit against a shoe retailer in October 2026 because the blind plaintiff offered no evidence of standing. We read the opinion and the appellate cases behind it. Here is what standing means, why these wins are narrower than they look, and why the defendants who win tend to be the ones who had already fixed their sites.

    Nov 18, 2026 · 15 min read

  • ADA Title II After the Extension: Put Accessibility Into Your Vendor Contracts Now

    The DOJ gave state and local governments an extra year, but the Title II web rule still covers every website and app a public entity provides through a vendor. Here is what to write into contracts, how to read a vendor’s ACR without being fooled by a wall of “Supports”, and a clause checklist drawn from the rule, ADA.gov, GSA and Idaho.

    Nov 18, 2026 · 16 min read