We are concerned about accessibility on our web site and would like to see how it is perceived and decoded by a common screen reader?
相关问题
- What is better practice use or for accessi
- Accessibility Custom Actions aren't announced
- Bug in GNOME's Java-Atk-Wrapper - how to disab
- Proper ARIA attribute for field/value pairs outsid
- How accessibility affect font sizes in iOS and And
相关文章
- Pronounce “DoIT” as “do it” for screen readers and
- Double tap doesn't click the parent view in ta
- What are the key components of web accessibility?
- Is there any callback or anything (any parameter i
- W3C document states
- Should I avoid javascript , jquery, flash, ajax, s
- is there any css validator with CSS3 and vendor sp
- Accessibility Service for my app is not working if
No. At least not one that is any good nor represents how a screen reader actually reads a page or responds to ARIA.
The best answer is to test in real screen readers, ideally by getting real users as they know how to use these tools. Consider contacting your local blind association and see if they offer testing services.
Screen Readers
Each platform has a screen reader, most are built in. Windows has the most variety.
For Windows
Use Narrator (it is built in, though not very good right now it is getting much better). Use it with Edge.
Download the free NVDA screen reader (but please donate to support it). Use it with Firefox
Download JAWS and use it in 40 minute increments for free. Use it with IE11.
For macOS
For iOS
For Android
For Ubuntu
For ChromeOS
Resources
These are handy to get started with testing on your own. Keyboard shortcuts are necessary to use a screen reader well, beyond just hitting the
Tab
key over and over and over.Basic screen reader commands for accessibility testing
Screen readers and web browsers – what’s the best pairing for testing?