Jonathan HoggDo you know what's not accessible? Writing "a11y" in any article or documentation
I will accept it as a convenience in APIs since developers are lazy and can't spell, but fuck off with using it in text
James@jonathanhogg I wonder what the origin story is?
It feels like something someone wrote in a conference talk to crack a gag about making something over-trendy and unintentionally inaccessible.
And people used it as a joke to each other so much that the funny wore off and it accidentally got adopted.
It feels like something someone wrote in a conference talk to crack a gag about making something over-trendy and unintentionally inaccessible.
And people used it as a joke to each other so much that the funny wore off and it accidentally got adopted.
lpbkdotnet@jtruk @jonathanhogg the general form (a11y, i18n, k8s) has been around a while now.
I think i18n came first, probably because it was easier than repeatedly having the "internationalisation vs internationalization" spelling debate...
But I have seen it said that "k8s" was first because no one could remember how to spell (or pronounce) kubernetes?
Either way, I absolutely hate that this has just become how the tech industry abbreviates things.
It feels like it's on the "smug" side of clever
mirabilos@jtruk @jonathanhogg @lpbkdotnet I now just pronounce k8s as Kachtes. This is stupid.
Internationalisation and localisation have been around for far longer than this cloud bullshit, but it’s still annoying, as these terms are also often confused with each other.