Who Actually Enforces This?
What the Public Record Shows
ACCESS BRIEF INSIGHTS — September 21, 2026
In conversations with consulting firms and public agencies, one question comes up more often than almost any other: who actually enforces this? It is a fair question, and it usually reflects a sound instinct. A requirement on paper does not change behavior. Enforcement does. So it is worth answering it directly, using the published enforcement record.
​
A common assumption in these conversations is a federal penalty schedule: miss the deadline, receive a fine. That is not how Title II of the Americans with Disabilities Act operates. The actual answer is more useful, because it identifies where enforcement pressure originates, what it produces, and which obligations apply now, before any 2027 date arrives.
Who Actually Enforces This - Two Channels, Both Older Than the Rule
Title II is enforced through two channels, and both existed long before the Department of Justice published its web accessibility rule in April 2024.
​
First, the Department of Justice can investigate complaints, negotiate settlement agreements, and bring enforcement litigation under its Title II authority (42 U.S.C. § 12133). Second, private individuals can file lawsuits alleging discrimination under Title II. No federal agency has to act first. A person who encounters an inaccessible government website or document can file a complaint or a lawsuit on their own.
​
The 2024 rule did not create a new basis for lawsuits (what lawyers call a cause of action), and the 2026 Interim Final Rule that extended the compliance deadlines did not create one either. What the rule added is a specific, measurable technical standard: Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Before the rule, there was no single technical standard that a court or investigator was required to apply to digital content. After the applicable compliance date, that standard is written into regulation. The rule made an existing obligation testable. It did not create the obligation.
What DOJ Enforcement Produces
The enforcement matters the Department publishes on ADA.gov take a recognizable form: settlement agreements and consent decrees (court-approved settlements). These are negotiated outcomes that require the covered entity to remediate content, adopt policies, train staff, and report on progress, often against defined timelines.
​
One published example involves digital content directly. In January 2024, the Department of Justice reached a settlement agreement with Service Oklahoma after finding that the state agency's mobile identification app was not accessible to people with vision disabilities. Under the agreement, the agency is required to ensure that mobile apps it creates or maintains conform to WCAG 2.1 Level AA.
​
That outcome is worth examining. It is not a one-time payment that closes the matter. It is a structured remediation obligation with a conformance standard attached. An entity in that position does the accessibility work anyway. It just does the work on the government's schedule instead of its own.
What the Rest of the Public Record Shows
Department of Justice matters are only part of the picture. Three developments in the Title II record are worth knowing, because together they show complaint activity that is organized rather than incidental.
​
Complaints now arrive in large numbers. In Michigan, an advocacy organization filed web accessibility complaints with the U.S. Department of Education's Office for Civil Rights concerning school and district websites. The filings have been reported at more than 2,400 complaints, with more than 1,000 resulting in resolution agreements, the Office for Civil Rights' equivalent of a settlement. The precise count matters less than the model: an organization identified a category of inaccessible public content and filed systematically, not one grievance at a time. The mechanism is not unique to Michigan or to education. Comparable complaint channels exist for other public sectors.
​
At least one court has declined to treat the deadline as a shield. In a case filed in 2024, a Louisiana resident sued state agencies over websites he could not use with his screen reader. The state asked the court to dismiss, arguing in part that the rule's compliance deadline had not yet arrived. The court declined to dismiss, and the case proceeded (Ellerbee v. State of Louisiana). One district court ruling does not settle the question nationally. It is, however, a documented instance of a court allowing a Title II digital accessibility claim to go forward before any compliance date, which is consistent with an obligation that predates the rule.
​
The extension itself is being challenged. In May 2026, the National Federation of the Blind filed suit challenging the Interim Final Rule that delayed the compliance dates, asking the court to set the extension aside. The outcome is pending, and planning should assume the current dates hold. But the filing tells you something about the environment: the extension is not being received as a quiet pause. The community most affected by inaccessible content is contesting the delay in federal court.
What Applies Right Now, Before Any Deadline
For agencies holding public meetings and posting project documents this year, the practical question is not what happens in April 2027. It is what applies today. The obligations that matter most here are already in effect, and none of them depends on the 2024 rule.
​
Title II has required public entities to communicate as effectively with people with disabilities as with everyone else since the ADA's enactment in 1990; the implementing regulation (28 CFR 35.160) makes that obligation explicit. When the Department of Justice extended the compliance dates, it stated that existing ADA obligations continue to apply during the extension. A meeting packet or study report that a screen reader cannot read is not sitting in a compliance-free zone. It is sitting in a pre-benchmark zone, where the duty exists but the technical benchmark is not yet mandatory.
​
For transportation agencies, there is a second layer. Section 504 of the Rehabilitation Act has prohibited disability discrimination in federally funded programs since 1973, and federal regulation requires early and continuing opportunities for public involvement on federal-aid projects (23 CFR 771.111(h)). For public involvement content on federal-aid projects, the accessibility obligation never depended on the 2024 rule. Federal funding carried it decades earlier.
​
Then there is the operational exposure, which rarely appears on a compliance report. Public involvement materials do a specific job: they support a legally required participation process. If some residents could not access the materials that supported a comment period, the adequacy of that participation process is open to question. The remedies such a challenge could seek are operational: an extended or repeated comment period, additional outreach, and schedule delay on the project the meeting was supporting. That is a risk, not a prediction. But it is the kind of risk that lands on active projects, not future ones.
What This Means for Consulting Firms
If you lead a firm that produces deliverables for public agencies, there is a version of the enforcement question that matters more than the general one: how does any of this reach us?
​
Start with what gets tested. When complaints arrive in large numbers, what they examine is the content posted on agency websites: public involvement plans, environmental documents, study reports, meeting materials. Public agencies routinely contract the production of this content to consulting firms. When that content is examined, the firm's deliverable is examined with it, under the agency's name.
​
The rule then closes the loop. It treats the compliance obligation as one that cannot be delegated. A public entity remains responsible for content produced on its behalf by contractors and vendors, and it cannot shift that responsibility through contract terms. The preamble to the 2024 final rule (the Department's published explanation of the rule) is explicit on this point (89 Fed. Reg. 31367).
​
That structure has a predictable consequence. Enforcement pressure on agencies converts into procurement pressure on the firms that serve them. It arrives as accessibility requirements in solicitations, conformance criteria in deliverable acceptance, and contract language that assigns remediation costs to the producing firm. A consulting firm will not receive the Department of Justice letter. It will receive the returned deliverable and the stricter contract clause, and where accessibility capability enters evaluation criteria, it will shape competitive position. For firms, that is the form enforcement takes.
Posture Changes Outcomes
There is one more feature of this landscape worth understanding, because it is the part an entity can control right now.
The compliance date extensions give agencies time to phase their work before the standard applies.
​
An entity that can produce a current inventory of its digital content, a dated remediation plan, and evidence of progress against that plan is in a much stronger position than an entity that can produce none of those things. Documentation is not a substitute for compliance. But it is evidence of good-faith effort, and it gives the entity something concrete to show when a complaint is evaluated or a settlement is negotiated.
​
The practical instruction follows directly. Inventory what you publish. Document the plan. Make demonstrable progress against a schedule. The entities that treat their compliance date as a working endpoint will arrive at it in a far stronger position than the entities that treat it as a buffer.
Enforcement Moves People. It Should Not Be the Only Thing That Does.
The instinct behind the original question is correct. Enforcement is what gets many organizations to move. But enforcement-driven work has a known shape: fix what the complaint names, then stop. Organizations that build accessibility into how content is produced avoid the retrofit costs that enforcement-driven remediation carries, and they are better positioned to sustain conformance once the immediate pressure passes. That is a longer conversation, and it is one worth having before the pressure arrives rather than after.
​
If your agency or firm wants to assess where it stands, the ADA Title II Readiness Checklist is freely available at aogaccess.com. The full regulatory picture, including how enforcement works and what the compliance dates do and do not change, is in Real. Relevant. Required., available now on Amazon.