Blog | Dynamic Language

DHS Rescinded Its Title VI Language Access Guidance. Here Is What Actually Changed

Written by Dynamic Language | Jul 20, 2026 11:18:44 PM

On July 14, 2026, the Department of Homeland Security (DHS) rescinded the guidance it had given recipients of its funding since 2011 on serving people with limited English proficiency (LEP) under Title VI of the Civil Rights Act of 1964. The rescission removes the how-to document. It does not remove the law. Title VI still prohibits national origin discrimination in any program that receives federal financial assistance, and the DHS notice itself states that recipients “have a continuing obligation to comply with Title VI, all applicable Title VI regulations, all applicable federal civil rights laws and nondiscrimination provisions.”

Organizations that read the headline as the end of language access requirements are taking on risk. Organizations that read it carefully will notice something more demanding: the obligation stands, and the federal playbook for meeting it is gone.

What DHS actually did

The notice, published in the Federal Register as document 2026-14128, rescinds the agency's 2011 guidance to recipients of DHS financial assistance (76 FR 21755). DHS took the step to conform with Executive Order 14224 of March 1, 2025, which designated English as the official language of the United States and revoked Executive Order 13166 of 2000, the order that had directed each federal agency providing financial assistance to publish LEP guidance for its recipients.

DHS is following a pattern, and more of it is coming. A July 2025 Attorney General memorandum encouraged all federal agencies to review guidance issued under Executive Order 13166 and rescind it where it conflicts with the new order and is not mandated by law or the Constitution. The Department of Labor rescinded portions of its own Title VI regulations effective July 2, 2026, and DHS amended parts of its Title VI regulations in June. Expect other funding agencies to act on the same memorandum. The DHS notice also says the agency anticipates issuing updated language access guidance in the future.

What did not change
  • Title VI itself. The statute, 42 U.S.C. 2000d, was passed by Congress in 1964. Guidance documents interpret it; rescinding guidance does not amend it.
  • The applicable Title VI regulations. The rescission notice reminds recipients that these still bind them.
  • Disability communication requirements. The same notice restates that recipients must make communication with individuals with disabilities as effective as communication with others under the Rehabilitation Act of 1973, including qualified sign language interpreters where needed.
  • Healthcare obligations. Providers covered by Section 1557 of the Affordable Care Act carry language access duties that come from a different statute and are untouched by a DHS notice.
  • Language assistance itself. The rescission notice reminds recipients, including subrecipients, that language assistance services “may be required under certain circumstances.” The document withdrawing the guidance says so in its own text.
  • State law and state contracts. This is the change organizations most often miss, and it is where two decades of our own contract history is instructive.
The requirement that lives in the contract

Dynamic Language has supported Washington and Oregon state agencies continuously since 2004. Across that period, federal guidance has been issued, revised, and now rescinded. The language access terms in state master contracts did not move with any of it, because they are written into procurement requirements and state law, and agencies budget against them year after year. A county public health department or a state benefits office that asks whether it still has to provide interpretation will usually find the answer in its own contract and its own state statutes before it ever reaches a federal guidance document.

For any organization holding public funding, the practical question this month is a mapping exercise: for each obligation in your language access plan, identify the source. Federal statute, federal regulation, state law, contract term, or accreditation standard. The 2011 DHS guidance was only ever one layer, and for most of the organizations we work with, it was never the binding one.

Why the guidance mattered anyway, and what replaces it

The 2011 guidance did useful work. It told recipients how a reasonable language access program looks: how to weigh the number of LEP people served, the frequency of contact, the importance of the service, and the resources available. With that roadmap withdrawn, an organization facing a complaint or an audit can no longer point to a federal document and say it followed the recipe.

What replaces the recipe is documentation. The organizations in the strongest position now are the ones that can show their work: which languages they support, based on what population data, delivered through which services, reviewed on what schedule, and decided by whom. In our government and healthcare engagements, the language access plan functions as an audit artifact, and the record of decisions matters as much as the services themselves. If anything, the rescission makes that record more valuable.

The non-political core of language access

Set the policy debate aside and the operational facts remain. Due process depends on notice a person can actually understand. A hearing notice only gives notice if the recipient can read it. An evacuation instruction only protects people who understand it. A benefits determination, a consent form, a school enrollment packet: each of these is a communication that carries legal or safety weight, and each fails at its purpose when it arrives in a language the recipient does not speak. Nearly 68 million people in the United States speak a language other than English at home, according to U.S. Census Bureau American Community Survey data. That figure describes the audiences public agencies serve every day, regardless of which guidance documents are in force.

Agencies and organizations that hold to that operational standard will find the current moment simpler than the headlines suggest. The reasons to communicate with the people you serve did not come from a 2011 guidance document, and they did not leave with it.

Frequently asked questions
Did DHS eliminate Title VI language access requirements?

No. DHS rescinded its 2011 guidance document explaining how funding recipients should serve LEP individuals. The rescission notice itself states that recipients have a continuing obligation to comply with Title VI, all applicable Title VI regulations, and all applicable federal civil rights laws. The statute is unchanged.

Does this apply to my organization if our funding comes from a different federal agency?

The July 14 rescission covers DHS funding recipients only. Each federal agency issues guidance for its own recipients, and several agencies have been revising Title VI materials in 2026. Check the current status of your own funding agency's guidance, and remember that the underlying statute and regulations apply across agencies.

Do state and local language access laws still apply?

Yes. State statutes, executive orders, and contract terms are independent of federal guidance. Agencies under state master contracts, including the Washington and Oregon contracts Dynamic Language has served since 2004, carry language access requirements that a federal rescission does not touch.

What about healthcare organizations?

Section 1557 of the Affordable Care Act imposes its own language access requirements on covered healthcare entities, separate from Title VI guidance issued by DHS. Hospitals, clinics, and health plans should treat their Section 1557 obligations as unchanged by this notice.

What should we do now?

Map each element of your language access plan to its legal source, document how you decide which languages and services to provide, and keep the decision record current. With federal how-to guidance withdrawn, a documented, data-based plan is the strongest evidence that your program meets the obligations that remain in force.

Will DHS issue new guidance?

The notice says DHS anticipates issuing updated language access guidance consistent with Executive Order 14224, the July 2025 Attorney General memorandum, and future Department of Justice guidance. No timeline is given. Until it arrives, the statute, the regulations, and your own documentation govern.

Sources
  • for All Federal Agencies from the Attorney General, Implementation of Executive Order 14224 (July 14, 2025).
  • Title VI of the Notice of Rescission of Guidance to Federal Financial Assistance Recipients Regarding Title VI, 91 FR 43108 (July 14, 2026), FR Doc 2026-14128, Docket DHS-2026-0364.
  • Executive Order 14224, Designating English as the Official Language of the United States, 90 FR 11363 (March 1, 2025).
  • Executive Order 13166, Improving Access to Services for Persons with Limited English Proficiency, 65 FR 50121 (August 16, 2000), revoked.
  • DHS 2011 Guidance, 76 FR 21755 (April 18, 2011), rescinded.
  • Rescinding Portions of Department of Labor Title VI Regulations, FR Doc 2026-13371 (effective July 2, 2026).
  • Memorandum Civil Rights Act of 1964, 42 U.S.C. 2000d.
  • U.S. Census Bureau, Language Use in the United States (American Community Survey), reporting nearly 68 million people speaking a language other than English at home.
About Dynamic Language

Dynamic Language is one of the few language service providers in the United States to hold five ISO certifications: ISO 9001 (Quality Management), ISO 17100 (Translation Services), ISO 27001 (Information Security), ISO 13485 (Medical Devices Quality Management System), and ISO 18587 (Machine Translation Post-Editing). As an NMSDC-certified Minority Business Enterprise (MBE), Dynamic Language helps government agencies meet supplier diversity requirements while accessing top-tier language services. Based in Seattle, we have served government agencies nationwide since 1985, providing translation, interpretation, and localization services in over 200 languages.

To learn more, contact us at www.dynamiclanguage.com/contact/