ADA Title II Web Accessibility Rule: Deadlines, Scope and What to Do

The ADA Title II web accessibility rule requires state and local governments to make their websites and mobile apps conform to WCAG 2.1 Level AA. After an April 2026 extension, entities serving 50,000 or more people must comply by April 26, 2027, and smaller entities and special districts by April 26, 2028.

That is the answer as of 20 October 2026. The rule also reaches the private companies that build and run digital services for public entities, which is why agencies, SaaS vendors and contractors should read it too. Below we cover what changed, what did not, who is covered, the exceptions, and a practical plan. Every date comes from the Federal Register or ADA.gov, linked in the sources at the end. This is general information, not legal advice.

The short answer, as of October 2026

The rule is final and in force, but the dates to comply moved by one year in April 2026. The technical standard did not change. Here is where things stand on the day this was written, 20 October 2026, taken from the Federal Register and ADA.gov.

Three things are true at once, and most articles online only report one of them:

• The extension is real and already effective. The Department of Justice published it as an interim final rule on April 20, 2026 (91 FR 20902), effective the same day. Public comments closed on June 22, 2026.
• The content of the rule may still change. In that same document DOJ said it "plans to engage in future rulemaking processes related to the substantive requirements of the 2024 final rule" and "will consider issuing an NPRM" (a notice of proposed rulemaking). As of 20 October 2026 we found no proposed rule published in the Federal Register under the rule's identifier (RIN 1190-AA82). Nothing has been proposed yet, so there is nothing to report as "proposed".
• The extension itself is being challenged. In May 2026 the National Federation of the Blind sued DOJ and the Department of Health and Human Services in federal court, arguing the extensions were issued without the notice and comment the Administrative Procedure Act requires (Government Executive, May 27, 2026). We found no ruling as of this writing.

If you are planning work, plan against the current dates, and keep an eye on both the DOJ docket and the lawsuit. DOJ itself said that if it does not issue a new proposal and nothing else justifies more delay, it "fully anticipates implementing the regulation at the new deadline."

This article is general information for planning, not legal advice. If your organization is covered, confirm your obligations with your counsel.

What the rule actually requires

The rule requires that web content and mobile apps a state or local government provides, or makes available, conform to WCAG 2.1 Level AA, subject to a short list of exceptions. That is the whole core of it.

It was published on April 24, 2024 (89 FR 31320) and added a new subpart to DOJ's Title II regulations at 28 CFR 35.200 to 35.205. Before this rule, Title II already required governments to make their services accessible, but there was no technical yardstick. Now there is one.

Why WCAG 2.1 and not 2.2

WCAG 2.1 was the version DOJ adopted, and the 2026 extension left it alone. WCAG 2.2 exists and adds nine success criteria, but the legal requirement under this rule is 2.1 AA. In practice we recommend building to 2.2 AA anyway, because it costs little extra on a new build, it is backward compatible with 2.1 apart from one removed criterion, and newer standards in Europe already point to it. Our WCAG 2.2 checklist lists the differences in plain language.

What "web content" and "mobile apps" include

The rule is broad. It covers public websites, but also login areas, online forms, payment portals, document libraries, video, and native mobile apps. The ADA.gov fact sheet gives examples that matter to anyone in the vendor chain: a county web page built by a web design company, and a city parking app run by a private company, are both covered because the government provides them through an arrangement (ADA.gov fact sheet).

Typical things that end up in scope for a city, county, school district or transit agency:

• The main website and every department microsite
• Online permit, license and benefit applications
• Utility bill payment and parking payment portals
• Court, tax and property record lookups
• Meeting video, agendas and minutes
• Learning management systems and course content in public schools and colleges
• Mobile apps for transit, 311 requests, recreation booking and alerts
• Social media posts made after the compliance date

Who is covered, including contractors

The rule covers every state and local government entity: states, counties, cities, towns, their agencies and departments, public schools and public colleges, special purpose districts, and commuter authorities. Size does not create an exemption. It only changes the date.

How "total population" is counted

The date depends on the population of the jurisdiction, not on the number of employees. For most governments that is the 2020 Census figure. A department or agency without its own population, such as a city library or police department, uses the population of the government it belongs to. School districts follow a specific method that uses city, county or Census poverty estimate figures (ADA.gov). A special district government, such as a water, fire or mosquito control district, gets the later 2028 date regardless of size.

Where contractors and vendors fit

This is the part private companies most often miss. The legal duty sits with the public entity. But the rule applies to content the entity provides "directly or through contractual, licensing, or other arrangements". ADA.gov puts it plainly: governments that contract out services must make sure their contractors follow Title II.

In practice the obligation travels into your contract. If you are a private company in any of these roles, expect it to land on you:

The extension does not take vendors off the hook. Procurement teams write requirements months or years ahead, and many RFPs already reference WCAG 2.1 AA. A vendor that cannot show conformance loses the bid, whether or not the deadline has arrived. If you sell into the public sector, accessibility is now a sales requirement, not just a compliance one.

The five exceptions, and their limits

The rule lists five exceptions. Each one is narrow, and each has conditions. Treating them as loopholes is the most common planning mistake we see.

Two more points from ADA.gov are worth knowing. First, the exceptions do not remove the general ADA duties of effective communication and reasonable modification, so if a resident asks for an accessible version of an excepted document, the entity still has to respond. Second, "conforming alternate versions", meaning a separate accessible page alongside an inaccessible one, are allowed only where a technical or legal limitation prevents the main content from being made accessible. A separate "accessible version" of the site is not a substitute for fixing the real one.

Why the dates moved

DOJ gave several reasons in the interim final rule. They are worth reading because they hint at what a future proposal might address.

• Resources and staffing. DOJ cited resource constraints and staffing limitations reported by public entities.
• Technology. DOJ said tools, including generative AI, do not yet reliably automate remediation of inaccessible content.
• Litigation risk. DOJ argued that more time would let entities spend money on compliance rather than on defending lawsuits.
• Course content confusion. The 2023 proposal had exceptions for some course content at public schools and colleges. The 2024 final rule removed them, and DOJ said entities needed time to adjust.

DOJ also acknowledged the cost to disabled residents: during the extra year, a person may have to request an accessible version of a document and wait for it. That trade-off is the core of the lawsuit now pending.

A parallel rule for healthcare and HHS-funded organizations

If you build for hospitals, clinics, health departments or other recipients of HHS funding, there is a second, separate rule under Section 504 of the Rehabilitation Act. HHS extended its web and app dates in an interim final rule published May 11, 2026 (91 FR 25496): recipients with 15 or more employees moved from May 11, 2026 to May 11, 2027, and recipients with fewer than 15 employees from May 10, 2027 to May 10, 2028. Note that the HHS rule counts employees, not population.

What to do now

Use the extra year to do the work in the right order, not to wait. Retrofitting a large site in a rush in early 2027 will cost more than steady work starting now. Here is the order we use with public sector and vendor clients.

1. Inventory everything. List every domain, subdomain, portal, third-party platform, app and document library. Include the ones run by vendors. Most entities find more than they expected.
2. Rank by use and by consequence. Start with the services people must use: applications, payments, appointment booking, emergency information, and anything tied to a deadline or a benefit. A brochure page about park history comes later.
3. Run an automated scan, then test by hand. Automated tools catch the mechanical issues quickly. They miss a large share of real barriers, so add keyboard-only testing, screen reader checks and zoom testing on the key journeys.
4. Fix templates first. One fix to a shared header, navigation or form component fixes it on every page that uses it. This is where most of the savings are.
5. Deal with documents deliberately. Decide which PDFs to remediate, which to turn into HTML pages, and which can be archived properly under the exception's conditions.
6. Put it in contracts. Require WCAG 2.1 AA (or 2.2 AA) in every new purchase and renewal, ask for an Accessibility Conformance Report, and keep a right to test.
7. Publish a way to report problems. An accessibility statement with a working contact route helps residents now and shows good faith later.
8. Train the people who publish. Most new failures come from new content: an image without alt text, a scanned PDF, a video without captions. A short training for content editors prevents them.

DOJ also published a plain-language starting guide, First Steps Toward Complying with the Title II Web and Mobile Application Accessibility Rule, which is worth sharing with non-technical staff.

If you are the vendor

Get ahead of the procurement question. Audit your product against WCAG 2.1 AA, write an honest conformance report, and fix the issues that block core tasks first. A vendor that shows up with a credible report and a dated roadmap is easier to buy from than one that promises compliance without evidence.

Budgeting the work

Cost depends far more on the number of templates, forms and documents than on page count. A site with 2,000 pages built on six templates can be cheaper to fix than a site with 200 pages built by hand over ten years.

When remediation is not worth it, a rebuild often is. If the platform is old and the templates are inaccessible at the core, a website redesign built to WCAG 2.2 AA can cost less over three years than patching. For a rough range on a new build, try our free website cost calculator, which gives a USD estimate in a couple of minutes.

Next steps

The deadline moved, the standard did not, and the duty to be accessible never paused. The sensible plan is to work toward the 2027 or 2028 date steadily, watch for a DOJ proposal and the outcome of the NFB lawsuit, and build new work to WCAG 2.2 AA so it will not need redoing if the rule is updated.

• Check a key page now with our free automated accessibility checker. It flags common WCAG failures in the page's HTML so you know where to start.
• Read our web accessibility guide for the fundamentals behind WCAG.
• If you sell to EU customers too, see our guide to the European Accessibility Act for US companies.
• When you are ready for an audit or a rebuild, contact us for a fixed-scope quote.

We will update this page when DOJ publishes anything new on this rule or the court rules on the challenge. Not legal advice.