Visa Accessibility - Test Procedures & Requirements - Test Order
VGAR Test Procedures
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
| TEST ORDER | TEST ID | TEST TOOLS | TEST FOCUS | TEST PROCEDURE |
|---|---|---|---|---|
| 1 | NAV-WEB-001-03-T | W3C Markup Validation Service | 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 | W3C Markup Validation Service | Automated Test | Run an automated validation tool against the page and confirm that it reports no errors. |
| 3 | INT-WEB-001-09-T | ANDI | Automated Test | 1) Run Accessibility Insights Fast Pass 2) Review the results of the Accessibility Insights Assessment automated checks under 'autocomplete-valid' and correct any errors detected. 3) Next, inspect the rendered DOM and confirm that any fields which have the HTML autocomplete or auto fill attribute have the correct, valid value for the specified input type. |
| 4 | PAG-WEB-001-01-T | ANDI | Valid HTML | 1. Open About the Nu HTML Checker < https://validator.w3.org/nu/about.html > in a new browser window. 2. Add these two bookmarklets to your browser bookmarks: 1. Check serialized DOM of current page: grabs the serialized DOM of whatever page you’re currently browsing and sends it to the checker 2. Check for WCAG 2.0 parsing compliance: filters checker results to just show messages relevant to requirements in the WCAG 2.1 spec (Mouse users can simply drag the corresponding links from the page to the browser bookmarks bar. Keyboard users can follow these instructions.) 3. Run the first bookmarklet in the browser tab containing your target page. It will send the page's DOM to the checker and show the results in a new browser tab. 4. Run the second bookmarklet in the browser tab containing the checker results. It will filter the results to show only WCAG parsing errors. 5. Examine the filtered results to verify that there are no errors related to: 1. Missing start or end tags 2. Duplicate attributes 3. Improper nesting of elements |
| 5 | PAG-WEB-002-01-T | ANDI | Valid HTML | 1) Run an HTML automated validation tool on the page 2) Check the page for the presence of a valid docypte declaration |
| 6 | NAV-WEB-002-02-T | Screen Reader | Keyboard Focus | Tab through the entire page and confirm that disabled elements do not receive visible keyboard focus unless the control is listed in the exceptions list |
| 7 | INT-WEB-008-01-T | Screen Reader | Moving & Blinking | 1) Perform a visual inspection of the page 2) Confirm that each page contains no content that blinks or flashes. |
| 8 | INT-WEB-007-01-T | Screen Reader | Moving & Blinking | 1) Perform a visual inspection of the page 2) 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 |
| 9 | CON-WEB-006-01-T | Screen Reader | Visual Check | 1) Review any instruction text (on-screen and screen reader only) 2) 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 | 1) Review the page and site navigation structure 2) Confirm that the site provides at least 2 of the following ways to find content (unless the page is a step in or result of a process): -Links to navigate to related Web pages -Table of Contents -Site Map -Search function -List of links to all other Web pages -Linking to all of the pages on the site from the home page Exception: Small sites (4 pages or fewer) can meet this requirement if the main navigation menu links to all other pages. |