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

Yep when I was doing accessibility dev, that was exactly how I tested. It's pretty effective and it also gives you a feel for how crappy the tools are for the blind.


what is the learning curve like for screen readers? ...and what form does documentation come in? I'd like to learn but not sure where to get started.


You can figure out the basics in about 20-60 minutes.

If you use a Mac, just enable VoiceOver: https://www.apple.com/voiceover/info/guide/_1121.html

If you use Windows, I suggest NVDA - it's a free screen reader that's similar to the most-popular-but-expensive one (JAWS): https://www.nvaccess.org/download/

IMHO the best screen readers are on your phone / tablet. This might sound crazy (how can a touchscreen work when you can't see it?) but they're much better designed than their desktop equivalents. Mobile software tends to be simpler, resulting in a better experience:

iOS: https://www.youtube.com/watch?v=qDm7GiKra28

Android: https://support.google.com/accessibility/android/answer/6007...

If you work in web tech and take 1-2 hours to learn one of these you'll be able to dazzle others with it for the rest of your life.




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

Search: