Decision: status page declares lang=en-US while serving bilingual content #522

Not a configuration change — a decision for the team. Raising it here because it is the strongest argument for eventually replacing Upptime, and none of the other changes touches it.

The problem

@upptime/status-page ships <html lang="en-US"> hard-coded in template.html. There is no .upptimerc.yml key that changes it.

Our page serves French content — every i18n value is a bilingual string like Up / Opérationnel — inside a document declared as English. That fails WCAG 2.1:

• 3.1.1 Language of Page — the declared language is wrong for half the content
• 3.1.2 Language of Parts — the French passages are not marked

A screen reader pronounces the French half with English phonetics.

Why configuration cannot fix it

• A snippet in status-website.js can set document.documentElement.lang, but only to one language. That fixes 3.1.1 for one audience and leaves 3.1.2 failing for both.
• Marking the French halves with <span lang="fr"> would be correct, but i18n values are rendered as text, not HTML.
• Serving two pages is not possible: Upptime supports one status page per repository.

Options

1. Fork @upptime/status-page and patch the template. Adds a maintenance burden we removed for good reasons (see MAINTENANCE.md §6).
2. Accept and document the gap, with a dated plan to address it.
3. Treat it as the trigger for evaluating a replacement. Kener has 24 real locales including French and serves multiple status pages from one instance.

Worth deciding deliberately rather than by default.