Do 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
Do 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
@jonathanhogg love to be able to read stuff and understand it on the first go without needing to look up information.
No wonder agentic coding is so popular...
@themediumkahuna Oh, does it not? Even knowing it references accessibility, I still assumed it was to be read as "ally."
I hereby declare its use even dumber than I thought.
@CatherineFlick @jonathanhogg
@gnate @themediumkahuna @CatherineFlick @jonathanhogg
On the stenotype, it's spelled like "SEBLT" and it's actually super fun to type for some reason, but that might be because I am easily amused.
@mirabilos Individually pronouncing each letter is what I imagined. X.S.A.B.L.T.
But then, having an abbreviation that survives translation is a beast of a problem!
@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
@jonathanhogg @lpbkdotnet @jtruk But it helps sometimes: try to go a interoperability meeting and you'll see why saying "i14y" is much more pratical.
Whatever the case, in my texts I always put an abbreviation with the expanded term right in the beginning. If it's seldom used, I only write the expanded form.
@jonathanhogg @andrewt But that's normal. Every group will develop their own language and conduct, opaque to outsiders.
Just like a group of friends will develop their own stories and contexts.
It's only a bad thing when the discussion is meant to welcome outsiders.
@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.
A8y! I c8y a3e!
"But it looks like ally, it's great"
Fuck you Jean-Eude. People should not do gatekeeping for something that important.
@jonathanhogg someone wrote a brilliant post about that:
A11y is about the least accessible way of writing 'accessibility' possible. A-11-letters-Y is not enough information to go on unless you've already been primed to understand it. It's aesthetically (a11y) ugly, astonishingly (a11y) pretentious, and has just this awful whiff of artificiality (a11y) about it. In an age where machines will automatically (a11y) type entire words out for you using the shorthand is aggravatingly (a11y) lazy and unintuitive. Quite frankly it strains acceptability (a11y). I don't think that this numeronym is being used appropriately (a11y).
@jonathanhogg at the very minimum, you'd want to do this before publishing:
sed -e 's/a11y/accessibility/g' mydocument
Yes, i will explain this if anyone doesn't speak Linux.
@jonathanhogg Wait, why am i just learning of this... who's idea was it to have accessibility abbreviated in a way screen readers won't be able to read?
That is worse than the word lisp. What the actual fuck?
You caused me to finally research what that "a11y" was about.
Leetspeak number sub for "ally? No.
"aleventy"? "aelevy"? Any other spoken number variation bookended with an a and y? No.
Finally... wow, counting letters is beyond stupid. It's not even a good counter-example joke. 🤷
I can't see using it under the covers either. Too dumb.