One of the benefits of making websites accessible is that you learn in the process how to actually use HTML.
Clean HTML is generally accessible HTML.
Web developers generally need to go out of their way to fuck that up and yet they still manage to do it. almost. every. single. time.
Reasons tend to range incompetence to malevolence but it’s actually not that hard and literally millions of people will be grateful for it.
Developers really should try harder at learning their craft.
John Hardy Developer 
This is kinda like those McDonalds burgers, served in Artisan buns.
The term lost any and all meaning when I ran across the the UK guy who sells his clients templated Wix Sites, but calls himself a Web Developer.
LikeLike
There’s also a tendency amongst developers to use JavaScript even when there’s a perfectly fine browser-native way to do it. Don’t fight the browser and put the convenience of the user above that of the developer seem like pretty good guiding principles.
LikeLike
John Hardy To be fair, Browser Native is a fairly relative term. What’s native in Chrome is not necessarily so in any of the others, and for some things you’ll only find support in Internot Exploder and
New Internot ExploderEdge.LikeLike
Sasch Mayer there’s still a pretty good default even in bad browsers like IE. Often it only takes familiarity on the part of the developer to see it.
Sometimes “seeing” means looking at the web from the perspective of the unsighted.
LikeLike
It was always amusing looking at the digital design projects produced by the local School of Architecture and Design, almost all produced by people that had no technical clues. The people who knew what they were doing invariably scored lower grades, despite the fact their sites were easier and faster to use (and much more navigable).
Different design priorities – looking pretty compared to being useful.
LikeLike