5 ms·
Sure, but 1. JAWS and NVDA have a massive chunk of market share, and I don't run Windows 2. Screen readers work differently, so I can't guarantee that somethi
by Brendinooo 6y ago
Sure, but
1. JAWS and NVDA have a massive chunk of market share, and I don't run Windows
2. Screen readers work differently, so I can't guarantee that something that's fine in Orca does what I want elsewhere
3. Even if I have access to everything, I can't use a screen reader at the speeds that real users prefer, and I don't use them regularly enough to know what's annoying and what's not.
I'm happy to learn, just noting the challenges.
- moron4hire 6y agoYou're way overthinking the situation. It takes 15 minutes to turn on the integrated screen reader and go through the initial training. Do that and you'll cover 90% of the issues. You can grow an intuition for what works well for screen readers very quickly. And being an infrequent user is an advantage for your testing. If you can make it easy for yourself to use, than someone with more experience will find it even easier. Quit making excuses and do the bare minimum work already.
- Brendinooo 6y agoI can state with extreme confidence that it takes some people more than 15 minutes. Maybe I'm not as smart as you, or perhaps we learn differently. If it's so much easier for you, you should share your knowledge! It was a blog post that got me running the basics with Orca; I found it to be much more approachable and practical than the docs.
- objectivetruth 6y agoHow many regular screen-reading-users have confirmed that the sites you've built with your method are as good as the ones built by teams including accessibility professionals?