Re:Top accessibility complaints from people with disabilities
by matwood on Wednesday July 05, 2017 @04:13PM
(#14705746)
> I have to strongly disagree the the implied point in your post that it requires investment of any significant time.
Totally agree. Basics like alt tags on images, wcag contrast friendly colors and semantic tags to let screen readers know this is a repeated menu, this is content, etc... take very little additional time and help so many people. Even in SPAs these items are basic.
Re:Top accessibility complaints from people with disabilities
by jasonkostempski on Thursday July 06, 2017 @07:01AM
(#14709444)
"this is content" sounds extremely useful for everyone. Curious if there is much abuse of accessibility markup to trick users into clicking ads.
Re:Top accessibility complaints from people with disabilities
by hinkley on Wednesday July 05, 2017 @02:47PM
(#14705112)
There's an argument to be made that the aria data can be leveraged by your test automation as well.
Code that a screen reader can't decipher is pretty hard for test frameworks to figure out, too.
Re:Top accessibility complaints from people with disabilities
by Justsignedup on Wednesday July 05, 2017 @04:24PM
(#14705816)
Hey, ever since we started using REMs it made scaling much easier as well. There are times when we had to work around for example bugs in Chrome with font scaling and transform under certain conditions which made chrome resize things incorrectly, but only chrome.
Its little things that take up a bunch of time. In theory we're already 80% of the way there, but the last bit is what makes the big difference.
Not doing basic accessibility on the web is just mental laziness, plain and simple. I have to strongly disagree the the implied point in your post that it requires investment of any significant time.
You can get 90% of the way to "good" just by picking appropriate font sizes and colors, doing halfway sane IA, and probably most important just using semantic markup. Adding text info to images, aria tags, etc are very minimal efforts if you simply have it in mind as you work.
None of those things require any extra time except that people need to care enough to read some documentation and watch a couple youtube videos which is a one-time up front investment of 1hr or so (not saying you are an expert after 1hr but you can definitely do "ok" with 1hr of research and learn as you go from there). a11y gets more complicated when you start doing heavy js with custom realtime interactions but even then you can get 70% of the way there with very little effort and it is a bit of a red herring because how many people are really working on fancy modern SPAs in their day jobs?