Overview#
A dispatcher answering emergency calls at 3am cannot afford a blank panel because a language file loaded slowly, so the platform treats localisation as an operational safety property: every screen stays fully legible in the user's language, and complete built-in fallback text guarantees that a missing or slow translation bundle can never blank a working console. If a language pack fails to load mid-shift, operators see clear English labels instead of raw keys or empty panels.
Every workspace ships its complete translation set in seven supported languages: English, Spanish, French, German, Irish, Dutch and Portuguese. Navigation, the command palette, review queues and home-page widgets all load their full translations, automated guards block any release in which a page is missing part of its translation set, and a resilient language provider degrades gracefully instead of crashing the page when translations are unavailable.
Key Features#
- Seven-Language Workspace Coverage: Every workspace loads its complete translation set in English, Spanish, French, German, Irish, Dutch and Portuguese, covering navigation, the command palette, review queues and home-page widgets.
- Guaranteed Fallback Text: Every emergency console widget, error boundary and accessibility label carries complete built-in fallback text, so a missing or slow language bundle shows clear English labels rather than raw keys or empty panels.
- Resilient Language Provider: When translations are unavailable, the language layer degrades gracefully instead of crashing the page, keeping operational screens usable through the incident at hand.
- Release-Blocking Completeness Guards: An automated guard blocks any release where a page is missing part of its translation set, so translation gaps and mixed-language pages cannot creep back in.
- Localised Accessibility Labels: Screen-reader labels are localised alongside visible text, including search-field labels and status strings, so assistive-technology users work in the same language as sighted users.
- Specialist Console Coverage: Emergency console widgets, from call controls and the callback queue to notifications, delivery analytics, procedures, demand forecasting, and the fatigue and maritime modules, keep their message bundles in sync across all language packs.
- Fully Localised Connector Catalogue: The data source connector catalogue is completely translated in all seven languages, in both the main application and the data platform workspace.
- Locale-Aware Details: The emergency console's browser-tab icon adapts to the user's locale, served without an extra network request.
Use Cases#
- Night-Shift Dispatcher: A call taker keeps a stable, fully legible console through a long shift in any supported language, even if a language bundle fails to load mid-shift.
- New-Locale Roll-Out: An emergency centre deployed in a new locale remains fully legible on day one, before its complete translation pack ships.
- Irish-Language Agency: An analyst working in Irish browses the data connector catalogue with no untranslated strings, down to the screen-reader labels.
- Multilingual Analyst Team: A French-speaking analyst moves between workspaces all day and never encounters untranslated interface fragments or pages that mix languages.
Integration#
Localisation is built into every workspace rather than bolted onto a few. The same translation and fallback machinery serves the emergency call-taking console, review queues, dashboards, administration areas and the data connector catalogue, and localised accessibility labels flow through to assistive technology across all of them. Interface localisation complements, and is distinct from, live translation of caller speech and multilingual call handling, which are covered by the platform's translation services and multilingual call-taking capabilities.
Open Standards#
- ISO 639-1: Supported interface languages are identified by their standard two-letter language codes, covering English, Spanish, French, German, Irish, Dutch and Portuguese.
- Unicode: All interface text is handled as Unicode, so every supported language renders correctly, including accented characters.
- WCAG 2.2: Accessibility labels are localised in line with the Web Content Accessibility Guidelines, so screen-reader users receive the same language coverage as sighted users.
Last Reviewed: 2026-07-16 Last Updated: 2026-07-16