Language Access Isn't an Accessibility Add-On. It's a Procurement Problem.

Keisha's analysis of the language access gap in digital accessibility is correct on the diagnosis. Twenty-five million people with limited English proficiency are navigating digital services built almost entirely in English, and WCAG conformance does nothing to fix that. The civil rights failure is real.

But understanding why this gap persists requires looking past legal frameworks and into something less glamorous — the operational machinery of how organizations actually purchase, implement, and sustain accessibility programs. The language access gap isn't primarily a knowledge problem or even a legal enforcement problem. It's a procurement and capacity problem, and treating it as anything else produces recommendations that sound right but don't change behavior.

How Accessibility Procurement Shapes What Gets Built

Most mid-to-large organizations don't build accessibility programs from scratch. They purchase them — through contracts with overlay vendors, remediation firms, audit consultancies, and testing platforms. The accessibility vendor market has grown substantially (opens in new window) as Section 508 and WCAG enforcement pressure has increased, and vendors have responded by building products that map to those specific standards.

This creates a structural reality: when an organization issues an RFP for accessibility services, the market responds with WCAG-shaped solutions. Vendors compete on WCAG coverage, automated testing accuracy, and remediation throughput. Language access doesn't appear in most accessibility RFPs because it doesn't appear in most accessibility standards — and vendors don't volunteer scope they aren't being evaluated on.

The result is that organizations end up with technically compliant programs that are structurally incapable of addressing language access, not because decision-makers chose to ignore LEP users, but because the procurement process never surfaced the question. By the time a compliance team recognizes the gap, they're locked into multi-year vendor contracts that weren't scoped to address it.

This is what I'd call an operational capacity failure — and it's distinct from the legal analysis Keisha lays out in her original piece. Legal frameworks tell you what's required. Operational capacity determines whether organizations can actually deliver on those requirements at scale.

The Staffing Architecture Problem

The procurement issue compounds a staffing problem that's equally structural. Accessibility programs are typically staffed by people with backgrounds in disability access — screen reader testing, cognitive accessibility, motor impairment considerations. That expertise is hard-won and genuinely valuable. But it doesn't transfer to language access work, which requires entirely different competencies: translation quality assessment, cultural adaptation, community engagement with LEP populations, and familiarity with Executive Order 13166 (opens in new window) implementation guidance.

According to the Department of Justice's LEP guidance (opens in new window), organizations subject to Title VI must conduct a four-factor analysis to determine the extent of their language access obligations. That analysis requires understanding community demographics, frequency of contact with LEP individuals, the nature and importance of the program, and available resources. Almost no accessibility team has the institutional knowledge to conduct that analysis. It lives — when it exists at all — in civil rights compliance offices, legal departments, or community relations functions that rarely coordinate with digital accessibility teams.

The Pacific ADA Center (opens in new window) and other regional technical assistance centers have documented this coordination failure repeatedly in their training materials. Organizations compartmentalize disability access and language access because those mandates arrived through different legal channels, are enforced by different agencies, and historically attracted different professional communities. Fixing that requires deliberate organizational design, not just awareness.

What Operational Integration Actually Requires

At Accessible Future, we analyze accessibility challenges through a framework that treats operational capacity as a prerequisite for sustainable compliance — not an afterthought. The question isn't just whether an organization knows it should address language access. The question is whether it has the staffing, vendor relationships, budget cycles, and internal coordination mechanisms to actually do it.

For language access specifically, that operational picture looks like this:

Translation and localization infrastructure: Organizations need either in-house translation capacity or established vendor relationships with quality controls. Machine translation alone is insufficient for high-stakes content — research on machine translation quality for low-resource languages (opens in new window) documents significant accuracy problems that can make content misleading or inaccessible.

Community feedback mechanisms: Translated content that doesn't reflect how communities actually communicate fails even if it's linguistically accurate. The Northeast ADA Center (opens in new window) has emphasized that meaningful access requires community input, not just technical translation.

Ongoing maintenance budgets: Translation isn't a one-time cost. Every content update, every new feature, every policy change requires corresponding language access work. Organizations that treat translation as a project cost rather than an operational line item will see their language access programs decay within 18 months of launch.

Cross-functional governance: Someone needs ownership over the intersection of digital accessibility and language access. In most organizations, that intersection is ungoverned — which means it's no one's problem until it becomes everyone's crisis.

The Budget Conversation No One Wants to Have

Building on the framework Keisha establishes for understanding this as a civil rights failure, the practical implication is that remediation requires budget commitments most organizations haven't made and aren't planning to make.

The ADA National Network (opens in new window) estimates that comprehensive accessibility programs for mid-sized organizations require sustained investment — and language access adds meaningful cost on top of disability access work. For organizations serving diverse LEP populations, the DOJ's language access planning resources (opens in new window) are explicit: language access programs are ongoing operational commitments, not compliance projects with end dates.

Advocates and journalists — myself included — can document the gap, frame the legal obligations, and make the ethical case for change. But organizations won't close the language access gap by understanding it better. They'll close it by restructuring procurement processes, hiring staff with the right competencies, establishing governance over the disability–language access intersection, and building budget lines that treat language access as infrastructure rather than initiative.

That's a harder conversation than diagnosing the problem. It's also the only conversation that produces results.

Marcus covers operational dimensions of accessibility compliance. Read more about our analytical approach or explore the full team's perspectives.