4 ms·

Cool, there is also a stackoverflow thread which is pretty interesting: http://stackoverflow.com/questions/118984/how-can-you-program-if-youre-blind http://stac

Cool, there is also a stackoverflow thread which is pretty interesting: http://stackoverflow.com/questions/118984/how-can-you-program-if-youre-blind http://stackoverflow.com/questions/118984/how-can-you-progra... What I think stinks is that companies seldom thinks of accessibility. In many cases, there are more people in need of special accessibility tools than support for lower web browsers, yet all focus is on the latter when it comes to web development. A good thing can be to follow the standard: https://www.w3.org/standards/webdesign/accessibility https://www.w3.org/standards/webdesign/accessibility

sotojuan 11y ago
I wonder what is stopping accessibility from being as popular as backwards compatibility... none of the resources I used when I started learning web development ever mentioned it (aside from alt text in the image tag). You really have to seek out information about it purposely.
- Fradow 11y ago
  There are several things that stop accessibility from being popular, here are the few I think about : - developers generally don't need it, can't easily test it, and aren't even that aware of it - "accessibility" can mean a lot of things. Are we talking about blind persons, daltonism, low visibility, limited motor skills, or something else I don't even know about? Each one has their challenge, and it's difficult to address all of them on purpose - accessibility is often regarded as "niche" by stakeholders (unless one of them requires it or you really have a big scale), and thus not important. Unlike backward compatibility, it's not easy to have accurate numbers on how many of your users require it too. That is not to say accessibility is not important. Generally, the first steps to get it right is NOT to design anything specific for them, but instead to adhere to standards, semantic HTML (or whatever your platform use if you do a native app), have enough constrast, big enough fonts, and take user-settings into account (generally it's as easy as not overriding anything like zooming and scrolling). The good thing about accessibility is if your app/website is accessible, it also benefits all your other users, in some ways.
voltagex_ 11y ago
Just remember that WCAG isn't the be-all-and-end-all [1] [1]: https://www.youtube.com/watch?v=0ijIzUUXdTM https://www.youtube.com/watch?v=0ijIzUUXdTM
diskcat 11y ago
>What I think stinks is that companies seldom thinks of accessibility. that's because there aren't as many blind people as seeing people.
- treerock 11y ago
  There aren't that many people using i.e. 9 (for example) but still, a lot of companies make effort to support it. Meanwhile there are huge numbers of people with poor eyesight or other disabilities. You'd think a business would be keen to get those customers.

sotojuan 11y ago

I wonder what is stopping accessibility from being as popular as backwards compatibility... none of the resources I used when I started learning web development ever mentioned it (aside from alt text in the image tag). You really have to seek out information about it purposely.

Fradow 11y ago
There are several things that stop accessibility from being popular, here are the few I think about : - developers generally don't need it, can't easily test it, and aren't even that aware of it - "accessibility" can mean a lot of things. Are we talking about blind persons, daltonism, low visibility, limited motor skills, or something else I don't even know about? Each one has their challenge, and it's difficult to address all of them on purpose - accessibility is often regarded as "niche" by stakeholders (unless one of them requires it or you really have a big scale), and thus not important. Unlike backward compatibility, it's not easy to have accurate numbers on how many of your users require it too. That is not to say accessibility is not important. Generally, the first steps to get it right is NOT to design anything specific for them, but instead to adhere to standards, semantic HTML (or whatever your platform use if you do a native app), have enough constrast, big enough fonts, and take user-settings into account (generally it's as easy as not overriding anything like zooming and scrolling). The good thing about accessibility is if your app/website is accessible, it also benefits all your other users, in some ways.

voltagex_ 11y ago

Just remember that WCAG isn't the be-all-and-end-all [1] [1]: https://www.youtube.com/watch?v=0ijIzUUXdTM https://www.youtube.com/watch?v=0ijIzUUXdTM

diskcat 11y ago

>What I think stinks is that companies seldom thinks of accessibility. that's because there aren't as many blind people as seeing people.

treerock 11y ago
There aren't that many people using i.e. 9 (for example) but still, a lot of companies make effort to support it. Meanwhile there are huge numbers of people with poor eyesight or other disabilities. You'd think a business would be keen to get those customers.