Is the ADA Title II Website Deadline Being Delayed? What Local Governments Need to Know

If you manage a government website, you're probably asking the same question thousands of other city clerks, IT directors, and ADA coordinators are asking right now: Is the April 2026 ADA website compliance deadline still happening?

The short answer: the deadline is still legally in effect. But the situation is more complicated than that — and more importantly, whether the deadline shifts or not probably doesn't change what you should do right now.

Here's everything we know, what it means for your municipality, and what steps you should take today.

What happened: The DOJ submitted a revised rule

On February 13, 2026, the Office of Information and Regulatory Affairs (OIRA) announced that the Department of Justice submitted a revised ADA Title II web accessibility rule as an Interim Final Rule (IFR).

Here's why that matters:

• An IFR can modify regulations without the standard public comment period — this is unusual and unprecedented for an accessibility regulation
• The specific changes in the revised rule have not been made public
• The current April 24, 2026 deadline remains legally in effect until a new rule is actually published
• No IFR has been published yet — what we have is a submission to OIRA for review

This came after a series of signals from the Trump administration throughout 2025:

• March 2025: DOJ withdrew 11 ADA guidance documents
• September 2025: DOJ halted 54 pending regulatory actions
• October 2025: DOJ announced it would re-examine all ADA Title II and III regulations
• February 2026: DOJ submitted the IFR to OIRA

What we don't know

We don't know what the revised rule actually says. The changes could range from:

• A deadline extension (pushing April 2026 to a later date)
• Modified technical requirements (adjusting which parts of WCAG 2.1 AA are required)
• Tailored exemptions for very small jurisdictions
• Complete repeal of the specific WCAG requirement (though legal experts consider this unlikely)

The National League of Cities (NLC) and the League of Minnesota Cities have been organizing to present compliance cost data to OIRA, pushing for adjustments to reduce the burden on smaller municipalities. NLC is actively collecting cost examples from cities across the country.

On the other side, the National Federation of the Blind submitted a formal letter to OIRA on March 5, 2026 opposing any changes. Disability rights attorney Lainey Feingold published an urgent call to action. The situation is politically contested and evolving rapidly.

Why the deadline might be less important than you think

Here's what most analyses of this situation miss: the federal deadline is only one of several reasons your government website needs to be accessible. Even if the DOJ delays or weakens the Title II rule, the following facts don't change:

1. Private lawsuits aren't going away

Over 8,600 ADA-related lawsuits were filed in 2025 alone. Plaintiff attorneys don't need a federal deadline to sue — the underlying ADA obligation to provide accessible digital services has existed since 1990. A delayed deadline might actually increase lawsuits, as attorneys fill the enforcement gap left by reduced DOJ action.

2. State laws are creating their own requirements

Several states have passed or are passing their own web accessibility laws:

• Colorado (HB 21-1110) has required WCAG 2.1 AA compliance for state and local government websites since 2024, with real monetary penalties. According to accessibility attorney David Swank, Colorado has experienced no litigation wave — governments adapted and some are even saving money by pushing vendors to deliver more accessible products.
• California (AB 434) requires state agencies to meet WCAG 2.0 AA standards and post biennial accessibility certifications.
• New Mexico and several other states are advancing similar legislation.

If your state has its own accessibility law, the federal deadline is secondary.

3. Courts favor documented "good faith effort"

This is the most important point for municipalities right now. Whether you face a DOJ investigation, a private lawsuit, or a complaint to your state's civil rights office, the single best protection you have is documented proof that you're actively working on accessibility.

Courts and enforcement agencies consistently treat organizations that can show a compliance roadmap, scan results, and remediation plans more favorably than those that did nothing. This is true regardless of whether you've achieved full compliance.

4. The underlying ADA obligation hasn't changed

The 2024 rule didn't create a new requirement — it codified an existing one. DOJ's Project Civic Access settlements have been requiring WCAG 2.1 AA compliance from state and local governments since at least 2015. Pulling or delaying the rule doesn't eliminate the underlying obligation to provide accessible digital services under Title II.

What your municipality should do right now

Regardless of what happens with the federal deadline, here's a practical action plan:

Step 1: Know where you stand

Run an automated accessibility scan on your website. This takes minutes and gives you a baseline score plus a list of specific issues.

Automated tools can detect about 30–40% of WCAG issues, but they catch the most common and impactful ones: missing image alt text, color contrast failures, missing form labels, and improper heading structure. These are also the easiest issues to fix.

Step 2: Document everything

Start a compliance file now. Include:

• Your scan results (date-stamped)
• A remediation plan with priorities and timeline
• Any accessibility improvements you've made, no matter how small
• Budget requests or allocations for accessibility work
• Staff training records related to accessibility

This documentation IS your "proof of good faith effort." If anyone ever questions your compliance, this file is your first line of defense.

Step 3: Fix the critical issues first

Not all accessibility issues are equal. Focus on these high-impact, low-effort fixes first:

1. Add alt text to images — Every meaningful image needs a text description. Decorative images get alt="". This is the most common violation on government websites, and each one takes about 2 minutes to fix.
2. Fix color contrast — Text needs a minimum 4.5:1 contrast ratio against its background (3:1 for large text). Free tools like the WebAIM Contrast Checker can help you find compliant colors.
3. Label your forms — Every input field (text boxes, dropdowns, checkboxes) needs an associated <label> element. Without this, screen reader users can't tell what information to enter.
4. Add a page language — Your HTML element needs a lang="en" attribute. This takes 30 seconds to fix and affects your entire site.
5. Fix heading order — Use headings (h1, h2, h3) in sequential order. Don't skip from h1 to h3. This helps both screen reader users and search engines understand your content structure.

Step 4: Set up ongoing monitoring

Accessibility isn't a one-time fix. Content changes, pages get added, and new issues appear. You need a system to catch regressions. Tools like GovAccess provide monthly monitoring that automatically rescans your site and alerts you to new issues — so you can fix problems before they become complaints.

The cost question: What does compliance actually look like?

One of the biggest concerns we hear from city clerks and IT managers is cost. Here's a realistic breakdown:

For a typical small city website (50–200 pages):

• Automated scanning tool: $79–$149/month
• Developer time to fix common issues: 20–80 hours total (can often be done by existing staff with guidance)
• Ongoing maintenance: 2–5 hours/month

What you probably don't need (for now):

• A $10,000+ enterprise accessibility platform
• A full manual audit ($3,000–$5,000 per audit)
• An overlay widget (the FTC fined a major overlay provider $1M for making false compliance claims — these don't actually fix your code)

The NLC is also helping cities identify funding sources: ARPA funds, IT modernization grants, DOJ grants, state technology funds, and risk management budgets can all be used for digital accessibility work.

FAQ

Q: If the deadline gets delayed, can I just wait?

We strongly advise against it. The underlying ADA obligation exists regardless of the deadline. Private lawsuits are increasing, not decreasing. And the municipalities that start now will have an easier, less expensive path to compliance than those scrambling at the last minute. Think of it like this: the deadline might move, but the requirement isn't going away.

Q: Does my small town (under 50,000) really need to worry about this?

Yes. The April 2027 deadline applies to municipalities under 50,000. But more importantly, every government website in the United States is subject to ADA Title II, regardless of size. There are no exemptions for small towns. The only difference is the timeline.

Q: We use a CMS vendor (CivicPlus, Granicus, etc.) — aren't they handling this?

Your CMS vendor may provide an accessible template, but you're still responsible for the content you publish. Inaccessible PDFs, images without alt text, improperly structured content — these are all your responsibility even if your vendor's platform is technically compliant. Check with your vendor about their WCAG 2.1 AA status, and make sure your contract includes accessibility requirements.

Q: Will an accessibility overlay widget make us compliant?

No. The FTC has taken action against overlay companies for making false compliance claims. The DOJ and disability advocacy organizations explicitly oppose overlay widgets as a compliance strategy. Overlays don't fix the underlying code — they add a JavaScript layer on top that can actually create new accessibility barriers. Real compliance requires fixing the source code.

Q: What are the penalties for non-compliance?

Federal penalties under the ADA can be up to $75,000 for a first violation and $150,000 for subsequent violations. But the more realistic risk is a DOJ investigation (which results in a consent decree requiring extensive remediation under federal oversight) or a private lawsuit (which results in legal fees, settlement costs, and mandatory remediation). The least expensive path is always proactive compliance.

Bottom line

The regulatory landscape is uncertain, but the obligation to make your government website accessible is not. The best thing you can do right now is:

1. Scan your website to understand your current compliance status
2. Start fixing the most critical issues (it's easier and cheaper than you think)
3. Document your efforts as proof of good faith

Whether the April 2026 deadline holds, gets pushed to 2027, or gets modified in some other way — municipalities that can demonstrate active compliance efforts are in the strongest possible position.

For a complete accessibility audit of your full website with prioritized fix instructions and a proof-of-effort PDF report, start a free 14-day trial of GovAccess — built specifically for local governments at a price that fits your budget.

Disclaimer: This article is for informational purposes only and does not constitute legal advice. Consult with your municipality's legal counsel for guidance specific to your situation.