Accessibility

The ADA Title II Web Accessibility Deadlines Just Changed. Here’s What You Need to Know.

Published on:
Calendar with the 26th circled in orange, beside an alarm clock and a checklist with three checked boxes on a blue background

If you manage a website for a state or local government and you have been bracing for a 2026 accessibility deadline, take a breath. The Department of Justice recently pushed those dates back, and the new timeline gives most entities another year to get compliant.

That said, an extension is not a pass. The requirements have not changed, only the calendar has. Here is what is actually due, who has to meet which deadline and what needs to be compliant before the clock runs out.

What Is This Rule and Where Did It Come From?

In April 2024, the Civil Rights Division of the Department of Justice finalized a rule under Title II of the Americans with Disabilities Act. Title II covers state and local governments, along with the nonprofits and businesses that contract with them to provide services on their behalf.

The rule set a clear technical standard for the first time. State and local government websites and mobile apps must conform to WCAG 2.1 Level AA. Before this, agencies knew accessibility was an obligation but had no measurable target to build toward. The result was years of inconsistent effort and, in many cases, websites people with disabilities simply could not use.

In other words: If your organization is a state or local government, you build and maintain digital content on their behalf or contract with them to provide a service to the public, WCAG 2.1 AA is now the bar you have to clear.

What Changed in April 2026?

On April 20, 2026, the Department of Justice issued an Interim Final Rule that extended the original compliance deadlines. The extension applies to both categories of entities covered by the rule. Everything else about the requirement stayed the same.

The reason to care about this is timing. 

If you were planning remediation around the old dates, your runway just got longer. If you hadn’t started yet, this is the window to begin without scrambling.

Who Has to Comply and by When?

Your deadline depends on population size. There are two tiers, and the extension pushed both back by one year.

Public entities with a total population of 50,000 or more 

Original deadline: April 24, 2026.
New deadline: April 26, 2027.

Public entities with a total population of less than 50,000 and any special district government 

Original deadline: April 26, 2027.
New deadline: April 26, 2028.

Businesses Under Contract With Title II Entities

If you contract with a Title II entity to provide services on its behalf, these guidelines apply to you too. You follow the deadline that matches that entity’s category.

A vendor building a site for a large city inherits the large-entity deadline, while a vendor serving a small special district inherits the later one. That covers a wider range of organizations than most people expect. Here are a few examples:

  • Nonprofits that operate drug treatment programs on behalf of a state or local government agency
  • Convenience stores contracted to sell state lottery tickets
  • Private companies that run mobile parking payment apps that a city uses to let the public pay for parking, such as ParkMobile
  • Local web design, hosting or technology companies hired to build, manage or update government web content, like an hours page for a county park
  • Private entities contracted to operate and offer services at a state park lodge

Not sure whether your entity clears the 50,000 line? That comes down to how the ADA defines population, which is where a lot of people get tripped up. It is not about how many people visit your website or use your service. It refers to the census population of the jurisdiction the entity belongs to.

In most cases, the number comes from the most recent decennial census population estimate calculated by the U.S. Census Bureau. A few special situations worth knowing:

  • Independent school districts use the district population estimate from the most recent Small Area Income and Poverty Estimates.
  • Instrumentalities or commuter authorities without their own census population use the combined population of the state or local governments they belong to.
  • The National Railroad Passenger Corporation (Amtrak) uses the population of the entire United States.

In other words: Find the jurisdiction you are part of, look up its census population and that tells you which deadline applies to you.

What Actually Needs to Be Compliant?

The standard is WCAG 2.1 Level AA. That covers the web and mobile app content your entity provides or makes available to the public. In practice, that means the working parts of your site people rely on to access your services, programs and activities.

There are a handful of narrow exceptions where specific content does not have to meet the technical standard. Note that these apply only to the content that fits the exception, not to your whole site.

  • Archived web content that was created before your compliance date, is kept only for reference or recordkeeping, is not updated and lives in a clearly marked archive area.
  • Pre-existing conventional electronic documents such as PDFs, word processor files, presentations and spreadsheets that were posted before your compliance date, unless people currently use them to apply for, access or participate in your services.
  • Content posted by a third party that is not posting under a contract or arrangement with your entity.
  • Individualized, secured documents that are about a specific person’s property or account and are password-protected.
  • Pre-existing social media posts published before your compliance date.

These Exceptions Have Conditions

Even when content falls under an exception, you are not off the hook entirely. If someone with a disability requests an accessible version, you may still have to provide it under your existing effective communication obligations. An archived set of meeting minutes might be exempt from WCAG conformance, but if a person with low vision asks for an accessible copy, you still need to accommodate that request.

What Happens If You Miss the Deadline?

Noncompliance carries financial and legal exposure. The ADA gives people with disabilities the right to file suit in federal court, and the Justice Department can bring its own enforcement actions in cases of general public importance. Penalties can reach up to $75,000 for a first violation and up to $150,000 for each additional one, and losing entities can be on the hook for the government’s attorney fees.

The Department has already brought enforcement actions against public entities over inaccessible websites and apps, and several ended in settlement agreements. In most cases, the cost of compliance is far lower than the cost of a violation.

A Few Best Practices Worth Building In

Meeting the standard is the requirement. These steps make it easier to demonstrate good faith and support your users along the way.

Publish an accessibility statement. It is not explicitly required by the rule, but it is a strong best practice. A good statement names the standard you are conforming to, explains how people can request help or file a complaint and lists any known issues you are actively working on.

Give people a clear path to request accessible alternatives. Especially for content that falls under an exception, users need an obvious way to ask for an accessible version and a reasonable expectation of getting one.

Document your remediation process. Keep a record of what you have fixed, what is in progress and how you handle requests. It supports your compliance posture and keeps the work organized.

Where to Start

The extended deadlines give you room, but the smartest move is to treat that room as time to work rather than time to wait. Start by identifying which tier you fall under, then audit your existing site against WCAG 2.1 AA to see how far you have to go.

If you are not sure where your organization stands or where to begin, we’re happy to help! Reach out to learn more about our accessibility services.