Community Expertise Is Real. Liability Exposure Is Realer.

Keisha's analysis in The Capacity Argument Has a Blind Spot makes a genuinely important point: disabled people and LEP community members hold detailed, actionable knowledge about where systems fail. That knowledge is systematically underutilized. The argument is correct as far as it goes.

But there's a dimension the community expertise framing doesn't fully address, and organizations ignoring it are accumulating legal risk in real time. The question isn't only whether community members should be architects of better systems — they should. The question is what happens legally when an organization knows its feedback mechanisms are inaccessible and continues operating them anyway.

That's not a theoretical concern. It's the operational reality that Title II covered entities, federally assisted programs, and Section 504 recipients face every day they leave documented accessibility gaps unresolved.

Constructive Knowledge: What It Means When You've Been Told

Under the Americans with Disabilities Act (opens in new window), covered entities don't need a formal complaint to be on notice. Constructive knowledge — the legal standard that organizations knew or should have known about a barrier — can attach through a variety of channels: community advocacy letters, informal staff reports, prior grievances that were resolved without systemic fix, or even publicly documented accessibility audits that were never acted upon.

The Department of Justice's enforcement guidance (opens in new window) on Title II makes clear that entities with notice of inaccessible feedback mechanisms face heightened scrutiny when complaints eventually surface. And they do surface. The average lag between an accessibility failure and a formal complaint or investigation is not infinite. It's a window — and organizations that use that window to document community expertise without acting on it have, paradoxically, made their legal position worse.

This is the risk dimension that the community expertise conversation tends to bracket. Participatory design processes, community listening sessions, and co-design frameworks are valuable. They're also, from a liability standpoint, documentation that an organization was told about a problem.

Title VI and Language Access: The Enforcement Pattern

The language access side of this equation has a clearer enforcement track record than many accessibility practitioners realize. Under Title VI of the Civil Rights Act (opens in new window) and the Executive Order 13166 framework (opens in new window), federally assisted entities are required to provide meaningful access to LEP individuals. The Department of Justice's LEP guidance (opens in new window) is explicit: a feedback or grievance mechanism that is only available in English is not a neutral administrative choice. It is a potential Title VI violation.

DOJ and HHS have both pursued resolution agreements with covered entities where inaccessible complaint mechanisms were central findings — not peripheral ones. The pattern matters because it reframes the community expertise argument. It's not just that Spanish-speaking parents have mapped informal channels around inaccessible systems, as Keisha documents. It's that those informal channels constitute evidence that the official mechanisms failed, and that failure has a legal name.

Organizations that engage community expertise processes and surface this evidence without corrective action timelines are, in effect, building the plaintiff's case.

The Grievance Mechanism Gap Is Specifically Regulated

This point deserves more attention than it typically receives in accessibility coverage. The ADA's Title II regulations at 28 CFR Part 35 (opens in new window) require public entities with 50 or more employees to designate an ADA coordinator, adopt grievance procedures, and make those procedures accessible. Section 504 of the Rehabilitation Act carries parallel requirements for federal grantees.

The Pacific ADA Center (opens in new window) and other regional ADA Centers have documented that grievance procedure compliance is one of the most commonly cited deficiencies in self-evaluation reviews. The mechanism itself — not just the substantive accessibility of programs — is a regulated artifact. An inaccessible grievance form isn't an operational inconvenience. It's a compliance failure with its own regulatory basis.

This matters for how we read the capacity argument and the community expertise counterargument. Both Marcus and Keisha are analyzing the feedback gap as primarily an information and capacity problem. The regulatory frame adds a third dimension: it's also a discrete legal obligation with its own compliance clock. Organizations don't get credit for good intentions about community co-design if their grievance procedures are out of spec.

Legal Exposure Doesn't Wait for Participatory Design Timelines

Co-design and participatory accessibility frameworks operate on timelines that legal exposure doesn't respect. A well-run community engagement process might take 12 to 18 months to move from listening sessions to implemented changes. A DOJ complaint investigation (opens in new window) can open in weeks. A private lawsuit under Title III or Section 504 can be filed the day a plaintiff's attorney documents the barrier.

This isn't an argument against participatory design — the approach we use at this publication takes community expertise seriously as both a journalistic and analytical framework. It's an argument for running legal risk assessment in parallel with community engagement, not sequentially.

Organizations that treat community expertise processes as a substitute for interim remediation are misreading their exposure. The legally defensible posture is to implement available fixes immediately — accessible complaint forms, translated grievance procedures, alternative submission channels — while longer-term co-design work proceeds. Doing it in the other order creates documented notice without documented action.

What the Legal Frame Adds to This Conversation

Building on the community expertise framework Keisha develops, the risk lens adds a practical urgency that the expertise argument alone doesn't generate. Disabled community members and LEP populations deserve to be architects of accessible systems — that's correct on its merits. They're also, in the current enforcement environment, the most likely source of the complaints and investigations that will force organizational change when co-design processes stall or lose institutional support.

The Section 508 compliance framework (opens in new window) for federal agencies and the ADA's Title II structure for state and local entities both assume that feedback mechanisms are functional. When they're not, the legal system provides a correction mechanism that operates independently of organizational goodwill. Understanding that mechanism — and the liability it creates — is not a reason to deprioritize community expertise. It's a reason to move faster on implementing what community expertise reveals.

Organizations that grasp both dimensions — the knowledge that lives in affected communities and the legal exposure that accumulates when that knowledge goes unacted upon — are better positioned than those treating this as a choice between compliance and co-design. It was never a choice. The regulations don't offer that option.

The practical decision point is straightforward: if your organization has run a listening session, received an advocacy letter, or completed an audit in the last 24 months and has not implemented interim remediation on the documented gaps, you have constructive notice and no corrective action record. That's the posture to fix first, before the next co-design cycle begins.