i18n, l10n & Principles for a More Accessible Web
summary
Explains concrete fixes and browser APIs: set the document lang to avoid screen reader and spellcheck errors and improve machine translation; use CSS unicode-range and :lang to load fonts and styles per language; use Intl.DateTimeFormat (dateStyle/timeStyle/formatRange), Intl.RelativeTimeFormat, Intl.ListFormat and DisplayNames for native date ranges, relative times, lists and currency/country names; Temporal is stage 2 with a polyfill; many JS i18n libs still exist (≈2M weekly npm downloads) but browser features already work.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:32World Map
- 2:39i18n
- 3:35l10n
- 4:51globalization
- 6:15localization
- 6:57cinema industry
- 8:54accessibility matter
- 11:37why this is important
- 12:38CSS
- 18:48List Format
- 19:58Display Names
- 21:04Temporal
- 21:55Conclusion
related talks
39mThink globally, act locally with i18n on the web
31mThink Globally, Act Locally on the Web
24mINTL: The best browser API you’re not using
17mi18n: A Brief Primer of Web Internationalization
35mCSS for internationalisation
26mThe State of the Art in Localization
19mLost in Translation? Intl, the Rosetta Stone of Web Development
34mWhat is the deal with internationalisation?