Screen Readers (PAG-WEB-009)

Support Screen Readers

The general rule for supporting screen readers is that all features and functionality of the site or web application MUST be supported with at least one screen reader.

When a user accesses a page with a screen reader, the user typically examines the content for the page title, landmark regions, headings, links, and iframes if present.

When a screen reader user is looking for specific elements a list of the desired elements is opened. For instance, to a find a specific heading, a list of headings is opened and the user selects the desired heading from the list.

In order to fully support screen readers, all aspects of the page that are available to sighted users must be available to screen reader users.

Recommended Screen reader/Browser Combinations

  • JAWS and/or WindowEyes with Internet Explorer
  • NVDA with Firefox
  • VoiceOver with Safari

Requirements

Support Screen Readers (PAG-WEB-009-01)

All features and functionality made available to users within the web application MUST be functionally supported with at least one screen reader per supported platform (i.e. JAWS for Windows desktop, VoiceOver for iOS, etc.).

Alerts Read (PAG-WEB-009-02)

When alerts are shown on screen (i.e., success, error, or status/informative) they MUST also be read aloud by each supported screen reader.

<div role="alert" aria-hidden="false" style="display:block; visibility:
visible">Warning: form is incomplete</div>
		

Screen Updates Read (PAG-WEB-009-03)

When the user takes an action resulting in a visual change to the screen above the focus (e.g., user entered a Visa card number and the Visa logo above the input highlights onblur), each supported screen reader MUST inform the user of this change.

Page Title Reads (PAG-WEB-009-04)

The page title MUST be properly read aloud by each supported screen reader on page load or when the URI changes on Single Page Architecture web applications.

IFrames List Reads (PAG-WEB-009-05)

When the list of iframes is requested by the user (or the user attempts to cycle through each), each supported screen reader MUST accurately identify all Frames designed for user interaction by reading their titles.

No System IFrames Read (PAG-WEB-009-06)

When the list of iframes is requested by the user (or the user attempts to cycle through each), each supported screen reader MUST NOT list any iframes designed for “system use”.

Landmarks List Reads (PAG-WEB-009-07)

When the list of Landmarks is requested by the user (or the user attempts to cycle through each), each supported screen reader MUST accurately identify all Landmark regions by role.

Multi Landmark Labels Read (PAG-WEB-009-08)

When the list of Landmarks is requested by the user (or the user attempts to cycle through each), and there are multiple navigation landmarks on the screen, each supported screen reader MUST accurately identify each uniquely by reading both the role and label.

Headings List Reads (PAG-WEB-009-09)

When the list of headings is requested by the user (or the user attempts to cycle through each), the headings MUST be read accurately by each supported screen reader.

Links List Reads (PAG-WEB-009-10)

When the list of links is requested by the user, link text MUST be present and read accurately for each link by each supported screen reader.


Test Procedures

Screen Reader (PAG-WEB-009-01-T)

Run through all use cases with each supported screen reader, confirming that all features and functionality are fully available to non-sighted users.

Screen Reader (PAG-WEB-009-02-T)

Confirm that when alerts are shown on screen (i.e., success, error, or status/informative) they are also read aloud by each supported screen reader.

Screen Reader (PAG-WEB-009-03-T)

When the user takes an action resulting in a visual change to the screen above the focus (e.g., user entered a Visa card number and the Visa logo above the input highlights onblur), each supported screen reader announces the change to the user.

Screen Reader (PAG-WEB-009-04-T)

Confirm that the "page" title is read aloud by each supported screen reader on page load or when the URI changes on Single Page Architecture web applications.

Screen Reader > IFrames (PAG-WEB-009-05-T)

Bring up the list of iframes (or cycle through each if a list is not available) with each supported screen reader and confirm that all iframes designed for user interaction have their titles read aloud.

Screen Reader > IFrames (PAG-WEB-009-06-T)

Bring up the list of iframes (or cycle through each if a list is not available) with each supported screen reader and confirm that iframes designed for "system use" are not read aloud.

Screen Reader > Landmarks (PAG-WEB-009-07-T)

Bring up the list of Landmark roles (or cycle through each if a list is not available) with each supported screen reader and confirm that all Landmark regions are accurately identified.

Screen Reader > Landmarks (PAG-WEB-009-08-T)

If there are multiple navigation landmarks on the screen, cycle through each with each supported screen reader and confirm that each is uniquely identified by the screen reader reading both the role and label.

Screen Reader > Headings (PAG-WEB-009-09-T)

Bring up the list of headings (or cycle through each if a list is not available) with each supported screen reader and confirm that all headings are accurately read.

Screen Reader > Links (PAG-WEB-009-10-T)

Bring up the list of links with each supported screen reader if available and confirm link text is present and read accurately for each link.


Related Content

WCAG Success Criteria

W3C Techniques

Common Failures

These materials and steps outlined on this website are provided “AS IS” and are intended for illustrative purposes only. They should not be relied upon for marketing, legal, tax, financial, regulatory or other advice. You are responsible for the legal aspects of any implementation of the concepts illustrated herein. Further, Visa neither makes any warranty or representation as to the completeness or accuracy of this information, nor assumes any liability or responsibility that may result from reliance on such information.  You should not act or rely on such content without seeking the advice of a professional.  All brand names, logos and/or trademarks are the property of their respective owners, are used for identification purposes only, and do not necessarily imply product endorsement or affiliation with Visa.