4 ms·
It sounds like the author first says that the word "a11y" is not accessible because it's jargon, but then says that jargon is ok as long as it's defined somewhe
by TiredGuy 3y ago
It sounds like the author first says that the word "a11y" is not accessible because it's jargon, but then says that jargon is ok as long as it's defined somewhere. He then proceeds to compare the alternative word "accessibility" with "A11y" and finds they are slightly different in meaning. So it sounds like if we want to use the word "a11y", just make sure it's defined somewhere, and know that there are no exact alternatives. Is that accurate?
Personally a lot of this a11y stuff is complicated and confusing to me. I am trying my best to be a responsible dev, but it feels overwhelming sometimes.
- xcdzvyn 3y agoFurthermore he begins by saying "accessibility" is too long to use but "a11y" is too terse. But also use it anyway. I quite dislike this post because my impression is that it just boils down to "no option is adequate to me, and I'm unwilling to present an alternative".
- marcosdumay 3y ago> no option is adequate to me, and I'm unwilling to present an alternative Well, it's a blog about software accessibility...
- solardev 3y ago> Personally a lot of this a11y stuff is complicated and confusing to me. I am trying my best to be a responsible dev, but it feels overwhelming sometimes. If you just go down the checklist and do what you can, you'll be way ahead of most websites: https://webaim.org/standards/wcag/checklist https://webaim.org/standards/wcag/checklist Microsoft also has a great interactive test that can probe your website for you and highlight issues: https://accessibilityinsights.io/ https://accessibilityinsights.io/ I think similar but less powerful checks are also built into some IDEs (Jetbrains) and linters (Eslint). Edit: I am a sighted user with color vision. I can't promise these fixes are enough to make your site super accessible, but it's a lot better than nothing!