Names, not flags
Flags mean countries, not languages. Show endonyms with a recognizable globe icon (Norman, 1999) in a consistent spot, and add lang to each name (MDN, n.d.; W3C, 2023, 3.1.2).
Auto-detect and override
Default to browser language but allow changes (W3C Internationalization, n.d.); IP-based guesses fail travelers. Persist choices and support per-app language (Android Developers, n.d.); use a searchable bottom sheet for long lists.
After switching
Stay on the translated version of the same page; link versions with hreflang (Google Search Central, n.d.). Adapt dates, numbers and RTL (Reinecke & Bernstein, 2011) — affecting information architecture and conversion.
FAQ
- Can I use flags?
- Use language names, optionally with a globe icon.
- Is auto-detection enough?
- No, use it only as a default with manual override.
Sources reviewed: 2026-10-27
References
- W3C Internationalization. (n.d.). Language negotiation and site navigation. Auto-detect but allow override.
- MDN Web Docs. (n.d.). lang. The lang attribute.
- Android Developers. (n.d.). Per-app language preferences. Per-app language settings.
- Google Search Central. (n.d.). Tell Google about localized versions of your page. hreflang for localized pages.
- Reinecke, K., & Bernstein, A. (2011). Improving performance, perceived usability, and aesthetics with culturally adaptive user interfaces. ACM Transactions on Computer-Human Interaction, 18(2), 1–29. https://doi.org/10.1145/1970378.1970382 Culturally adaptive UIs.
- Norman, D. A. (1999). Affordance, conventions, and design. Interactions, 6(3), 38–43. Recognizable signifiers.
- World Wide Web Consortium. (2023). Web Content Accessibility Guidelines (WCAG) 2.2. Criteria 3.1.1 and 3.1.2.
