Image description: A vibrant illustration of online shopping elements, including a shopping cart with packages, colorful items like shoes, bags, and headphones, and icons for accessibility, search, play, and audio. A prominent "Buy Now" button and various UI elements highlight the e-commerce experience.
Understanding screen readers
Reading Time: 8 minutes
For those unfamiliar with screen reader testing, adopting a different perspective can be an enlightening experience that reveals how users with vision impairments navigate digital content. Screen readers are software applications that enable people with vision impairment to use a computer by vocalizing the content on the screen or by braille output.
Screen readers for web accessibility
| Screen reader | Description |
|---|---|
| JAWS | Job Access With Speech (JAWS) is a widely used screen reader for Windows. Essential for testing web content, it works with browsers like Chrome and Firefox. To use JAWS effectively, one must learn its keyboard shortcuts, as most users do not use a mouse. Its reading commands and navigational shortcuts, such as pressing ‘H’ to jump to the next heading or ‘T’ to move to the next table, are integral to web navigation. |
| NVDA | NonVisual Desktop Access (NVDA) is a free, Windows-compatible screen reader. It’s known for its ease of use and a broad array of keyboard commands similar to JAWS, such as navigating through links, headings, and form controls using single-key shortcuts. Adjustments can be made to its settings, like voice and speed, directly from its menu. |
| VoiceOver | Apple’s VoiceOver is built into Mac and iOS devices and provides robust support for navigating through web content in Safari. It introduces unique features like the Rotor, which lets you choose the type of web page elements to navigate through with simple gestures. It’s essential to become familiar with the VoiceOver commands for effective testing. |
| TalkBack | TalkBack is the equivalent screen reader for Android devices. It features a variety of gestures and settings that allow you to explore and interact with web content using Chrome. The Local Context Menu is a key tool in TalkBack, allowing users to select navigation settings like headings or links with simple finger movements. |
| Narrator | Narrator is the built-in screen reader for Windows that has gained traction alongside browsers like Edge. With a range of commands, Narrator facilitates web navigation and content reading. Its “Scan Mode” is particularly useful for browsing content and automatically switches off when you need to interact with elements like text boxes. |
| Dolphin Screenreader | Popular in the UK and Europe, Dolphin ScreenReader for Windows offers a different set of hotkeys and boasts features tailored for both desktop and laptop keyboard layouts. It supports Chrome, Firefox, and Edge, and has an option for audible reading of web content, making navigation intuitive. |
| Orca | Orca is a comprehensive screen reader for Linux systems, including distributions like Ubuntu and Fedora. It provides robust support for navigating web content and applications through browsers such as Firefox and Chromium. Orca offers an array of keyboard commands for reading and interacting with web elements and allows for extensive customization of speech output and settings. |
Screen reader testing reveals how different tools interpret headings, links, and interactive elements, making it essential for ensuring accessibility compliance. For instance, while sighted users can skim through content visually, screen reader users rely on a linear, text-based experience. Thus, understanding the structure and semantics of web content is crucial.
While learning every screen reader might not be practical, familiarizing yourself with their basic functionalities can drastically improve web accessibility. It is recommended to test content with multiple screen readers to cover the range of user interactions and preferences.
Familiarize yourself with basic commands and accessibility features of screen readers
Each screen reader has a set of unique commands. Before you start testing, familiarize yourself with basic navigation such as moving between headings, links, and controls. This often involves learning key combinations. For example, with JAWS, you might press ‘Insert’ + ‘F7’ to pull up a list of links, while NVDA uses ‘NVDA’ key + ‘F7’ for a similar function.
| Testing task | Navigation methods |
|---|---|
| Dive into the accessibility features of your operating system |
|
| Conduct basic navigation tests |
Open a web page and use the screen reader to navigate through the content:
|
| Adjust settings for testing |
To simulate the experience more accurately, adjust the settings of the screen reader:
|
| Use developer and testing tools | Leverage built-in developer tools or extensions like WAVE, and the browser’s developer console to understand how screen readers interpret the code behind your web content. This can help you identify any structural issues that may not be immediately apparent through audio feedback alone. |
Testing with screen readers requires patience. Spend time practicing with the screen reader so you can navigate as proficiently as a regular user. Remember, screen readers are complex tools, and learning to use them effectively will take time. Once you’ve tested the content, consider seeking feedback from actual screen reader users. By incorporating screen reader testing into your QA workflows, you identify issues that automated scans alone can’t detect.
To ensure that your screen reader testing is effective and comprehensive, it’s important to consider several factors that can impact the user experience for individuals relying on this technology. Here’s a detailed guide to help you understand these considerations and incorporate them into your testing procedures.
Key considerations for testing screen readers
- Understand the user experience
- Before you begin testing, it’s crucial to understand how a screen reader interprets and presents web content. Unlike sighted users who can quickly glance at an entire webpage, screen reader users receive information in a sequential, linear manner. This means the logical order of your content and how it’s coded is critically important.
- Testing across different platforms
- Windows: JAWS and NVDA are prominent, but don’t overlook Narrator, especially as it continues to improve.
- MacOS: VoiceOver is deeply integrated and offers unique navigation features, such as the rotor.
- Linux: Orca provides robust screen reading experience on Linux, integrating with browsers and the GNOME desktop environment.
- Mobile: Don’t forget to test VoiceOver on iOS and TalkBack on Android devices, as mobile accessibility is crucial.
- Interactive elements
- Ensure that all interactive elements like forms, buttons, and links are clearly labeled and can be navigated using standard screen reader shortcuts. Testing should confirm that these elements are not only accessible but also provide feedback when interacted with, such as confirming when a form is submitted.
- Dynamic content
- Testing must also cover dynamic content such as modal dialogs, live updates, and AJAX-driven interfaces. Ensure that changes in the content are announced by the screen reader without needing to refresh the page.
- Visual dependency
- Evaluate if your site’s functionality or content is overly dependent on visual cues. Ensure that all information conveyed with color or layout is also available through text.
- Use of ARIA (Accessible rich internet applications)
- ARIA roles and properties help improve the accessibility of web content, especially dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies. Ensure proper use of ARIA labels and roles where applicable.
- Feedback and iterative testing
- Incorporate feedback from actual screen reader users. Their insights can provide valuable perspectives that automated tools and simulations might miss. Iterative testing, which involves regular reviews and updates, can help in addressing accessibility concerns more effectively.
- Documentation and training
- Maintain comprehensive documentation of your accessibility protocols and screen reader testing processes. Additionally, invest in training developers and content creators on accessibility best practices to ensure that accessibility is considered at every stage of web development.
- Legal compliance and best practices
- Lastly, ensure your website complies with legal standards like the EAA (European Accessibility Act), ADA (Americans with Disabilities Act), Section 508 of the Rehabilitation Act, and WCAG (Web Content Accessibility Guidelines). Following these guidelines not only helps in making your site accessible but also enhances the overall user experience for everyone.
Conclusion
Effective screen reader testing involves trying multiple devices, platforms, and browsers to account for real-world use cases. By understanding and implementing thorough testing protocols anyone can ensure their sites are accessible, thereby reaching a wider audience and providing a better user experience. This commitment to accessibility can significantly enhance the reputation and efficacy of your digital presence.
Read more about our European Accessibility Act Services that we offer.
EAA has been effective since June 28, 2025.
