Language Access Laws and Compliance in 2026 (What’s Changed?)

In 2025, two executive orders changed the federal government’s approach to language access compliance. Executive Order 14224 designated English as the official U.S. language and revoked the longstanding executive order supporting language access for people with limited English proficiency. Executive Order 14281 then directed agencies to deprioritize enforcement of laws and regulations that rely on disparate-impact liability, changing how certain Title VI protections are enforced.

However, Title VI, Section 1557, the Americans with Disabilities Act (ADA), and Section 504 remain in force.

Earlier in 2026, we met with language access expert and lobbyist Dr. Bill Rivers for our webinar, Building a Defensible Language Access Strategy in the AI Era, to discuss these federal shifts and the growing use of AI. Since then, agencies have withdrawn guidance and removed resources, states have adopted conflicting approaches, and new developments in healthcare, telehealth, and AI have added to the compliance landscape.

For language access leaders, these developments necessitate revisiting existing plans. A strategy written six months ago, for instance, may no longer reflect available federal guidance, the requirements in every state where the organization operates, or the safeguards needed when using AI.

Here is what has changed and what organizations should review now:

2026 language access compliance changes at a glance

Federal and state policy changes have affected language access guidance, enforcement, and program requirements differently. Here’s a quick summary of what changed and what each development means for organizations.

Federal guidance changed, but the laws stayed the same

Executive orders direct the executive branch, but they do not repeal a law passed by Congress.

Executive Order 14224, signed in March 2025, designated English as the official language of the United States and revoked Executive Order 13166, which had shaped the federal language access framework since 2000. The Department of Justice then directed agencies to review guidance issued under the earlier order. LEP.gov and many agency language access pages were removed, eliminating the central reference library organizations had used to build language access plans.

The Department of Homeland Security (DHS) made the distinction explicit when it rescinded its 2011 language access guidance in July 2026. In the same notice, DHS said recipients of its financial assistance still have a continuing obligation to comply with Title VI, applicable Title VI regulations, the Rehabilitation Act, and other federal civil rights laws. It also noted that language assistance and qualified sign language interpreters may still be required under the circumstances.

A hospital, school district, public agency, or nonprofit that receives federal funding shouldn’t read the removal of a guidance page as permission to stop providing language access. The governing obligations still come from the laws and regulations that apply to the organization.

What remains legally binding: Title VI, Section 1557, and the ADA

Title VI of the Civil Rights Act of 1964 continues to prohibit discrimination based on race, color, or national origin in programs and activities receiving federal financial assistance. Section 1557 of the Affordable Care Act continues to require covered health programs and activities to take reasonable steps to provide meaningful access to limited English proficient (LEP) individuals.

The ADA and Section 504 also continue to require effective communication for people who are Deaf, Blind, or hard of hearing.

Other federal statutes apply to specific settings, including voting, housing, education, workforce programs, and disaster response. State and local laws operate alongside those federal requirements and may impose additional obligations.

For healthcare interpreting, the 2024 Section 1557 final rule remains a particularly important operational reference. Its language access provisions address qualified interpreters and translators, restrictions on relying on unqualified adults or children, and a Notice of Availability in English and at least the 15 most commonly spoken languages among LEP people in each relevant state.

Language access advocates rebuilt the missing reference layer

The federal pullback didn’t leave the field without a reference point. The National Coalition for Language Access (NCFLA) was formed in March 2025 as a network of language access administrators, physicians, lawyers, interpreters, educators, and advocates. The coalition has become an important response to the loss of federal infrastructure.

NCFLA now maintains a plain-language federal law and policy library, an active tracker of federal and state developments, and links to archived federal guidance. Organizations can still access previous guidance to understand established compliance practices, even when the pages are no longer hosted by the agencies that produced them.

The U.S. Commission on Civil Rights also released a bipartisan report in May 2026 after a yearlong investigation. It documented the absence of legally required interpreters, mistranslated health information, and wide differences in machine-translation accuracy across languages.

The Commission stated that Executive Order 14224 did not eliminate statutory obligations under Title VI, Section 1557, or the ADA, and recommended that Congress include stronger language-access requirements directly in statute.

2026 Updates: Joint Commission and the SPEAK Act

Joint Commission and National Performance Goals

On January 1, 2026, The Joint Commission replaced its National Patient Safety Goals with 14 National Performance Goals under Accreditation 360. Language access is addressed most clearly in Goals 4 and 7. Accredited hospitals are expected to examine quality outcomes across patient populations, including preferred language, and to provide patients with information in a language and format they understand.

This change consolidated existing expectations rather than creating an entirely new language access mandate. It also changes what a defensible program should demonstrate. Hospitals, for example, need more than interpreter utilization totals. They’re also required to connect language data to quality outcomes and demonstrate that communication is understandable to a patient.

The SPEAK Act and Telehealth

The Supporting Patient Education and Knowledge Act, commonly called the SPEAK Act, became law through the Consolidated Appropriations Act on February 3, 2026.

It directs the Department of Health and Human Services to issue guidance within one year on integrating interpreters into telehealth visits, providing accessible platform instructions, improving patient portal access, enabling multi-party video calls, and providing multilingual reminders, prescription information, and other patient materials.

The law doesn’t impose the five new operational requirements on providers today. Rather, it requires HHS to develop guidance by approximately February 2027. Currently, health systems should continue to use the five areas as an audit framework, especially when selecting telehealth platforms or redesigning digital patient workflows.

State language access requirements are moving in opposite directions

Relying on federal policy guidance is no longer enough to understand language access obligations. Some states are restricting access, while others are creating stronger, more standardized requirements.

Florida, for example, began administering all driver license knowledge and skills exams exclusively in English back in February 2026. Translation services are also no longer allowed for those exams, which had previously been offered in Spanish, Haitian Creole, Portuguese, and other languages.

Washington moved in the other direction. HB 2475 directs the state Office of Equity to develop uniform guidelines for language-accessible public programs and services, along with a proposal for addressing shortages of qualified spoken-language and sign-language professionals.

For multistate organizations, this means a single plan built only around a federal baseline is no longer enough. The binding rule at a particular location may come from an insurance regulation, a court rule, a state agency policy, or a city ordinance. A practical language access plan now needs a state-by-state annex that identifies the requirements affecting each element.

AI is advancing faster than language access regulation

AI adoption has entered a stage of cautious implementation. Organizations face pressure to use AI to control costs and extend coverage, but users who test these tools also see inconsistency. That tension is pushing the conversation away from whether an AI tool is effective and groundbreaking, toward where it is appropriate, how its quality is measured, and what happens when it fails.

While there is no single federal statute written specifically for AI interpreting, existing legal obligations still apply:

• Covered organizations must take reasonable steps to provide meaningful access to individuals with LEP.
• Qualified interpreters or translators must be used when required by applicable laws and circumstances.
• Organizations must ensure effective communication for people with disabilities under the ADA and Section 504.
• AI tools must comply with applicable privacy and confidentiality requirements.
• Decisions about AI use should be reasonable, risk-based, and supported by documentation.

Written machine translation has a more specific rule in healthcare. Under Section 1557, critical documents that are machine-translated must be reviewed by a qualified human translator when accuracy is essential, the text is complex or technical, or the material affects a person’s rights, benefits, or meaningful access.

A live back-translation generated by the same AI system shouldn’t be mistaken for independent human review. A person who doesn’t understand the other language wouldn’t be able to tell whether that second AI output corrected the first error or repeated it in a different form.

Healthcare leaders are already drawing sharper use-case boundaries. In a 2026 survey of 123 healthcare respondents conducted by Fierce Healthcare and Boostlingo, 85% accepted AI interpreting for scheduling and billing, with or without human backup.

It should be noted, though, that acceptance fell for emergency, inpatient, and sensitive care. Meanwhile, 59.3% said they lacked confidence that AI would work correctly in real interactions, and 53.7% cited accuracy concerns.

Routine, lower-risk conversations may be reasonable starting points for AI, while clinical, legal, emotional, or otherwise high-stakes interactions call for qualified human interpreters.

Mixed and unpredictable workflows need an escalation path that staff can use without delay.

This need for escalation is central to Boostlingo’s approach: AI when it fits. Human when it counts. In practice, organizations can use AI for approved, routine, lower-risk interactions while maintaining a clear path to a qualified human interpreter when a conversation becomes complex, sensitive, or high stakes.

The proposed Language Access for All Act of 2026 would add more explicit federal requirements, including provisions addressing qualified interpreters and translators, agency language access plans, complaints, performance measures, and AI. H.R. 7223 and S. 4985 remain proposals in committee, however.

7-step checklist for updating a language access plan written in 2025

Because federal language access policy remains volatile, healthcare organizations should audit plans written in 2025 against the standing laws, patient care workflows, and LEP patient data they rely on today. Organizations outside healthcare can apply the same process to their service workflows and community language data.

1. Confirm the legal authority behind the plan

Identify the federal, state, and local laws and regulations that apply to each operation instead of relying on Executive Order 13166, LEP.gov, or withdrawn agency guidance. Archived guidance can still inform program design, but it should not be presented as current policy.

2. Update the organization’s LEP patient data

Review preferred-language records, interpreter requests, encounter volume, complaints, and demographic changes to confirm that the plan reflects the populations currently being served.

3. Compare the plan with actual patient care workflows

Follow the patient journey through scheduling, intake, consent, clinical conversations, discharge, and follow-up to verify that staff can access appropriate language support at every stage. Be sure to include patient portals, telehealth visits, multiparty video calls, and multilingual communications in the review.

4. Recheck notices and accreditation requirements

Confirm that Section 1557 notices are current, available in the required languages, and displayed in the appropriate physical and digital locations. Hospitals should also align their policies and quality reporting with Joint Commission Goals 4 and 7.

5. Define when AI can and shouldn’t be used

Document the encounters where AI is permitted, the situations where it is prohibited, who approves each use case, what qualifies as human review, and how users reach a qualified human interpreter when needed.

6. Strengthen vendor requirements

Require vendors to provide evidence of interpreter qualifications, disclose where AI enters the workflow, report incidents, share relevant quality data, and support organizational audits.

7. Preserve contemporaneous evidence

Retain dated plans, language needs assessments, interpreter qualification records, encounter and training logs, AI approval decisions, complaints and resolutions, vendor reviews, and leadership approvals to show how decisions were made at the time.

Reasonableness remains central to many language access requirements. Records created at the time help an organization demonstrate that its decisions reflected the applicable laws, language needs, and risks, rather than an explanation assembled after a complaint or adverse event.

Put your language access program into practice in 2026

With less centralized federal guidance and a more fragmented policy environment, organizations need clear internal rules, qualified language professionals, state-level monitoring, auditable technology, and documented escalation paths.

Boostlingo supports language access programs by helping organizations put these practices into action. Teams can connect with qualified human interpreters, use AI interpreting for approved routine, lower-risk interactions, and maintain workflows that provide oversight and a clear path to human support when conversations require greater nuance, trust, or subject-matter expertise.

Request a demo to explore how Boostlingo can support your updated language access plan while keeping your organization in control.