platform-guideline 1 linked patterns checked
W3C Internationalization: When to use language negotiation
Explains Accept-Language negotiation, its limits, the need for visible manual language controls on pages, explicit user override, and sticky language selection across site navigation.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Language selector | Choose language selector when users need to switch the current page, task, or product interface to another available language. | The selector names the current language and available alternatives in language labels users can recognize. | Supports visible manual override and sticky explicit language choice alongside automatic negotiation. |
Comparisons supported by this source
- Language selector vs settings management vs preference center vs adaptive defaults
W3C explains why automatic negotiation must be paired with visible manual language controls and sticky explicit choices.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: W3C Internationalization. Last checked: .