Structural Fixes Won't Work Without Regulatory Teeth

Marcus makes a compelling case that operational capacity — not regulatory gaps — is what's actually keeping multilingual screen reader accessibility broken. His operational diagnosis is sharp: organizations lack translators fluent in ARIA semantics, QA pipelines that test translated content with actual assistive technology, and procurement language that holds vendors accountable for semantic accuracy rather than just visual translation. I don't dispute any of that. What I want to examine is the assumption embedded in that framing — that regulatory reform is the wrong lever to pull because the problem is structural.

Capacity doesn't materialize in a vacuum. It follows enforcement pressure, funding incentives, and explicit legal obligations. The history of disability rights implementation suggests that structural capacity problems in government agencies rarely get solved until there's a legal reason to solve them.

What ADA and Section 508 History Actually Shows About Capacity Building

The Americans with Disabilities Act turned 35 this year. For the first decade after its passage, the same argument Marcus is making now was made about physical accessibility: organizations don't have the architects, the contractors, the internal knowledge to execute ADA compliance. The gap, critics argued, was operational, not regulatory. What changed wasn't a sudden surge of voluntary capacity building. It was DOJ enforcement actions (opens in new window), settlement agreements that mandated specific remediation timelines, and the gradual development of a professional ecosystem — consultants, auditors, specialized contractors — that emerged specifically because legal liability created market demand for those services.

The Section 508 refresh of 2018 (opens in new window) followed a similar pattern. Federal agencies had nominally been subject to Section 508 since 2001. Compliance remained inconsistent and largely unmonitored for years. The 2018 refresh didn't just update technical standards to align with WCAG 2.0 — it renewed enforcement attention and created clearer accountability structures. Procurement language improved not because agencies suddenly developed internal expertise, but because vendors faced clearer legal exposure.

This pattern matters for the multilingual accessibility question. Marcus is right that you need translators who understand ARIA attributes. But those translators don't currently exist in sufficient numbers partly because there's no regulatory requirement driving demand for them. Workforce pipelines follow market signals. Market signals follow legal obligations.

Title VI Is Already There — Enforcement Is the Missing Piece

The regulatory foundation Marcus suggests is missing is actually partially in place. Title VI of the Civil Rights Act (opens in new window) requires recipients of federal financial assistance to provide meaningful access to people with limited English proficiency. Executive Order 13166, issued in 2000, directed federal agencies to develop language access plans. The DOJ's Language Access guidance (opens in new window) provides a framework for what meaningful access requires.

The problem isn't that regulatory tools don't exist. The problem is that Title VI enforcement for digital accessibility — particularly for the intersection of language access and assistive technology — has been inconsistent and largely reactive. Complaints drive investigations. Investigations drive settlements. Settlements drive remediation. But the population most affected by multilingual screen reader failures — blind and low-vision users who are also limited English proficient — faces compounded barriers to filing complaints in the first place. The feedback loop that drives enforcement is broken at the intake stage.

As explored in the original analysis, the scenario of a Vietnamese-speaking blind user stranded at a Medicaid form error isn't hypothetical — it's a predictable outcome of overlapping compliance failures. But that user is unlikely to navigate the complaint process in English to report a failure they experienced in Vietnamese. Enforcement data undercounts the problem, which means enforcement pressure remains low, which means capacity investment remains low. That's a regulatory design problem, not just an operational one.

The WCAG Gap Carries More Legal Weight Than Practitioners Assume

Marcus frames the absence of multilingual semantic requirements in WCAG 2.1 as operationally significant but not the core issue. From a practitioner standpoint, that's reasonable. From a legal liability standpoint, the gap matters more than he suggests.

When organizations defend against ADA Title III digital accessibility claims, WCAG conformance — even though WCAG is not itself law — functions as a de facto safe harbor in litigation. Plaintiffs' attorneys and defense counsel both treat WCAG 2.1 Level AA as the relevant benchmark. Organizations that meet it have a stronger defense. Organizations that don't are more exposed. This creates a powerful incentive structure that Marcus's operational framing underweights.

If WCAG incorporated explicit multilingual semantic requirements — language attribute accuracy at the component level, screen reader testing requirements for translated content, ARIA label accuracy standards for non-English interfaces — those requirements would propagate through legal risk calculations, procurement contracts, and vendor obligations within a few litigation cycles. The Web Content Accessibility Guidelines development process (opens in new window) at W3C is slow, but its outputs carry outsized influence precisely because of how they function in the legal ecosystem.

The Great Plains ADA Center (opens in new window) and other regional ADA centers have documented how technical standard changes ripple through state and local government procurement within two to three budget cycles. That's not fast. But it's a more reliable mechanism than voluntary capacity building.

Both Levers, Not Either/Or

The operational framework Marcus develops — workforce development, vendor accountability, CMS architecture, QA pipelines — is exactly right as a description of what organizations need to build. Where I'd push back is on the implied sequencing: fix operations first, then worry about regulation.

The evidence from ADA implementation, Section 508 enforcement, and language access compliance under Title VI points in the other direction. Regulatory clarity and enforcement pressure are what create the conditions under which organizations invest in operational capacity. You don't build a workforce pipeline for multilingual ARIA specialists because it seems like a good idea. You build it because contracts require it, audits check for it, and liability follows if you don't.

At Accessibility In Focus, the analytical framework we apply to these questions tries to hold both dimensions simultaneously — the operational reality practitioners face and the structural conditions that shape what organizations prioritize. The multilingual accessibility gap is genuinely both. Treating it as primarily operational, without attending to the regulatory incentives that drive capacity investment, risks producing thoughtful analysis that doesn't translate into changed practice.

The Vietnamese-speaking blind user stranded at a Medicaid error message needs translators who understand ARIA semantics. She also needs enforcement mechanisms robust enough that the agency serving her had a reason to hire them. The practical implication for practitioners: if your organization is waiting for internal champions to build multilingual accessibility capacity voluntarily, you're waiting for the wrong signal. Watch the enforcement docket and the next WCAG working draft instead.