18 Governors vs. DOJ: The Olmstead Battle That Redefines 'Accessible'

The word "integration" appears four times in the governors' letter to Attorney General Todd Blanche. The word "segregation" appears three times. The word "home" appears once—but it carries the weight of the entire argument.

That single word is doing a lot of work right now.

What Actually Happened—and Why the Distinction Matters

In June, the Justice Department's Office of Legal Counsel issued a memo questioning long-held interpretations of Olmstead v. L.C. (opens in new window), the 1999 Supreme Court decision that established the right of people with disabilities to receive services in the most integrated setting appropriate to their needs. The memo did not change the law. The ADA is still the ADA. Olmstead is still binding precedent.

But enforcement posture is not the same as statutory text—and the disability rights community knows it. Jennifer Mathis, now deputy director at the Bazelon Center for Mental Health Law (opens in new window) and formerly deputy assistant attorney general for the DOJ's Civil Rights Division, stated: "The DOJ Olmstead memo is not the law, and we are asking states to keep it that way by committing not to engage in these types of attacks themselves."

That sentence matters. The advocates aren't arguing that the law changed. They're arguing that the interpretation of the law—and the federal posture toward enforcing it—creates conditions under which states might feel emboldened to roll back community-based services. The law as written and the law as enforced are two different things. The gap between them is where disabled people's actual lives are decided.

The Coalition and What It Signals

New York Governor Kathy Hochul organized the response letter, which drew signatures from governors in 18 states: Arizona, Connecticut, Delaware, Illinois, Maine, Maryland, Massachusetts, Michigan, Minnesota, New Jersey, New Mexico, North Carolina, Oregon, Pennsylvania, Rhode Island, Washington, and Wisconsin.

The governors' framing is deliberate: "This is not a partisan issue." They cite the ADA's signing by President George H.W. Bush and note that progress on community integration has happened under both parties. This is political insulation—it removes the easy dismissal that this is partisan opposition—and it signals that the coalition is building durable, cross-aisle support for Olmstead's core principle.

The principle itself is straightforward. As the governors wrote: "Community integration is not an abstract legal concept. It means having a home, being able to work, attend school, shop, worship, build relationships, and participate in an ordinary civic life."

That's not legal language. That's a description of what it means to be a person.

The Enforcement Gap as an Accessibility Problem

For organizations working on Title II compliance—state and local governments, public universities, transit systems—this situation illustrates something that often gets obscured in technical compliance work: the difference between having a policy and having infrastructure that makes the policy real.

Olmstead compliance isn't primarily a digital accessibility question. But the pattern it exposes maps directly onto dynamics that accessibility professionals see constantly. A state can have an Olmstead plan on paper—and many do, because federal guidance has required them—while simultaneously underfunding the home and community-based services (HCBS) waiver programs that make those plans operational. The document exists. The access doesn't.

This is structurally identical to the compliance failures documented in The Settlement Trap: How Legal Victories Create Accessibility Compliance Failures, which examines how legal agreements that appear to resolve discrimination often create deeper organizational failures downstream. Winning the legal argument doesn't automatically build the capacity to deliver on it.

Language Access: The Compliance Layer Nobody's Auditing Together

The people most affected by rollbacks in community-based services are disproportionately people who also face language barriers.

The intersection of disability access law and language access law (opens in new window)—ADA/Section 504 on one axis, Title VI of the Civil Rights Act on the other—is enforced by overlapping agencies but almost never audited together. A state Medicaid agency can pass a WCAG AA audit of its HCBS waiver portal while that same portal is functionally inaccessible to a Spanish-speaking family navigating it for a family member with an intellectual disability. The screen reader works. The language doesn't.

This isn't a hypothetical edge case. It's a structural gap. Organizations that invest heavily in WCAG compliance (opens in new window) often have zero language access infrastructure—and vice versa. The compliance teams operate in silos, each checking their own box, neither one responsible for the person who needs both.

Tools like idioma.chat (opens in new window) represent what closing that gap actually looks like in practice. Unlike traditional translation services that handle static page text, idioma.chat translates the full accessibility layer—ARIA labels, alt text, form validation messages, dynamically loaded content, and modal dialogs—so that a screen reader user who reads Spanish encounters a coherent, navigable experience, not a bilingual patchwork. A government HCBS portal that passes WCAG AA but only works in English is not fully accessible to the communities it serves. That's not a philosophical point. It's a compliance gap that Title VI and the ADA both speak to, and that enforcement agencies are increasingly paying attention to.

What the Broader Pattern Raises

When the federal enforcement posture on a foundational civil rights precedent shifts—even without changing the underlying law—what does that mean for the organizations that have built their compliance frameworks around that precedent?

State Olmstead plans were developed in response to federal guidance and DOJ enforcement pressure. If that pressure recedes, the plans don't disappear. But the political will to fund and implement them can. And the communities most dependent on those services—people with developmental disabilities, people with serious mental illness, elderly people who would otherwise be institutionalized—have the least capacity to absorb the gap.

The governors' letter is, in part, an attempt to fill that gap with state-level commitment. Whether 18 signatures translate into 18 states maintaining robust HCBS funding and Olmstead enforcement infrastructure is a different question. As The Compliance Framework Paradox documents, the distance between stated commitment and operational capacity is where most compliance failures actually live.

What Practitioners Should Watch

For accessibility professionals working with state and local government clients, the Olmstead situation is a signal, not just a news story. Here's what to track:

Indicator	What to Watch	Primary Authority
State Olmstead plans	Are they being updated or quietly shelved?	28 CFR Part 35 (opens in new window)
HCBS waiver portals	WCAG AA + language access together	WCAG 2.1 SC 3.1.1 (opens in new window)
Grievance procedures	Are disability rights complaints being tracked?	ADA Title II, §35.107 (opens in new window)
DOJ enforcement actions	Which cases are being dropped or modified?	DOJ Civil Rights Division (opens in new window)
State AG posture	Are state AGs filling the federal enforcement gap?	State civil rights statutes

The law hasn't changed. But the conditions under which the law operates have. Erica Bonn carrying her favorite painting into her home at Quest Village in Orlando isn't an anecdote. It's the outcome that 25 years of Olmstead enforcement was designed to produce. The question now is which organizations—federal, state, and local—are willing to treat that outcome as non-negotiable.

The governors' letter says 18 of them are. The work of holding that commitment operational falls to the people who build and maintain the systems those commitments depend on.