The applicant flow ships in English only. This page describes how
language selection works so the behavior is predictable for every
applicant.

## How language is picked

The applicant flow uses the language declared by the applicant's
browser. The platform reads the `Accept-Language` HTTP header on the
first request and, on the client, falls back to `navigator.language` for
in-flow updates. The closest match against the platform's list of
supported locales wins; if no supported locale matches, the flow falls
back to English.

Since English is the only supported locale, every applicant sees
English regardless of their browser locale.

## Browser locale

For developer testing, you can override the browser locale:

- **Chrome / Edge** — DevTools -> Sensors -> Locale.
- **Firefox** — `about:config` -> `intl.accept_languages`.
- **Safari** — change the system language.

The applicant page reads the locale at first load; reload after changing
the setting.

## Workflow template overrides

There are no language overrides per workflow template. Every workflow
template renders the applicant flow in English.

## What to tell the applicant

If a customer reports an applicant getting "the wrong language," the
answer is: the applicant flow is English-only. The browser locale picker
has no effect because English is the single supported locale.

## Supported languages

- **English (`en`)**: every applicant sees this.

Developer-facing surfaces (the console, the documentation, and API
error messages) also ship in English only. These are operator surfaces,
not applicant surfaces.