I'm sure this will be the unpopular opinion but... if you're a professional you should take some minimal amount of time to learn the jargon for your industry. Software (just like every other industry) has a bunch of abbreviations like HTTP, DOM, CPU, a11y, etc. They've been around for decades, and blog posts like this won't get people to start typing out full names like Central Processing Unit or Accessibility if they believe their audience is familiar with the term. Learn the jargon once and get on with your career.
Since the parent commenter probably didn’t read the conclusion, here it is:
> [...] By being less accessible, the word a11y denotes a more technical approach to accessibility, not necessarily from those who use accessibility tools, but those who create them.
> That’s why I choose to use the word a11y here, and why I choose the hashtag #a11y on social media. And I’d recommend you do the same to avoid creating noise for people looking to improve their personal accessible experience.
Let us avoid tilting at strawpersons. The author does not claim industry professionals shouldn’t know jargon. From tfa:
So for general use, I recommend against using a11y, yet I’ve named this site with this acronym. There are a few reasons I made this decision. Firstly, WCAG 3.1.1 does permit domain-specific jargon so long as it we define it. So, take this post as a definition. Additionally, I expect most people who have found this site will have found it because they are specifically looking for something accessibility related.
Yes, to be clear, I agree with the author. But I bet the author also thinks it's an unpopular opinion, else they wouldn't feel the need to write a blog post defending their choice.
