Language Access Infrastructure Starts With Community, Not Contracts

Marcus makes a compelling case for operational infrastructure in language access. But infrastructure built without the communities it serves tends to replicate the same exclusions it claims to fix. The procurement gap he identifies is real. The maintenance problem is real. What's missing from the operational framing, though, is the question of who gets to define what "functional equivalence" actually means in practice.

In his recent analysis, Marcus correctly identifies that a translated page describing a defunct program isn't meaningful access. What he doesn't fully address is why that failure keeps happening — and the answer isn't purely operational. It's relational. Organizations contract with translation vendors, push content live, and consider the obligation discharged. The communities those translations are supposed to serve were never in the room.

What "Meaningful Access" Actually Requires

The Department of Justice's LEP guidance (opens in new window) uses the phrase "meaningful access" repeatedly, but the legal standard is interpreted almost entirely by the organizations obligated to provide it. That's a structural problem. When a county health department decides its Spanish-language FAQ constitutes meaningful access to a complex benefits enrollment process, it's making that determination based on internal capacity assessments — not on whether Spanish-speaking residents can actually navigate the system.

Research on limited English proficiency and healthcare navigation (opens in new window) consistently shows that machine translation and even professional translation frequently miss community-specific terminology, regional dialect variation, and the cultural framing that makes information actionable. A document can be grammatically correct and linguistically accurate while still being functionally useless to the people it's meant to serve.

The LEP.gov four-factor framework (opens in new window) that Marcus references is a useful compliance scaffold. But factor four — resources available — has historically been used to justify inadequate service rather than to prompt creative problem-solving. Community organizations serving LEP populations have been saying this for decades. The framework gives agencies an exit ramp.

The Difference Between Translation and Communication

This is where the CORS framework we use at this publication becomes analytically useful. Marcus's operational lens captures the Risk and Strategic dimensions well: maintenance failures create legal exposure, and treating language access as infrastructure rather than a project is the right strategic posture. Where the community dimension gets underweighted is in the assumption that professional translation, properly maintained, constitutes the end goal.

Community-based language access looks different. It involves bilingual community health workers who understand that "diabetes management" means something different to a Hmong elder than it does in a clinical pamphlet. It involves trusted messengers who can explain a benefits change in terms that map to how people in that community actually make decisions. It involves feedback loops — mechanisms for LEP community members to report when translated content is wrong, confusing, or missing.

The National Council on Interpreting in Health Care (opens in new window) has documented extensively how professional interpreter services, when deployed without community input into their design, frequently fail the populations they serve. The problem isn't the interpreters — it's the assumption that linguistic accuracy and communicative effectiveness are the same thing.

Who Gets to Audit the Infrastructure?

As explored previously in Marcus's piece, the procurement cycle is broken. Organizations translate content once and move on. The counterpoint I'd offer is that even organizations with robust maintenance cycles — regular content audits, vendor contracts that include update provisions, staff capacity to manage translated content — can still produce language access infrastructure that fails its users.

The audit question matters here. Section 508 compliance (opens in new window) and WCAG guidelines (opens in new window) give us technical frameworks for evaluating whether digital content meets accessibility standards. Language access has no equivalent community-auditable standard. There's no mechanism analogous to automated accessibility testing that lets a Vietnamese-speaking resident flag that the translated version of a city's housing assistance portal uses terminology that doesn't match how Vietnamese speakers in that city actually talk about housing.

Some jurisdictions are experimenting with community review panels for translated government content. The Pacific ADA Center (opens in new window) has documented approaches where disability and language access communities are involved in content review rather than treated as passive recipients of translated materials. These models are resource-intensive, but they produce infrastructure that actually functions.

The Capacity Argument Cuts Both Ways

Marcus notes that LEP.gov's four-factor analysis includes available resources as a consideration — and that most organizations underuse this framework. The capacity argument is typically deployed to explain why language access is limited. But community organizations serving LEP populations have been building language access capacity for decades, often with minimal resources, precisely because they understand that the communities they serve can't wait for institutions to get their procurement cycles right.

Partnerships with those organizations represent an underutilized infrastructure strategy. A county that contracts with a community health organization already embedded in its Somali-speaking population gets something a translation vendor can't provide: ongoing, trust-based communication that surfaces problems before they become compliance failures. This isn't a replacement for the operational infrastructure Marcus describes. It's what makes that infrastructure actually work.

The legal architecture — Title VI, Executive Order 13166, state-level language access laws — creates the floor. But floors aren't the goal. The goal is digital and service infrastructure that LEP communities can actually use to access healthcare, benefits, legal protections, and civic participation. Building on this framework requires treating community members not as the subjects of language access policy, but as the people best positioned to tell you whether it's working.

That's not a soft add-on to the operational argument. It's the difference between infrastructure that checks boxes and infrastructure that functions.