Hacker News new | past | comments | ask | show | jobs | submit login

Web accessibility describes specific requirements for people with disabilities to be able to use your website. If you don't implement these features, blind people, colorblind people, people who can't use a mouse, etc., won't be able to use your website. You can make a strategic choice not to support these users for reasons like ROI. But obviously there are plenty of situations where either we make the affirmative choice not to exclude people with disabilities, or we're required by law to accommodate them. In my personal opinion, we should always build on the web with the modern features that support assistive technologies, and that building inaccessible web experiences is synonymous with building poor quality web experiences. Many of the (mostly native) features that enable an experience accessible to people with disabilities improve the experience for all users.



>we should always build on the web with the modern features that support assistive technologies

Or build on the old web without modern features, that supports assistive technologies by default [1] :).

[1] https://motherfuckingwebsite.com/




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: