The Evacuation Notice Nobody Could Read: Accessible, Translated Emergency Communication Under Pressure

Every other accessibility obligation gives you time. A website has a compliance date. A document backlog has a remediation schedule. A procurement has a solicitation cycle. Emergency communication has none of that: the requirement arrives at the same moment as the emergency, and whatever you have prepared in advance is what you have.

This is the one area where planning is not a best practice but the entire mechanism of compliance. You cannot commission a translation during a wildfire evacuation. You cannot caption a press conference that is already over. If the capability is not built before the event, the obligation is simply unmet at the moment it mattered most.

What does the law actually require during an emergency?

The governing standard for state and local government is effective communication, at 28 CFR § 35.160. A public entity must take appropriate steps to ensure that communications with members of the public with disabilities are as effective as communications with others, and must furnish appropriate auxiliary aids and services to give people with disabilities an equal opportunity to participate in and benefit from its programs.

Two features of that standard matter enormously in an emergency.

First, it contains no urgency exception. The regulation does not relax the effective-communication requirement when circumstances are difficult, and emergency management is a program of the entity like any other. The obligation applies to the evacuation order exactly as it applies to the parks brochure.

Second, “as effective as” is a comparative test. The question is not whether you made some effort. It is whether the deaf resident and the blind resident received communication as effective as the hearing, sighted resident did — in content, and in timeliness. An alert that reaches one group twenty minutes after the other has failed the comparison even if it eventually arrived.

Subpart E does acknowledge emergencies in one narrow place: it permits reliance on an accompanying adult, or in extremis a minor child, to interpret where there is an imminent threat to safety and no interpreter is available. That is a limited allowance for an unforeseeable moment, not a licence to plan on having no interpreter. And § 35.162 separately requires telephone emergency services, including 911, to provide direct access to users of TDDs and computer modems.

Language access runs in parallel under Title VI of the Civil Rights Act, which remains the correct authority for obligations toward people with limited English proficiency. The executive order that agencies used to cite alongside it was revoked in 2025 — we cover what changed and what did not. Title VI itself is untouched, and the meaningful-access standard it carries did not soften.

Where do emergency communications actually fail?

The failures are consistent enough to be listed.

The alerting system truncates. Mass-notification platforms impose character limits, and the compressed text drops the specifics — which streets, which direction, which shelter. The compressed version is often the only version a screen-reader user receives, because the fuller detail lives behind a link to an inaccessible page.

The critical detail is in an image. An evacuation map posted to social media, a road-closure graphic, a shelter flyer photographed and shared. To a screen reader this is a blank. It is also, almost always, English-only, so it fails two populations at once.

The press conference is uncaptioned and uninterpreted. Live streams without CART captions, and without an ASL interpreter in frame. ASL is a distinct language with its own grammar, not a visual encoding of English, which is why English captions do not substitute for an interpreter for many deaf residents. Note also that a broadcaster who crops the interpreter out of the shot has undone the provision entirely — camera framing is part of the deliverable. Our ASL and CART services post covers how these are arranged.

The PDF goes up untagged. The full shelter list, the boil-water notice, the disaster-assistance application — posted as scanned images under time pressure, unreadable to assistive technology for the entire duration of the event.

The translation is machine output nobody checked. This is where an emergency does real harm rather than merely failing an audit. Machine translation inverts negation, mistranslates imperatives, and renders place names as common nouns. “Do not return to your home” and “return to your home” are one error apart. Directional and conditional instructions are precisely the sentence types machine translation handles worst, and they are precisely what an emergency message consists of.

The alert never reaches the language at all. Many notification systems are configured with a single English template because the multilingual templates were never written.

How do you build this before you need it?

The answer is a pre-translated, pre-tested message library, and it is far more achievable than it sounds — because emergency messaging is formulaic.

Start from your hazard list. Your jurisdiction already maintains one: flood, wildfire, hurricane, tornado, chemical release, boil-water advisory, extreme heat or cold, active-threat lockdown, evacuation, shelter-in-place, all-clear. That list is finite, and each hazard generates a small set of message types.

Write each message as a template with variable slots. Fixed text carries the instruction; slots carry the specifics — street names, times, shelter addresses, phone numbers. The fixed text is what you pre-translate and pre-review, once, by a human linguist, at your leisure. During the event you fill slots, not sentences. This is what makes speed and accuracy compatible.

Fix the alerting system’s constraints in advance. Confirm the character limits per channel, whether the platform supports non-Latin scripts and right-to-left languages such as Arabic without mangling them, and whether it can send different language versions to subscriber segments. Find out during a drill, not during a fire.

Pre-build the accessible artefacts. Shelter lists, assistance-application forms and hazard fact sheets as tagged, accessible documents ready to publish — in every language you serve. For maps, write the text equivalent in advance: the boundaries of a flood zone can be described in words before there is a flood.

Arrange interpreter coverage contractually. On-call ASL interpreters, with after-hours terms, before the season starts. An interpreter you have to find at 2am is an interpreter you do not have.

Drill the communication, not just the response. Most exercises test operational response. Add the communication leg: publish the alert to a staging channel in every language and format, and have a screen-reader user and a native speaker of each language actually read it. That rehearsal finds more real defects than any checklist.

What about the all-clear?

Consistently the most neglected message in the set, and arguably the most consequential. Entities that translate the evacuation order often issue the return-and-all-clear notice in English only. The population most likely to have evacuated on an English-language order is not the population most likely to be reached by an English-language recall — and people who do not know it is safe stay displaced, or worse, return on rumour.

Pre-translate the all-clear alongside the warning. It is one more template.

Want an emergency message library built before your next season? Send us your hazard list, your notification platform and its character limits per channel, the languages your jurisdiction serves, and any existing English templates — then request a quote. We will tell you how many distinct templates you actually need, which ones need per-channel variants, and what it takes to have them human-translated, accessibility-checked and drilled. Our accessibility and compliance services page covers how we handle the accessibility and language-access requirements as a single programme rather than two procurements.