Tools Without Trust: Why Legal Architecture Can't Fix Definitional Power

David's structural analysis in The Harm Definition Problem Has a Structural Solution is technically precise. Pattern-or-practice authority exists. Section 504 compliance review powers are real. The DOJ's Civil Rights Division can, in theory, initiate investigations without waiting for complaint accumulation. All of this is accurate.

But there's a prior question the structural argument doesn't fully address: what happens when communities have spent decades watching those same legal tools deployed selectively, inconsistently, or in ways that treated their expertise as supplementary rather than foundational? The tools don't exist in a vacuum. They exist inside institutions that have their own definitional cultures — and those cultures are precisely what Keisha's original complaint-volume analysis was interrogating. The structural solution assumes the structure can be trusted. That assumption requires examination.

The Institutional Culture Behind Civil Rights Enforcement

Federal civil rights enforcement agencies do hold significant proactive authority. The Department of Justice's Civil Rights Division (opens in new window) has exercised pattern-or-practice powers in meaningful ways across disability rights contexts. But the exercise of that authority has historically been episodic, administration-dependent, and shaped by internal agency cultures that were themselves built without systematic community input.

The ADA National Network (opens in new window), which operates regional ADA Centers across the country, has documented this dynamic extensively in their technical assistance work. Practitioners who work directly with disability communities consistently report a gap between what federal enforcement authority permits and what affected communities actually experience as responsive enforcement. That gap isn't primarily a resource problem or a legal authority problem. It's a definitional problem — agencies determine what harm looks like before communities get a meaningful seat at the table.

Section 508 of the Rehabilitation Act (opens in new window), which governs federal agency technology accessibility, illustrates this clearly. The statute exists. GSA's governmentwide guidance exists. Compliance review authority exists. And yet, as research from the National Federation of the Blind (opens in new window) and other disability-led organizations has consistently shown, federal agencies routinely procure inaccessible technology with limited accountability — not because the tools to prevent this are absent, but because the definitional framework for what counts as adequate accessibility was constructed through procurement processes that treated disabled users as edge cases rather than primary stakeholders.

Community Input as Infrastructure, Not Consultation

The distinction worth drawing here — and it matters practically — is between community input as a procedural step and community input as foundational infrastructure. David's structural argument, as explored in the original piece, implicitly treats the legal tools as neutral mechanisms waiting to be better deployed. But legal tools encode the assumptions of the people who built them.

The Web Content Accessibility Guidelines (opens in new window) process at W3C offers a useful parallel. WCAG is frequently cited as a technical standard. What's less frequently discussed is how working group composition shapes which accessibility barriers get codified as violations and which get characterized as edge cases or future considerations. Disability-led organizations have raised concerns for years about the degree to which the standard reflects the priorities of technologists over the lived experience of users with disabilities. The standard exists. The authority to enforce it exists. The definitional culture that produced it remains largely intact.

This is the CORS framework's community dimension applied rigorously: operational and strategic considerations can't be separated from whose knowledge counts as evidence when harm is being defined. At accessibility.chat, we treat community expertise as primary data, not supplementary context. That distinction is methodological, but it has structural implications.

What Redistributing Definitional Power Actually Requires

If the legal architecture genuinely contains mechanisms to redistribute definitional power — and I agree with David that it does — then activating those mechanisms requires something the structural argument underweights: sustained institutional relationships with disability communities that predate enforcement action.

The Great Lakes ADA Center (opens in new window) and the Pacific ADA Center (opens in new window) both conduct community-based technical assistance that could, in principle, feed directly into federal enforcement priority-setting. The Southwest ADA Center (opens in new window) maintains regional expertise that federal agencies rarely systematically consult before initiating compliance reviews. These relationships exist. They are not structurally integrated into enforcement pipelines in ways that give communities upstream influence over what gets investigated and why.

The DOJ's ADA.gov guidance framework (opens in new window) is comprehensive. It does not contain a mechanism for community-defined harm to trigger pattern-or-practice review. Individual complaints can accumulate into patterns that agencies recognize — but the recognition still happens inside the agency. The definitional authority hasn't moved.

Building on the structural framework David outlined, the practical path forward isn't just better deployment of existing tools — it's redesigning the intake and priority-setting processes that precede tool deployment. That means formal community advisory structures with actual agenda-setting authority, not post-hoc comment periods. It means disability-led organizations having standing to initiate compliance reviews, not just inform them. It means treating the ADA Centers' regional expertise as enforcement infrastructure rather than educational supplementary programming.

The Trust Deficit Has Evidentiary Consequences

There's a practical reason this matters beyond the principled argument about power. When communities don't trust that enforcement institutions will recognize their definition of harm, they don't engage with those institutions — which produces exactly the complaint-volume problem Keisha's earlier analysis identified. Low complaint volume gets read as low harm incidence. Low harm incidence reduces enforcement priority. Reduced enforcement priority confirms community skepticism about institutional responsiveness. The cycle is self-reinforcing, and it operates entirely within the existing legal architecture.

The structural tools David identifies are real. Deploying them effectively requires addressing the trust deficit that makes communities reluctant to engage with them. That's not a soft consideration. It's an evidentiary problem with direct consequences for what enforcement agencies can see, measure, and act on.

Legal architecture without institutional trust isn't a solution waiting to be activated. It's infrastructure that communities have learned to route around. The concrete implication for enforcement reformers: before redesigning legal tools, map the relationships — or their absence — between federal agencies and the disability-led organizations that hold regional expertise. Where those relationships don't exist, building them is the prerequisite, not the follow-on.