Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This. I have a strong suspicion that the web was inherently more accessible 10 years ago when it was written in -- you know -- HTML. But now it's not written in HTML as much as in Javascript frameworks, most of which are necessary only to add "flash" (no pun intended) to modern websites but which also hinder accessibility.

Web developers need to decide if their job is to impress or to inform. Usually users want to be informed, while the VP of marketing (your client) wants to be impressed. The two goals do not have to be in conflict with each other but the blind use of frameworks and client-side rendering often puts them in conflict.



Component frameworks can choose to have deep support for the ARIA accessibility tags e.g. Dojo had it in 2007 - https://dojotoolkit.org/reference-guide/1.10/dijit/a11y/stat...

Using a framework that is designed for accessibility should be better than using plain HTML that is not designed for a11y.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: