3 ms·
Jargon isn't a problem, the problem is using jargon in places where you should be able to predict your audience isn't going to understand it. A11y and WCAG aro
by seanwilson 3y ago
Jargon isn't a problem, the problem is using jargon in places where you should be able to predict your audience isn't going to understand it.
A11y and WCAG around frontend web developers is usually fine but risky elsewhere, the same way "MVP" is fine in general HackerNews posts but not elsewhere.
Even "accessibility" is jargon and a lot of people outside of tech won't know what it means or what a screen reader is.
I don't think a11y and i18n are an attempt to be clever, they're just really long words to type correctly and take up space so they get shortened, like in Git commits and pull request discussions.