The Translation Gap Is Real. The Fix Isn't What You Think.

The scenario David describes in his recent analysis — a Vietnamese-speaking blind user stranded at a Medicaid form error — is real, documented, and genuinely underserved by current compliance frameworks. The diagnosis is accurate. Where I want to push back, or more precisely push further, is on what that diagnosis implies about solutions.

The instinct in accessibility journalism, including my own, is to frame this as a technical gap: WCAG doesn't require multilingual semantic layers, therefore organizations don't build them. Close the WCAG gap, close the access gap. That logic is clean. It is also, in my experience covering this space for fifteen years, incomplete in ways that matter operationally.

The organizations failing multilingual screen reader users aren't primarily failing because WCAG 2.1 lacks a language requirement. They're failing because they don't have the internal capacity to execute multilingual accessibility even when they want to. That's a different problem, and it points toward different solutions.

What Operational Capacity Actually Means for Multilingual Accessibility

Consider what a government agency would need to actually solve the problem David outlines at the semantic and document layers. You need translators who understand ARIA attributes well enough to produce accurate labels — not just grammatically correct ones, but semantically precise ones. You need QA processes that test translated content with actual screen readers in those languages. You need procurement language that makes vendors responsible for multilingual semantic accuracy, not just visual translation. You need a content management system that tracks language attributes at the component level, not just the page level.

None of these are primarily regulatory problems. They're workforce, vendor management, and systems architecture problems. According to research from the Pacific ADA Center (opens in new window), the organizations with the worst multilingual accessibility records are typically the same ones struggling with basic accessibility staffing — they don't have a dedicated accessibility coordinator, let alone someone with cross-functional expertise in both translation workflows and assistive technology QA.

The Department of Justice's guidance on language access (opens in new window) under Title VI is instructive here. DOJ has pushed federal agencies and recipients of federal funding toward language access plans for years. The 2023 update to Executive Order 13166 (opens in new window) implementation guidance explicitly requires agencies to assess the language access needs of their service populations. What the guidance reveals, in practice, is that most agencies have language access plans that are entirely disconnected from their digital accessibility plans. Two separate offices, two separate compliance frameworks, zero integration.

That structural disconnect is the actual operational failure. WCAG's silence on language is a contributing factor, not the root cause.

The Procurement Problem Nobody Talks About

Government agencies and large institutions don't build their own forms, their own CMS platforms, or their own error message libraries. They buy them. And the procurement process for these systems almost never includes multilingual accessibility requirements at the semantic layer.

Section 508 (opens in new window) conformance documentation — the VPAT — asks vendors to document accessibility support. It does not ask vendors to document multilingual accessibility support. An agency can purchase a fully Section 508-compliant form platform that hard-codes all error messages in English, deploy it to serve a population that is 40% Spanish-speaking, and be in complete procurement compliance. The vendor did nothing wrong under current standards. The agency did nothing wrong under current standards. The user gets an incomprehensible error message.

This is where the WCAG conformance framing — while analytically correct — can inadvertently let the procurement system off the hook. If the problem is framed as "WCAG doesn't require this," the implied solution is "update WCAG." But WCAG 2.2 is already finalized, and WCAG 3.0 (opens in new window) is years from adoption. Waiting for a standards update is a decade-long strategy for a problem affecting people today.

The faster lever is procurement. Agencies that add multilingual semantic accessibility requirements to their RFPs — requiring vendors to demonstrate screen reader testing in at least the top three languages of the service population — can move faster than any standards body. The Great Lakes ADA Center (opens in new window) has documented examples of state agencies using procurement requirements to drive vendor accessibility improvements that preceded formal regulatory changes by years.

The Workforce Gap Is Worse Than Reported

Even with better procurement language, agencies face a workforce problem that rarely surfaces in accessibility coverage. Multilingual accessibility QA requires testers who are both fluent in the target language and proficient with assistive technology. That is a genuinely rare combination. The accessibility testing workforce in the United States is already undersized relative to demand — research from the Bureau of Internet Accessibility (opens in new window) and practitioner surveys consistently show more open accessibility roles than qualified candidates. Adding multilingual fluency as a requirement narrows that pool further.

This isn't an argument against multilingual accessibility requirements. It's an argument for being honest about the implementation timeline and the workforce development investments that need to accompany any regulatory push. Organizations told to fix their multilingual semantic layers without a realistic path to finding or training people who can test them will do what organizations always do under compliance pressure without capacity: they'll document compliance they haven't achieved.

What Actually Moves the Needle

From an operational standpoint, the interventions most likely to produce real improvement in the near term are:

Integrated planning requirements. DOJ and HHS should require that language access plans and digital accessibility plans be developed jointly and reviewed jointly. The Vietnamese-speaking blind user doesn't exist in two separate compliance silos — neither should the plans meant to serve them.

Procurement standards updates. Section508.gov (opens in new window) guidance on VPAT requirements should be updated to include multilingual semantic accessibility as a documented capability, at minimum for agencies serving populations with significant LEP representation.

Dedicated technical assistance. The regional ADA Centers — Pacific, Great Lakes, Southwest, Southeast, Northeast — have the infrastructure to provide technical assistance on accessibility implementation. Expanding their mandate and funding to explicitly cover multilingual accessibility integration would create a support system for the agencies most likely to struggle.

Component-level language tracking. CMS vendors serving government clients should be pushed toward component-level language attribute management — not just page-level language flags, but tracking that follows each content component through translation workflows.

None of these require waiting for WCAG 3.0. None require litigation. They require the kind of operational coordination that is genuinely hard but genuinely achievable.

The technical gap David documents is real. The 25 million people with limited English proficiency who also rely on assistive technology deserve better than a compliance framework that doesn't see them. But closing that gap requires treating it as an operational and structural problem, not primarily a standards problem. The standards will eventually catch up. The question is what we do for those users in the meantime.

At CORS, we analyze accessibility challenges across four dimensions — community impact, operational capacity, risk exposure, and strategic positioning — because solutions that ignore operational reality tend to produce compliance theater rather than actual access. The multilingual semantic gap is a case where the operational dimension deserves at least as much attention as the regulatory one.