The Audit Nobody Runs: Title VI, the ADA, and the Gap Between Them

A government benefits portal can earn a clean WCAG 2.1 AA audit, post its accessibility statement, and still systematically exclude 25 million people. Not because the audit was wrong. Because it tested the wrong thing.

This is the compliance gap that almost no organization closes — and almost no auditor tests. Disability access and language access are treated as separate programs, governed by separate laws, owned by separate teams. In practice, they land on the same pages, the same forms, and the same users. The populations overlap. The technical surfaces overlap. The legal obligations overlap. The audits don't.

Two Mandates, One User

The legal architecture here is worth understanding precisely. Title II of the ADA prohibits disability-based discrimination by state and local government entities. Section 508 of the Rehabilitation Act requires federal agencies to make electronic and information technology accessible. WCAG 2.1 AA provides the technical standard that both frameworks increasingly reference.

Separately, Title VI of the Civil Rights Act (opens in new window) prohibits discrimination based on national origin by recipients of federal financial assistance — which includes virtually every state agency, county government, public university, and federally funded nonprofit. Executive Order 13166 (opens in new window), signed in 2000 and reinforced repeatedly since, requires those same entities to provide meaningful access to programs and services for people with limited English proficiency (LEP).

These are not optional guidance documents. They are enforceable civil rights mandates. The Department of Justice has pursued Title VI LEP enforcement against healthcare systems, courts, and social services agencies. The legal exposure is real — but more to the point, the human cost is real. Multilingual people with disabilities are entitled to equal access under both frameworks. Most compliance programs deliver neither fully.

What the law has never quite forced organizations to confront is this: a multilingual person with a disability experiences both barriers simultaneously. A Hmong-speaking blind user navigating a Medicaid enrollment portal needs the page to work with a screen reader and needs the content to exist in a language they can understand. A WCAG audit addresses one dimension. A translation review addresses the other. Neither addresses both at once.

What Traditional Translation Misses in Accessible Web Applications

This is where the technical gap becomes concrete — and where most compliance programs quietly fail.

Traditional translation services handle visible text. They translate what a sighted user reads on the screen: headings, paragraphs, button labels, navigation items. That work has real value. It also leaves an entire layer of a modern web application completely untouched.

Assistive technology — screen readers, in particular — doesn't just read visible text. It reads ARIA labels, ARIA roles, and ARIA live regions. It reads alt text on images. It reads error messages surfaced by form validation, which are often injected dynamically after a user attempts to submit. It reads modal dialog titles and tooltip content. In single-page applications, it reads content that loads asynchronously after the initial page render — content that may not exist in the HTML when a translation tool first processes the page.

Idioma.chat (opens in new window) was built specifically to close this gap. Where conventional translation pipelines capture static visible text, idioma.chat translates the full accessibility layer: ARIA attributes, alt text, form validation messages, modal and tooltip content, and dynamically loaded content in single-page applications. The distinction matters enormously. A translated page that leaves ARIA labels in English isn't accessible to a screen reader user whose primary language isn't English. It passes neither mandate fully.

This is the technical reality that compliance teams need to internalize: translation and accessibility are not parallel tracks that occasionally intersect. On a modern web application, they are deeply entangled. You cannot fully satisfy one without addressing the other.

The Audit Methodology Problem

Why does this gap persist? Part of the answer is structural. Accessibility audits are typically scoped to WCAG conformance. Language access reviews are typically scoped to document translation and interpreter availability. Neither audit methodology was designed to test the intersection.

Automated accessibility testing tools — already limited in what they can detect, as research on the gap between automated and manual audits makes clear — have no mechanism for evaluating whether ARIA content is accurately translated. They can check whether an ARIA label exists. They cannot check whether that label means anything to a user who reads Spanish or Somali.

Manual accessibility audits can catch more nuanced failures, but auditors working in English will test the English version of a site. The translated versions — if they exist at all — are rarely included in the audit scope. This isn't negligence. It's a scoping problem that reflects how compliance programs were designed: disability access in one silo, language access in another.

The compliance framework fragmentation problem that creates organizational paralysis across WCAG, Section 508, and EN 301 549 is compounded when you add Title VI and EO 13166 to the stack. Most compliance teams are already stretched managing one set of technical standards. Adding a second legal framework with its own enforcement mechanism and its own technical requirements pushes many organizations past their operational capacity.

What DOJ Enforcement Actually Looks Like

The DOJ's Title VI LEP enforcement has historically focused on high-stakes service contexts: courts, hospitals, social services. The pattern in settlement agreements tends to follow the same arc — an agency provides inadequate language access, a complaint is filed, an investigation surfaces systemic failures, a resolution agreement requires a corrective action plan. The settlement trap dynamic applies here too: organizations that settle Title VI complaints often address the immediate complaint without building the infrastructure to prevent recurrence.

What's largely absent from enforcement history is scrutiny of the digital language access layer — specifically, whether translated web content actually reaches assistive technology users. That gap in enforcement attention shouldn't be read as permission. The legal obligation under EO 13166 doesn't distinguish between visible text and ARIA content. Meaningful access means meaningful access.

As government services continue migrating online, and as agencies invest in digital transformation, the probability that digital language access failures will draw enforcement attention increases. The populations affected are large. The technical failures are documentable. The legal framework is already in place.

Designing Audits That Cover Both Mandates

The practical implication for compliance leaders is straightforward, even if the implementation isn't: audit scope must expand.

A comprehensive audit of a government-facing digital service should test WCAG conformance and verify that translated versions of the site maintain full accessibility — including ARIA labels, error messages, and dynamically loaded content. Procurement specifications for translation services should explicitly require coverage of the assistive-technology layer, not just visible text. Idioma.chat (opens in new window) represents the technical approach that makes this possible at scale.

Beyond audit scope, organizations need to examine their governance structure. If the ADA coordinator and the Title VI coordinator never sit in the same room, the gap between their programs will persist regardless of how good each individual program is. The standards fragmentation crisis that already fragments disability access compliance becomes more acute when language access is treated as a separate domain with separate ownership.

The 25 million people in the United States with limited English proficiency aren't a niche population. Among them are people with disabilities, people navigating benefits systems, people interacting with courts and healthcare and housing agencies. They are entitled to meaningful access under both Title VI and the ADA. Right now, most compliance programs are testing for one and assuming the other.

That assumption is both legally wrong and practically consequential. The audit that closes this gap isn't a new invention — it's the one that finally tests what the law has always required.