Test Procedures & Requirements

The Visa Global Accessibility Requirements (VGAR) is a combination of requirements and complimentary test procedures that help teams implement and verify accessible web experiences.

For accessibility testing, the tester simply executes the test cases and determines whether each page being tested passes or fails the test case. When a failure is found, the tester then documents the failure and provides it to the development team for remediation.  The development team subsequently references both the identified failure and the corresponding requirement to assist in the remediation effort.

Test Order    |    Requirement Order

Test Order

The following table contains the VGAR web test cases, they are ordered for the ideal test execution.

Test Order Test ID Test Tools Test Focus Test Procedure
1 NAV-WEB-001-03-T N/A Application Review Confirm that 3rd party tools, plugins, and applets are not be used in the web application unless absolutely necessary.
2 PAG-WEB-010-01-T HTML_Codesniffer Automated Test Run HTML_CodeSniffer against the page and confirm that it reports no errors.  IF THERE ARE ANY ERRORS FOUND, RETURN THE PAGE AS NOT READY TO TEST.
3 PAG-WEB-001-01-T HTML Validator Valid HTML Run an HTML validator on the page and check that no errors are present.  Ensure that the validator is executed against the fully rendered html for the page.
• i.e. Inspect the web page, select the entire <html> document, select "Edit as HTML", copy and paste the rendered html page source into the W3C validator tool along with the proper doctype/etc (as applicable).
4 PAG-WEB-002-01-T HTML Validator Valid HTML Check the page for the presence of a valid doctype declaration.
5 INT-WEB-008-01-T Visual Inspection Moving & Blinking Confirm that each page contains no content that blinks or flashes.
6 INT-WEB-007-01-T Visual Inspection Moving & Blinking Confirm that for any content that meets the following criteria, a mechanism is provided to pause, play, or hide the applicable content:
• Starts automatically
• Is presented in parallel with other content
AND
• moves, blinks or scrolls for >5 seconds
OR
• All auto-updating content regardless of the time of duration
7 INT-WEB-007-02-T Auditory Inspection Audio Control Confirm that for any audio which 1) plays automatically and 2) lasts for >3 seconds, ONE of the following is true:
• A mechanism to pause the content is presented to the user
OR
• A mechanism for adjusting the volume of the content is presented to the user AND it does not rely on the system audio levels to adjust the volume.
8 NAV-WEB-006-04-T Keyboard Keyboard Functionality Confirm that the scrollable div can be scrolled using keyboard only.
9 CON-WEB-006-01-T Visual Inspection Visual Check Confirm that Instructions and interactions never refer solely to visual cues such as size, shape, color, or spatial directions.
10 NAV-WEB-005-01-T Visual Inspection Visual Check Confirm that the site provides at least 2 of the following ways to find content:
 Links to navigate to related Web pages
• a Table of Contents
• a Site Map
• a search function
• a list of links to all other Web pages
• Linking to all of the pages on the site from the home page
11 NAV-WEB-006-01-T Visual Inspection Visual Check Confirm that components that appear on multiple pages appear in the same relative order on every page.
12 VIS-WEB-002-01-T Visual Inspection Visual Check Confirm that whenever a difference in color is used is used to convey information, that information is also available in text or through some other alternative method.
13 INT-WEB-004-07-T Visual Inspection Modal Click Click outside the modal window with the mouse and confirm that it has no effect on the modal.
14 VIS-WEB-004-01-T Visual Inspection Select Text Using the mouse, click and drag over all text on the page to select it.  HTML text will be selectable.  Text that is part of an image will show the entire image being highlighted.  Confirm that text is presented using  text rather than in an image of text, except for logos and within pictures where it cannot be avoided (e.g., graphs or screenshots).  
15 VIS-WEB-001-01-T Visual Inspection Zoom Text Using the browser's built in functionality, set the browser to a width of 1280px and then increase the zoom level to 200% and confirm that the zoomed layout has no text clipping, truncating, or being obscured.
16 VIS-WEB-006-01-T Visual Inspection Audio Visual Confirm that all video content (live AND prerecorded) provides accurate captions via an accessible mechanism.
17 VIS-WEB-006-02-T Visual Inspection Audio Visual Confirm that any video content that provides information visually that is not described by the default audio track provides that information via an Audio Description track that fully explains the visual information.  
18 VIS-WEB-006-03-T Visual Inspection Audio Visual Confirm that If an Audio Description track cannot fully explain the visual information during gaps in dialog on the default video, Extended Audio Description is used, where the video is paused at appropriate times to allow for the descriptions to finish.
19 VIS-WEB-006-04-T Visual Inspection Audio Visual Captions and Audio Description MUST be made available to users via one or more of the following methods (both need not use the same method):
• always on, included in the original video (open captions)
• included as a separate file or track that can be toggled on and off by the user via an accessible mechanism (closed captions) note: use of Extended Audio Description may complicate this
• included as a video file and made available via separate link(s) adjacent to the original video link
20 VIS-WEB-006-05-T Visual Inspection Audio Visual A transcript which provides the same information as presented in the original media content MUST be made available for all audio-only AND/OR video-only content.
21 INT-WEB-009-01-T Visual Inspection Timeout Confirm that users are warned prior to when a session times out and expires.
22 INT-WEB-009-02-T Visual Inspection Timeout Confirm that users are given at least 30 seconds to take action in order to avoid a session time out by extending the time limit (of a session) via a “simple” user action (e.g., "press the space bar").
23 CON-WEB-002-01-T Firebug > Inspect Element Firebug Whenever content conveys information through presentation of text, appropriate semantic markup confirm that the proper semantic markup is being used (e.g., em, strong, cite, blockquote, sub, and sup).
24 CON-WEB-004-01-T Firebug > Inspect Element Firebug If a page contains paragraphs visually, pull up the source code and confirm that those paragraphs are marked up properly (i.e., with <p>).
25 INT-WEB-001-04-T Jim Thatcher > Form Labels Labels Run the Jim Thatcher Form Label favelet and confirm that there are no errors.  Common errors are "No For", "No Match", and "2 Labels"
26 CON-WEB-008-01-T Jim Thatcher > Tables Tables Run the Jim Thatcher Table Favelet and review the tables on the page, confirming that no tables are used for layout purposes.
27 CON-WEB-008-02-T Jim Thatcher > Tables Tables Run the Jim Thatcher Table Favelet and review the tables on the page, Confirm that THs are used as appropriate and every TH has scope as appropriate.  If present, confirm that headers point to the correct TH's IDs.
28 CON-WEB-003-01-T WAVE > Disable Styles Content Order Disable styles, linearizing the page and confirm that the logical order of content is present in the code order.
29 CON-WEB-003-02-T WAVE > Disable Styles Content Order Disable styles and confirm that "hidden" content being "parked" for later use/display is located at the bottom of the document.
30 CON-WEB-001-03-T NC State Web Eval > Headings & ARIA Content Order Run the NC State Web Evaluation Bookmarklet and check the Headings and ARIA Landmarks checkboxes.  Confirm that the H1 is within and at the top of the Main ARIA Landmark, with no content above it.
31 VIS-WEB-003-01-T WCAG Contrast Checker Contrast Confirm that all color contrast ratios of text, informational images, and images of text to their backgrounds must be at least 4.5:1, except if the text is 18 point or 14 point bold or larger, where a ratio of 3:1 is then required.

Note: All of this information will be provided in the WCAG Contrast Checker side panel, except for text that is not HTML text or an HTML colored background (e.g., text over a gradient image). In this case, use the color picker tool at the bottom of the panel to pick samples and determine if the text fails in any places.
32 VIS-WEB-003-02-T WCAG Contrast Checker Contrast If all site colors cannot meet VIS-WEB-003-01 (which is preferred), contrast requirements can be met by providing an alternate (high-contrast) style sheet and an accessible method of activating it.
33 VIS-WEB-005-01-T Web Dev Toolbar > Images Images On the Web Developer Toolbar, choose
• Images > Hide Background Images
• Images > Outline Images > Outline All Images
• Images > Display Alt Attributes
Confirm that all non-text content provides text alternatives that provide equivalent information, context, and purpose to the user.
Note: given the variety of possible situations, testers may need to investigate further than the above steps allow (e.g. using Firebug).
34 VIS-WEB-005-02-T Web Dev Toolbar > Images Images Confirm that all non-text content that is decorative, provides no contextual value, or is already defined by surrounding text is hidden from the user using the following techniques (as applicable):
• For <img>, provide alt="" (alt null)
• For role="img", aria-hidden="true"
35 NAV-WEB-003-03-T Juicy Studio > ARIA > Document Landmarks Landmarks Verify that all rendered content is within one or more (through nesting regions) of the following landmark regions, as appropriate: Main, Navigation, Banner, Contentinfo, Complementary, Search
36 NAV-WEB-007-01-T Juicy Studio > ARIA > Document Landmarks Landmarks Confirm that any pagination controls on the screen have role="navigation"
37 CON-WEB-001-01-T Headings Map Headings Confirm that each page organizes content using headings (e.g., H1, H2, etc.).
38 CON-WEB-001-02-T Headings Map Headings Confirm that each page has only one H1.
39 CON-WEB-001-04-T Headings Map Headings Headings MUST occur in a sequential and increasing order (i.e., Heading 1, then Heading 2, then Heading 3 and so on, no skipping numbers).
40 CON-WEB-001-05-T Headings Map Headings Confirm that headings are nested properly (i.e., 2 is always a child of 1, and 3 is always a child of 2, and so on)
41 NAV-WEB-003-07-T Headings Map Headings Confirm that if HTML5 sections are used within the "Main" ARIA Landmark role they do not interfere with a properly nested heading structure.
42 INT-WEB-001-06-T Headings Map Headings If more than one distinct group of related form controls is present and fieldsets are not used to group the controls, confirm that the controls are grouped using headings.
43 PAG-WEB-003-01-T FAE > Navigation > Title Page Title Verify that the page title is accurate and descriptive of the purpose of the page and content.
44 PAG-WEB-003-02-T FAE > Navigation > Title Page Title Verify that the page title is unique and conforms to a consistent structure among the other pages.
45 NAV-WEB-008-02-T FAE > Navigation > Title Page Title Confirm that any Process or Wizard Step Indicator information if present MUST be included in the page title and H1.
46 CON-WEB-009-01-T FAE > Navigation > Title Page Title Confirm that the following are consistent on each page:
• Page title
• Current Navigation menu item
• Progress Indicator / Wizard Step (if present)
• Top-level heading (H1)
• referring link (if present)
47 PAG-WEB-004-01-T FAE > Navigation > Language Changes Language Confirm that the correct language is set on the page’s <html> element.  E.g. <html lang="en">
48 CON-WEB-007-01-T FAE > Navigation > Language Changes Language Confirm that a lang attribute is set on every word or phrase that is in a different language than the page’s main language.
49 NAV-WEB-004-01-T FAE > Navigation > Access Keys Access Keys Confirm that no access keys are used on the page.
50 NAV-WEB-006-03-T FAE > Navigation > Links Links Bring up the list of links with the Firefox Accessibility Extension (which also shows the HREF of links, unlike the JAWS links list) and sort by link text or HREF.  Confirm that Links with the same HREF have the same link text and vice versa, and links with different HREFs have different link text and vice versa.
51 CON-WEB-004-02-T FAE > Style > Lists Lists Confirm that groups of items (e.g., a navigation menu or group of tabs) on the page are marked up as lists.
52 PAG-WEB-005-01-T FAE > Navigation > Frames Screen Reader Iframes Confirm that iframes are only used when no reasonable alternative exists.
53 NAV-WEB-003-05-T Keyboard Skip Links If the page has a "login" feature available and focus is not automatically placed in the login control, Hit Tab after the page loads.  Confirm that the first link on the page is "skip to login" - it may be visibly hidden until it receives focus.
54 NAV-WEB-003-06-T Keyboard Skip Links Hit Tab after the page loads.  Confirm that the first or second link on the page is "skip to content" - it may be visibly hidden until it receives focus.
55 NAV-WEB-001-04-T Keyboard Keyboard Focus Run through all use cases using keyboard only (i.e., without a mouse), confirm that no UI elements take control of keyboard focus unless they also return focus.
56 NAV-WEB-002-01-T Keyboard Keyboard Focus Tab through the entire page and confirm that the keyboard focus indicator is always clearly visible.
57 NAV-WEB-002-02-T Keyboard Keyboard Focus Tab through the entire page and confirm that disabled elements do not receive visible keyboard focus.
58 NAV-WEB-002-03-T Keyboard Keyboard Focus Tab through the entire page and confirm that the tab order matches the logical order of the content.
59 NAV-WEB-001-02-T Keyboard Keyboard Functionality Run through all use cases using the keyboard only (i.e., without a mouse), confirm that any "mouseover" events are available to the keyboard when the keyboard focus is placed on the element.
60 NAV-WEB-001-01-T Keyboard Keyboard Functionality Run through all use cases using keyboard only (i.e., without a mouse), confirming that all features and functionality are fully available to users.
61 INT-WEB-002-01-T Keyboard Keyboard Functionality Confirm that if a page accepts user input it also checks for errors and allows the user to correct them.
62 INT-WEB-002-02-T Keyboard Keyboard Functionality Confirm that If user input is collected across multiple pages in order to execute a transaction of some kind, the user is presented with a summary of the input before submitting.
63 INT-WEB-002-04-T Keyboard Keyboard Functionality Fill out all client-side validated form controls with invalid data, confirm that when an error is detected using client side validation, the visual UI highlights the field (e.g., with a red border) and places error helper text near it.
64 NAV-WEB-001-06-T Keyboard JS Events Confirm that changes of context are never initiated on focus.
65 INT-WEB-003-02-T Keyboard JS Events Confirm that system and success messages are only presented to users after a button press or on page load.
66 INT-WEB-005-01-T Keyboard JS Events Interact with each form control and confirm that no actions take place onchange or onfocus.
67 INT-WEB-005-02-T Keyboard JS Events Interact with each form control and confirm that no actions take place onblur (rather they require a go button) unless this is absolutely necessary.
68 NAV-WEB-001-05-T Keyboard JS Events Confirm that Onblur is used instead of onchange unless it cannot be avoided and care has been taken to ensure that it has no negative consequences for keyboard only or screen reader users. 
69 NAV-WEB-001-07-T Keyboard JS Events Confirm that screen changes caused by onblur and onchange events are minor, and if not that the user is informed of the change of context ahead of time with text onscreen (not visually hidden).
70 INT-WEB-004-05-T Keyboard Keyboard Modal Confirm that when a modal window pops up, focus is set to the appropriate content. If the modal is primarily presenting text (including links), confirm that focus is placed on the heading or beginning of the text content. If the modal's goal is using interactive elements (i.e. form, button, etc.), confirm that focus is placed on the first interactive element inside the modal, excluding any close button(s).
71 INT-WEB-004-06-T Keyboard Keyboard Modal Tab through the each modal window and confirm that the user can move through the modal's focusable elements, “wrapping around” from bottom-to-top and top-to-bottom using the <TAB> and <SHIFT>+<TAB> keyboard events.
72 INT-WEB-004-08-T Keyboard Keyboard Modal Hit <ENTER> in a modal and confirm that this keystroke trigger's the modal's main call-to-action (e.g. Submit form, etc.).
73 INT-WEB-004-09-T Keyboard Keyboard Modal Hit <ESC> and confirm that the modal closes.
74 INT-WEB-004-10-T Keyboard Keyboard Modal After hitting <esc> to close the modal, confirm that focus is restored to the triggering element on the page.
75 VIS-WEB-001-02-T Visual Inspection Zoom Text Using the browser's built in functionality, set the browser to a width of 1280px and then increase the zoom level to 200% and confirm that all interactive content is fully usable at the increased zoom level.
76 VIS-WEB-001-03-T Visual Inspection Zoom Text Using the browser's built in functionality, set the browser to a width of 1280px and then increase the zoom level to 200% and confirm that when an action is initiated that results in changed content 1) a clear visual cue is provided within the currently viewed area indicating a change has occurred outside of currently viewed area OR 2) the resulting change can be observed within the current view.
77 PAG-WEB-009-04-T Screen Reader Screen Reader Page Title 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. 
78 PAG-WEB-009-07-T Screen Reader > Landmarks Screen Reader Landmarks 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.
79 NAV-WEB-003-01-T Screen Reader > Landmarks Screen Reader Landmarks Bring up the list of Landmark roles and confirm that each page has (at a minimum) one of each of the following ARIA landmark regions: 1) Banner, 2) Navigation, 3) Main, and 4) Contentinfo Landmark role.
80 NAV-WEB-003-02-T Screen Reader > Landmarks Screen Reader Landmarks Bring up the list of Landmark roles and confirm that when "aside" or search content is present on the page, the page includes the following ARIA landmark regions as needed: Complementary, Search
81 PAG-WEB-009-08-T Screen Reader > Landmarks Screen Reader Landmarks 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.
82 NAV-WEB-003-04-T Screen Reader > Landmarks Screen Reader Landmarks Bring up the list of Landmark roles and confirm that if the page has multiple landmarks of the same type (e.g., Main Nav and Sub Nav), those regions MUST be labeled so they can be differentiated by the user.
83 NAV-WEB-007-02-T Screen Reader > Landmarks Screen Reader Landmarks Cycle through each landmark role with each supported screen reader and confirm that any pagination controls have the word "Pagination" included in their aria-label.
84 PAG-WEB-009-09-T Screen Reader > Headings Screen Reader Headings 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.
85 PAG-WEB-005-02-T Screen Reader > iframes Screen Reader Iframes Bring up the list of iframes (or cycle through each if a list is not available) and confirm that each iframe designed for user interaction has a unique, descriptive, and consistent title.
86 PAG-WEB-009-05-T Screen Reader > Iframes Screen Reader Iframes Bring up the list of frames (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. 
87 PAG-WEB-005-03-T Screen Reader > iframes Screen Reader Iframes Bring up the list of iframes (or cycle through each if a list is not available) and confirm that each Frame designed for “system use” are not in the list. Confirm that iframes that users SHOULD not interact with are hidden from all users by:
• Set CSS style to display:none
• Set aria-hidden attribute to true for the iframe
88 PAG-WEB-009-06-T Screen Reader > Iframes Screen Reader Iframes 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.
89 CON-WEB-005-01-T Screen Reader > Links Screen Reader Links Bring up the list of links with each supported screen reader if available and confirm that all link text describes the destination or purpose of every link in a way that makes the destination or purpose clear to all users when taken out of context (i.e., in a list of links for the page).  Some of the link text may be hidden via CSS provided the text left visible makes sense when taken in context of the enclosing sentence, table header(s) or preceding heading.
90 PAG-WEB-009-10-T Screen Reader > Links Screen Reader Links 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.
91 INT-WEB-006-02-T Screen Reader > Links Screen Reader Links Bring up the list of links with each supported screen reader if available and confirm link text is unique and descriptive.
92 INT-WEB-006-03-T Screen Reader > Links Screen Reader Links Bring up the list of links with each supported screen reader if available and confirm no links HREF points to "javascript:void(0);" nor "#"
93 CON-WEB-008-03-T Screen Reader > Tables Screen Reader Tables Bring up the list of tables (or cycle through each if a list is not available) with each supported screen reader and confirm that each table is identified.
94 CON-WEB-008-04-T Screen Reader > Tables Screen Reader Tables Bring up the list of tables (or cycle through each if a list is not available) with each supported screen reader and confirm that each table with more than 4 THs has its layout/functionality described after the "title"
95 CON-WEB-008-05-T Screen Reader > Tables Screen Reader Tables - Sorting Use a screen reader to access any table sorting functionality on the page. Confirm that sorting state is announced to the screen reader and that all sorting controls are keyboard accessible. 
96 PAG-WEB-006-01-T Screen Reader Screen Reader Custom Controls Interact with each custom control using a screen reader.  Confirm that each custom control's name reads properly.  
97 PAG-WEB-006-02-T Screen Reader Screen Reader Custom Controls Interact with each custom control using a screen reader.  Confirm that each control properly emulates the native control, announcing appropriate name, role, state, values, and properties.
98 PAG-WEB-006-03-T Screen Reader Screen Reader Custom Controls Interact with each custom control or element using a screen reader.  Confirm that interaction is possible using the expected native keyboard commands or that clear instructions are provided to the user before the element.
99 PAG-WEB-006-04-T Screen Reader Screen Reader Custom Controls Interact with all expanding and collapsing controls and elements using a screen reader. Confirm that the current state of each expanding/collapsing control is read when the element receives focus and when any user action is taken on the element. For instance, tabbing to an expanding navigation item SHOULD read the element name and the current state (e.g. Expanded or Collapsed). When ENTER is pressed on the element the new state SHOULD be read.
100 NAV-WEB-008-01-T Screen Reader Screen Reader Forms Read any process or Wizard Step Indicators with each supported screen reader and confirm that each provides context and status to screen readers (e.g., "Current Step: Add Card, Step 2 of 4").
101 INT-WEB-001-01-T Screen Reader Screen Reader Forms Tab through each control on the page and confirm that each form control has a unique label attribute that fully describes the control’s purpose, including any supplementary information that the visual presentation may also provide.
102 INT-WEB-001-02-T Screen Reader Screen Reader Forms Tab through each control on the page and confirm that each form control label reads out properly.
103 INT-WEB-001-05-T Screen Reader Screen Reader Forms If fieldsets are used on the page to group more than one distinct group of related form controls, confirm that the legends read properly, i.e., before each label for the controls in the given fieldset.
104 INT-WEB-001-08-T Screen Reader Screen Reader Forms Tab through each control on the page and confirm that helper text is read after the label for each form control that has helper text.
105 INT-WEB-002-05-T Screen Reader Screen Reader Forms Fill out all client-side validated form controls with invalid data and confirm that onblur, the screen reader interrupts the user with an audible alert reading the contents of the error helper text.
106 INT-WEB-001-07-T Screen Reader Screen Reader Forms Tab through each control on the page and confirm that each required form control is announced as such by each supported screen reader.
107 INT-WEB-002-06-T Screen Reader Screen Reader Forms Fill out all client-side validated form controls with invalid data, return to the top of the form, and tab through all invalid form controls with each screen reader and confirm that onfocus, invalid form controls are announced as such and that the text of the error helper text is read aloud.
108 INT-WEB-002-03-T Screen Reader Screen Reader Forms Tab through each control on the page and confirm that no form controls announce as invalid if they are not invalid.
109 INT-WEB-002-07-T Screen Reader Screen Reader Forms Submit a form with errors and confirm that a list of errors is placed in an alert box directly below the H1, that the contents of the alert box are read aloud to the user on page load, and that focus is automatically set on the first invalid form control.
110 INT-WEB-006-01-T Screen Reader Screen Reader Forms Confirm that all elements that look like and behave like a button (causing an action) are described as buttons by all supported screen readers. Confirm that all elements that look like and behave like a link are described as links by all supported screen readers.
111 INT-WEB-005-03-T Screen Reader Screen Reader Forms Interact with each form control that uses an onblur event to cause a “significant” change to a page, the page visually describes what will happen via a textual description to the user prior the control being triggered, and that description is also read to the user after the label, onfocus.
112 PAG-WEB-009-03-T Screen Reader Screen Reader Alerts 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.
113 PAG-WEB-009-02-T Screen Reader Screen Reader Alerts 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. 
114 INT-WEB-003-01-T Screen Reader Screen Reader Alerts Confirm that the contents of system and success messages are read aloud to the user when they appear.
115 NAV-WEB-006-02-T Screen Reader Screen Reader Labels Confirm that content with the same functionality has consistent labels, names, and text alternatives.
116 INT-WEB-001-03-T Screen Reader Screen Reader Labels Confirm that when visual presentation provides context not provided in a label, that the necessary context is read aloud by the screen reader along with the visible label.
117 CON-WEB-006-02-T Screen Reader Screen Reader Labels Confirm that text labels and/or names are used when providing instructions to allow users who cannot perceive other indicators to locate elements.
118 INT-WEB-004-01-T Screen Reader Screen Reader Modals Confirm that when a modal window pops up, it is described to the user as such.
119 INT-WEB-004-02-T Screen Reader Screen Reader Modals Confirm that when a modal window pops up, the modal's main heading or title is read aloud to the user.
120 INT-WEB-004-03-T Screen Reader Screen Reader Modals Confirm that when a modal window pops up, any helpful information that is above the first focusable element is read aloud after the modal's main heading or title.
121 INT-WEB-004-04-T Screen Reader Screen Reader Modals Confirm that focus is trapped inside all modal windows by cycling through headings, landmark roles, and links with each supported screen reader and confirming that focus stays within the modal and doesn't move the screen behind.
122 PAG-WEB-008-01-T Screen Reader Screen Reader Hidden Content Run through the page with a screen reader, confirm that content included for screen readers but to be hidden visually (e.g., hidden Headings to provide content structure that is visually implied) is reading for screen readers but not onscreen.
123 PAG-WEB-008-02-T Screen Reader Screen Reader Hidden Content Run through the page with a screen reader, confirm that content that SHOULD be hidden from screen readers (but not sighted users) is shown on screen but not showing up for screen readers.
124 PAG-WEB-008-03-T Screen Reader Screen Reader Hidden Content Run through the page with a screen reader, confirm that content that SHOULD be hidden from all users is neither available onscreen or to a screen reader.
125 PAG-WEB-009-01-T Screen Reader Screen Reader Features Run through all use cases with each supported screen reader, confirming that all features and functionality are fully available to non-sighted users.

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.