Today I learned that i18n is called i18n because it has 18 letters between the “i” and the “n”.
Funny thing, considering my first task as a ServiceNow developer was translating labels and texts into Spanish.
But I never connected the dots. The same applies to t9n, l10n and g11n.
Alaina Beaver starts this nullEDGE session with an interesting statement:
Everyone will use accessibility features at some point in their life.
1 in 6 people globally need these features permanently, but we all might need them temporarily.
Key takeaways
Alaina shares several slides full of info about standards, accessibility categories, reports, and the roadmap with what’s coming with the Australia and Brazil releases that are worth checking carefully.
Tools
- Text Adjust Plugin (Free Chromium extension): 4 dyslexia-friendly fonts and spacing controls.
- AI Model Accessibility Checker.
Localization framework vs Localization workspace
The Localization Framework was a bit of a pain last time I tried it (especially with HTML fields). The good news is that, apparently, the Localization Workspace is more efficient and handles things better.
Speaking of which, before the Framework even existed, I once had to translate the portal we were building into Chinese and Japanese.
The translations were perfect in the system, but the font we chose wasn’t, and it was displaying a chaotic mix of characters from both languages. Luckily, we caught it in UAT before the chaos reached production.
References
- Alaina Beaver: LinkedIn
- Text adjust extension
- AI model accessibility checker
- nullEDGE Website
- nullEDGE YouTube channel
- My LinkedIn posts #nullEDGEAdvent (any feedback is welcomed!)
- Intro to my nullEDGE advent calendar adventure
Pingback: nullEDGE advent calendar » Rubén Ferrero