Semantic Translation Is a Symptom. The Audit Industry Is the Disease.

Patricia's analysis of the semantic translation gap is technically precise. But focusing on what compliance programs fail to detect obscures the more fundamental question: why do compliance programs define success this way at all?

In their recent analysis, the argument is structured around a structural gap — two legal frameworks, administered separately, producing audits that never ask whether translated content preserves its full semantic layer. That framing is correct. But it implicitly treats the audit apparatus as a neutral instrument that simply needs better calibration. The evidence suggests something more systemic: the compliance industry has financial and institutional incentives to define accessibility narrowly, and those incentives are upstream of every technical failure the article describes.

The Compliance Market's Structural Problem

The U.S. digital accessibility compliance market generates substantial revenue — estimates from accessibility consulting firms and industry analysts place it in the hundreds of millions annually. That market is built almost entirely on WCAG conformance testing (opens in new window), automated scanning, and audit reports that produce a defensible paper trail. The business model rewards checkboxes, not outcomes.

This matters because WCAG conformance and actual usability are not the same thing. The Web Accessibility Initiative (opens in new window) has been explicit about this distinction since at least 2016: conformance to technical standards is a floor, not a ceiling, and a page can pass every automated WCAG test while remaining functionally unusable for its intended audience. When a government portal's Spanish translation passes a WCAG scan because the visible body copy is in Spanish, the audit tool has done exactly what it was designed to do. The problem is the design.

As explored previously, the semantic layer — button labels, error messages, alt text, embedded PDF metadata — falls through the gap between disability access audits and language access reviews. But that gap exists partly because neither audit type is designed to ask functional questions. They're designed to produce audit reports.

What "Meaningful Access" Actually Requires

The Department of Justice's guidance on Title VI (opens in new window) uses the phrase "meaningful access" deliberately. The standard is not whether translated materials exist. It is whether a person with limited English proficiency can actually use the program. That is a functional standard, and it has never been reducible to a document checklist.

The Executive Order 13166 framework (opens in new window), which requires federal agencies and federally funded recipients to develop language access plans, was designed with this functional standard in mind. But implementation has drifted toward documentation: do you have a plan, do you have translated materials, can you produce them for an auditor. The question of whether a Spanish-speaking screen reader user can actually complete a housing assistance application has essentially never appeared on a compliance audit form.

The Great Lakes ADA Center (opens in new window) and peer regional centers have published technical assistance materials acknowledging that the intersection of disability access and language access creates compliance complexity that standard audit frameworks don't address. This is not a new observation. It has simply not produced market pressure to change audit methodology, because the entities purchasing compliance audits are primarily motivated by liability management, not service delivery.

The Procurement Problem

Government agencies don't buy accessibility. They buy compliance documentation. This distinction, which sounds semantic, has concrete consequences. When a municipal agency contracts for a benefits portal, the accessibility requirements in the procurement document are almost universally written as WCAG 2.1 AA conformance. Not "users with disabilities can complete the application." Not "LEP users can navigate the full transaction flow." WCAG 2.1 AA conformance, because that's what the agency's legal team knows how to specify and what the vendor's legal team knows how to certify.

Section 508 of the Rehabilitation Act (opens in new window) requires federal agencies to ensure that electronic and information technology is accessible, but the practical implementation has followed the same pattern: conformance standards, not outcome standards. The Access Board's Section 508 refresh (opens in new window) incorporated WCAG 2.0 Level AA as the technical standard precisely because it was auditable. Auditable and functional are related but not identical.

The vendors building these portals are not, for the most part, acting in bad faith. They are delivering what the contract specifies. If the contract specifies WCAG conformance and the portal achieves WCAG conformance, the vendor has performed. The Spanish-speaking screen reader user who cannot complete the housing application is not a contract failure. She is an externality.

A Different Framework for the Same Problem

Building on this framework for understanding the semantic translation gap, the more productive intervention may not be adding a third audit layer that checks semantic completeness across languages. It may be shifting from conformance-based procurement to outcome-based procurement.

Several jurisdictions have begun experimenting with usability testing requirements as part of accessibility compliance — requiring vendors to demonstrate, with actual users from target populations, that key transactions can be completed. The UK Government Digital Service (opens in new window) has embedded this in their service assessment framework for years: accessibility is assessed partly through research with disabled users, not purely through technical audits. That model has not meaningfully penetrated U.S. government procurement.

The Pacific ADA Center (opens in new window) and similar regional technical assistance providers have the expertise to support outcome-based assessment frameworks. The barrier is not technical capacity. It is procurement culture and the liability-management logic that drives agencies toward documentation over function.

The Balanced View

None of this is to minimize the technical analysis of semantic translation failures. That analysis is correct and the legal frameworks it maps are real. But practitioners working in this space — accessibility coordinators, language access officers, procurement officers, advocates — need to understand that the audit industry's incentive structure actively resists the kind of integrated, functional assessment that would catch these failures. Better checklists will produce better-documented failures. Outcome-based accountability might produce fewer of them.

The 25 million people with limited English proficiency in the United States, and the substantial overlap between that population and people with disabilities, deserve compliance programs designed around their ability to use government services. That requires confronting not just what audits miss, but why the audit market is structured to miss it.

For more on how we approach the intersection of legal frameworks and practical implementation, see our editorial approach.