What Happens the Day After April 24

The Deadline Is Not the End of Something

Sixty days from now, on April 24, 2026, the DOJ's Title II rule takes effect for state and local governments serving populations of 50,000 or more. Every public-facing website, mobile app, and digital service operated by or on behalf of these entities must conform to WCAG 2.1 Level AA.

Most of the conversation around this deadline focuses on getting ready before it arrives. That makes sense — there is still time to remediate, document, and prepare. But almost nobody is talking about what happens on April 25.

The answer matters more than the preparation, because the deadline does not mark the end of an obligation. It marks the beginning of an enforcement regime. And for municipal contractors, the shift from "get ready" to "prove it" changes everything about how you operate, how you bid, and how you protect yourself.

What Actually Changes on April 25

Before April 24, 2026, the Title II digital accessibility obligation technically exists — the ADA has always required state and local governments to provide equal access to services, programs, and activities. But the obligation has been vague. There has been no specific technical standard codified in the regulation. Courts have referenced WCAG as persuasive authority, but municipalities could argue ambiguity. Some did argue it, and some won.

That ambiguity disappears overnight.

On April 25, the DOJ's final rule — published April 2024 and carrying the full force of federal regulation — establishes WCAG 2.1 Level AA as the enforceable standard. This is not guidance, not a best practice recommendation, and not a suggestion. It is codified in 28 CFR Part 35, Subpart H. Every government website, app, and digital service is now measured against a specific, testable set of success criteria.

That single change triggers three cascading effects that reshape the landscape for contractors.

Effect 1: DOJ Enforcement Gets Teeth

The Title II rule does not create new enforcement mechanisms. The DOJ still uses the same tools it has always had: investigations triggered by complaints, compliance reviews, settlement agreements, and federal lawsuits when necessary. But the new rule gives those tools something they have never had in the digital context — a clear, specific, testable standard to enforce against.

Before the rule, a DOJ investigator reviewing a complaint about an inaccessible government website had to make subjective arguments about what "effective communication" and "equal access" meant in digital terms. After April 24, the investigator references WCAG 2.1 Level AA. The success criteria are numbered. The conformance levels are defined. The testing methodology is established.

Here is how the enforcement pipeline works:

A resident with a disability encounters a barrier on a government website — a form they cannot complete, a payment portal that does not work with their screen reader, a PDF they cannot read. They file a complaint with the DOJ's Civil Rights Division, either online or by mail. The Disability Rights Section reviews the complaint. If they determine there may be a pattern of non-compliance or the complaint raises an issue of general public importance, they open an investigation.

The investigation can include document requests, technical reviews, interviews, and site assessments. If the DOJ finds non-compliance, it attempts to negotiate a voluntary settlement agreement — a legally binding document that typically requires full remediation to WCAG 2.1 AA, an ongoing accessibility maintenance plan, staff training, designation of an ADA coordinator, and periodic reporting to the DOJ. If the entity refuses to settle, the DOJ can file a federal lawsuit.

None of this is new. What is new is the specificity. Before the rule, "accessible" was arguable. After the rule, "accessible" means WCAG 2.1 Level AA, and the 50 testable success criteria either pass or they do not.

For contractors, the implication is direct: your deliverables are now tested against a federal standard, not a general principle. When a DOJ investigator reviews a municipality's website, they will trace accessibility failures to their source. If a contractor built or maintains the non-conformant component, the contractor's work product is part of the evidentiary record — even though the DOJ names the municipality as the responsible entity.

Effect 2: Plaintiff Firms Open a New Market

This is where the calculus shifts dramatically. The DOJ processes complaints at federal government speed — investigations take months or years. But private litigation operates on a different timeline entirely.

Until now, ADA accessibility lawsuits have overwhelmingly targeted private businesses under Title III. The 2025 lawsuit data shows over 4,900 federal filings, almost entirely against commercial websites. Government entities have been a relatively small portion — only 142 municipalities sued since 2011.

That ratio is about to change, and plaintiff firms are already signaling the shift.

The Title II rule removes the ambiguity that has insulated government entities. Before the rule, a plaintiff suing a municipality over its website had to argue that the ADA's general requirements applied to digital services — an argument that some courts accepted and others rejected. After April 24, WCAG 2.1 AA is the explicit standard. A plaintiff only needs to demonstrate that the website fails to meet that standard, which any automated scanning tool can establish in minutes.

The same law firms that built infrastructure to file hundreds of cases per year against private businesses now have a new category of targets with three characteristics that make them especially attractive:

Government entities are public accommodations by definition. There is no nexus argument, no question about whether the ADA applies. Title II covers them categorically.

Government entities have constrained legal budgets. Unlike major corporations that can litigate aggressively, municipalities often find it cheaper to settle — which is exactly what serial plaintiff operations are optimized for.

Government entities face political pressure. An ADA lawsuit against a city makes local news. Elected officials want it resolved quickly. That urgency drives faster settlements at higher amounts than a private business might agree to.

For contractors, the threat is indirect but real. When a municipality gets sued over accessibility failures in a system you built or maintain, the first thing their attorney does is review vendor contracts. If your contract includes accessibility warranties or indemnification clauses — and increasingly, RFPs require both — the municipality's legal problem becomes your legal problem.

Effect 3: The Vendor Liability Chain Activates

The DOJ's final rule makes one thing unambiguous: public entities cannot outsource their compliance obligation. If a municipality contracts with a vendor to build a payment portal, and that portal is not accessible, the municipality is responsible. The DOJ does not care who wrote the code.

This has always been true in principle. But with a clear enforceable standard and active enforcement, municipalities are now incentivized to push compliance responsibility downstream — to you.

Expect to see three things happening in government contracts starting the day after the deadline:

Accessibility audits as acceptance criteria. Municipalities will require WCAG 2.1 AA conformance testing before accepting deliverables. If your work does not pass, it does not ship.

Indemnification clauses with teeth. Contract language requiring contractors to hold the municipality harmless for accessibility-related complaints, lawsuits, settlements, and remediation costs — specifically tied to the contractor's deliverables.

Ongoing compliance obligations. Not just at delivery, but for the life of the contract. Monthly or quarterly accessibility scans, documented remediation cycles, and proof that the deliverable remains conformant as content changes.

If you are not already building these into your delivery process, you will be forced to after April 24. The contractors who anticipated this shift will win bids over those who are scrambling to catch up.

What "Compliance" Actually Looks Like on Day 1

Here is the uncomfortable truth: on April 25, 2026, almost no government website in America will be fully WCAG 2.1 AA conformant. The standard includes 50 testable success criteria across four principles. Full conformance means every criterion passes on every page, every form, every document, every interactive component. For large municipal sites with years of accumulated content, legacy systems, and third-party integrations, 100% conformance on Day 1 is a fantasy.

The DOJ knows this. Their enforcement posture has consistently recognized the difference between an entity that has made no effort and an entity that has a documented, good-faith compliance program in progress.

On Day 1, defensible compliance looks like this:

A documented baseline. You ran a comprehensive scan before the deadline. You know where you stand. The scan results are timestamped and preserved — not as evidence of failure, but as the starting point of a remediation program.

A prioritized remediation plan. You identified the highest-risk violations — the six categories that appear in 96% of automated scan findings — and you addressed them first. Critical barriers that prevent access to essential services (forms, payments, applications) were remediated before cosmetic issues.

An active audit defense log. Every fix is documented with a date, description, responsible party, and verification. Every scan is recorded. Every decision is traceable. This is the artifact that distinguishes a good-faith compliance effort from negligence.

An ongoing monitoring plan. You are not treating the deadline as a one-time event. Scans run on a regular schedule — monthly for active sites, quarterly for stable ones. New content is checked before publication. The log continues to grow.

An accessibility statement. Published on the site, it describes the standard you are working toward (WCAG 2.1 AA), the steps you have taken, the known limitations, and how users can report barriers or request assistance.

This is not perfection. It is demonstrable effort, documented consistently, maintained over time. And in the enforcement landscape that begins on April 25, demonstrable effort is the difference between a complaint that gets resolved with a phone call and a complaint that becomes a federal investigation.

The Contractor's Position After the Deadline

If you are a municipal contractor delivering digital projects, April 25 changes your competitive landscape in three specific ways.

The contractors who documented their compliance process will win renewals. When a municipality reviews its vendor relationships under the new enforcement pressure, the vendors who can show audit defense logs, scan histories, and remediation records will be retained. The vendors who cannot will be replaced.

New RFPs will require accessibility evidence at bid. Not just a checkbox claiming WCAG awareness, but actual documentation — past scan results, remediation timelines, VPAT conformance reports, and accessibility methodology descriptions. The documentation packages that win bids are no longer optional differentiators. They are table stakes.

Accessibility failures become contract disputes. Before the deadline, a municipality might have tolerated an inaccessible deliverable because the standard was unclear. After the deadline, non-conformance is a measurable failure against a federal requirement. Expect disputes, cure notices, and contract terminations where accessibility failures were once overlooked.

Sixty Days to Get Ahead

The contractors who will be strongest on April 25 are not the ones with perfect WCAG scores. They are the ones with documented processes, defensible records, and the infrastructure to maintain compliance over time.

You have sixty days. Use them to run baseline scans, fix the critical barriers, build the audit defense log, and establish the monitoring cadence. When the enforcement regime activates, you will not be scrambling to prove what you have done — you will have the documentation already in hand.

The deadline is not the end of the compliance conversation. It is the first day of a new one. Be ready for it.

---

This post is for informational purposes only and does not constitute legal advice. Consult with qualified legal counsel for guidance specific to your situation.