This can be done through a list, such as in the VoiceOver rotor or NVDA elements list, or by using special keys that navigate by item type.
Navigate through landmarks, links, and headings only.
The arrow keys will read line by line, reading everything on the page at your navigation pace.
Use the arrow keys to navigate through the page.
Make sure they can all be accessed and function when using the screen reader.
Use the Tab key to navigate through all the interactive items.
IMAC ACCESSIBILITY SCREEN READER READ A WEBPAGE FULL
Listen to the full page from start to finish to verify that the order of elements on the page follow a logical progression, such as left to right, top to bottom.
Then turn the screen back on and navigate the page with the screen reader key commands, verifying visually that all screen elements are accessible through the navigation. First explore and listen to the page with the monitor turned off or the screen covered to measure the page's comprehensiveness and make note of problem areas. Each web page should make sense without the visual context. When evaluating a website with a screen reader, listen for clarity and the logical order of page elements. To get started with these screen readers, including keyboard commands or touch gestures, see: While Chrome can also be used across multiple platforms and screen readers, its inconsistency makes its viability as a testing tool limited.Īt the minimum, you should test with the following combinations: For example, Firefox can be used with VoiceOver on both desktop and mobile environments, but most people who use VoiceOver use it with Safari. The screen reader and browser combinations above are widely accepted as the best and most consistent combinations, although many other combinations are possible.
Only compatible with Edge, at this date.
Most often paired with Internet Explorer 11 or Firefox.
For example, some screen readers may announce "link" before the name of the link, while others might announce "link" after the name of the link. The way content is announced may differ from screen reader to screen reader. To ensure that your website has not been created in a way that takes advantage of bugs or features of any one particular screen reader, you will need to check the site with more than one screen reader.ĭifferent screen readers behave in slightly different ways. Using a screen reader to check a web page or website can reveal many accessibility issues. It is impossible to meet the website accessibility standards in IU's Americans with Disabilities Act Policy (UA-02) using only automated tools. This is not a substitute for performing a complete Web Content Accessibility Guidelines (WCAG) 2.0 AA site evaluation, but following this full process will capture most of the WCAG 2.0 AA Guidelines more efficiently. This information is intended for web developers, providing a holistic process for performing an initial pass of evaluating your website for accessibility.