While on the surface this is true, the amount of work required as a developer to learn how to do this is insignificant compared to the total time required to really understand your craft. While you may have to spend more time testing accessibility if you want to use the latest features in the bleeding-edge versions of JavaScript and CSS (or whatever language you're using which compiles down to them) or WebAssembly, you'll probably spend more time on browser compatibility testing, too, with those technologies (or you'll take the IDGAF approach).When you really dig into it, though, most of the accessibility issues for the UI of a web application are still among the things you have to know to present accessible content on a website. In either case, the important point is to know when you're pushing the boundaries so you can make an informed decision about your testing requirements. It's just another metric to consider, like browser compatibility or mobile presentation.
No comments yet.