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 is it really more arbitrary than any other abbreviation, though? If anything the uniqueness is a long term good, like https:// ended up being
@codinghorror "Accessibility" is not a word that needs abbreviation. "Ah-eleven-why" is longer and harder to say, which is what a screen reader will do. The result is harder to read, since it requires mental translation or manual lookup. It serves only as a shibboleth and a lazy optimisation for those who hate typing and/or spelling. For such people, the correct tools have already been invented: macro expansions and continuous spell checking. My hatred of it is unbounded.
@jonathanhogg I hear you and I could raise you fifty other even more worthy examples but I humbly submit this particular h5e has left the b4n