Co-Design Is Necessary But Not Sufficient for Language Access

Community co-design is a genuine improvement over top-down language access programs. Keisha's analysis in the original piece makes a compelling case that organizations consistently build language access infrastructure on assumptions rather than evidence gathered from the communities they serve. That argument is well-supported and practitioners should take it seriously.

But there's a tension worth examining directly: elevating community voice as the primary missing infrastructure can inadvertently shift accountability away from the institutional and legal obligations that protect LEP communities when participation processes fail, stall, or get defunded. The question isn't whether co-design matters — it does — but whether framing it as the root cause of language access failures adequately captures the structural problem.

What Title VI Actually Requires

The Department of Justice's Title VI guidance (opens in new window) establishes affirmative obligations for recipients of federal financial assistance. Organizations must provide meaningful access to LEP individuals — and that obligation doesn't hinge on whether a co-design process was completed. The four-factor analysis DOJ uses to assess compliance (number of LEP persons, frequency of contact, importance of the program, and available resources) is an organizational accountability framework, not a community participation framework.

This distinction matters practically. When a hospital system fails to provide a qualified interpreter for an emergency department visit, the legal remedy flows from Title VI and Section 1557 of the Affordable Care Act — not from whether the hospital consulted community members during program design. The ADA National Network (opens in new window) and regional ADA Centers consistently document that enforcement pathways are institution-facing, not participation-facing.

Co-design can improve program quality substantially. But it doesn't substitute for the compliance infrastructure that creates enforceable rights. Treating participation as the missing piece can obscure the extent to which organizations are simply not meeting existing legal baselines — a problem that community consultation alone won't fix.

The Participation Burden Problem

There's a second concern that Keisha's framework, as presented, doesn't fully address: who bears the cost of co-design processes?

Meaningful community participation requires time, translation, childcare, transportation, and compensation for participants' expertise. When organizations treat community input as a design resource without resourcing the participation itself, they transfer the burden of improving institutional programs onto the communities those programs are supposed to serve. Research from the National Council on Interpreting in Health Care (opens in new window) has documented that community members — particularly those with limited English proficiency — are frequently asked to contribute unpaid labor to improve systems that have failed them.

This isn't an argument against co-design. It's an argument that co-design done poorly can replicate the extractive dynamic it's meant to correct. The Pacific ADA Center (opens in new window) and other regional technical assistance providers have noted that participation processes without adequate support infrastructure often end up representing the most resourced and connected members of a community rather than those with the deepest service needs.

As explored in the original analysis, organizations make infrastructure decisions that look sound from the inside and fail in practice. That's true. But the solution isn't participation as an abstract principle — it's participation with genuine institutional investment in making that participation substantive and representative.

The Operational Reality

From a balanced analytical perspective, the three-way debate between compliance, strategy, and community voice reflects a real fragmentation in how language access gets theorized versus how it gets implemented. Practitioners working in government benefits administration, healthcare, or emergency management aren't typically choosing between these frames — they're navigating all three simultaneously with inadequate resources for any of them.

The Section 508 compliance framework (opens in new window) offers a useful analogy. Digital accessibility requirements created a legal floor that forced organizational investment — but technical compliance without usability testing with disabled users consistently produces accessible-in-theory, inaccessible-in-practice outcomes. The solution the field arrived at wasn't to abandon compliance in favor of co-design, but to require both: legal obligation as the non-negotiable floor, user involvement as the quality mechanism above it.

Language access could benefit from the same architecture. WCAG's approach (opens in new window) to web accessibility — testable success criteria combined with understanding documents that incorporate user research — models how compliance standards and community input can be structurally integrated rather than positioned as competing priorities.

Where the Argument Lands

The case for community co-design in language access is strong. The AHRQ research Keisha cites on health literacy is real, and the pattern of technically accurate translations that fail communicatively is well-documented across sectors. Organizations that exclude LEP communities from program design are making a consequential error.

But framing community voice as the primary missing infrastructure carries risks worth naming. It can create pressure on communities to solve problems that institutions are legally obligated to address. It can make participation a substitute for compliance rather than a complement to it. And it can obscure the extent to which many language access failures are straightforward non-compliance issues that enforcement — not co-design — is positioned to remedy.

Building on this framework, the more complete picture is an integrated one: compliance obligations that create enforceable rights and institutional accountability, operational infrastructure that can actually deliver on those obligations, and community co-design processes that are adequately resourced and structurally embedded — not treated as a substitute for the first two. Each element addresses failures the others can't. Practitioners who want to move forward have a concrete starting point: audit which of the three is actually missing in their context before deciding which to prioritize. The field needs all three working in concert, not a debate about which one is most fundamental.