Accessibility Testing Standards

Revised 6/6/2024

As required by the Illinois Information Technology Accessibility Act (PA 095-0307/30 ILCS 587) accessibility testing will be performed to confirm conformance with:

• Web Content Accessibility Guidelines (WCAG) 2.1 Level AA (https://www.w3.org/TR/WCAG21)

WCAG 2.2 and Level AAA criteria may also be tested but should be identified as such in reports.

Accessibility testing will be performed with the following tools/techniques:

• Accessibility Insights for Web (https://accessibilityinsights.io/downloads)
• Keyboard Commands (https://doit.illinois.gov/initiatives/accessibility/testing/keyboard)
• High Contrast & Zoom (https://doit.illinois.gov/initiatives/accessibility/testing/visual)
• Colour Contrast Analyser (https://doit.illinois.gov/initiatives/accessibility/guides/color)

Additional testing may be performed by trained testers using the following assistive technology tools:

• JAWS screen reader (https://www.freedomscientific.com/products/software/jaws)
• NVDA screen reader (https://www.nvaccess.org)
• ZoomText screen magnifier (https://www.freedomscientific.com/products/software/zoomtext)
• Dragon speech recognition (https://www.nuance.com/dragon/business-solutions/dragon-professional) 

If functional impact ratings are provided, the following scale will be used:

• Critical – Will prevent some users from completing essential tasks
• High – Will be very difficult or confusing to some users, but means of completing task exist
• Med – May be difficult or confusing to some users, but means of completing task exist 
• Low – Violates accessibility standards but unlikely to significantly affect users
  

Accessibility testing will include the following processes:

1. Automated Tests
2. Keyboard Tests
3. Visual Tests
4. Assistive Technology Tests
   

Automated accessibility testing is useful but has some significant limitations:

• Current testing tools are able to test fewer than 60% of accessibility criteria, so additional manual testing is necessary.
• Current testing tools are susceptible to false positives, so all findings must be confirmed through manual testing.

Because of these limitations, the State of Illinois primarly uses automated testing to (1) provide an initial overview of potential accessibility issues and (2) to identify elements that may need extended manual testing.

For automated testing, Illinois primarily uses Microsoft’s Accessibility Insights for Web, as it (and other tools based on the axe-core engine) has a low incidence of false positives and is able to test within shadow DOMs. To test with Accessibility Insights: 

1. Browse to the screen to be tested. 
2. If there are elements of the screen that are not initially displayed, such as collapsed sections or pop-up dialogs, display as many of them as possible. (If there are elements that cannot be displayed simultaneously, re-run the test in each state.)
   
3. Open Accessibility Insights and select FastPass Automated Checks.
4. Export or make note of the failed instances for confirmation with manual tests. 
5. If there are findings regarding ARIA, or any other issues that are unclear, refer them to the DoIT Office of Information Accessibility ([email protected]) for confirmation.

Note: Do not simply copy and paste failure details directly into an accessibility report. Findings must be confirmed, and, if so, clearly documented in terms that developers will understand.

Keyboard testing is performed using standard keyboard commands only – a mouse must not be used. Keyboard testing may be completed by following existing test scripts substituting keyboard commands for mouse actions. Otherwise, keyboard testing should be performed by doing the following on each page/screen:

1. Browse to the screen to be tested.
2. Explore the screen with the mouse to identify and determine the function of all interactive elements.
3. Click in the browser address bar and press enter to reload the page; then set the mouse aside.
4. If necessary, press the Tab key several times to move focus past any browser toolbars and into the page.
5. Once focus is in the page, use the following keyboard commands to move to and operate all interactive elements: 
   • Tab - Move to the next interactive element. 
     
   • Shift + Tab - Move backwards to the previous interactive element (when needed). 
   • Right or Left Arrow - Move horizontally through items in a menu bar, tab list, or grid. 
   • Up or Down Arrow - Move vertically through items in a dropdown, list box, radio button group, menu, or grid. 
   • Alt + Down Arrow - Open a dropdown. 
   • Spacebar - Check a checkbox or click a button. 
     
   • Enter - Click a link. 
   • Other - For other types of controls, such as look up and use the Keyboard Interactions in the ARIA Authoring Practices Guide (APG) (https://www.w3.org/WAI/ARIA/apg/patterns)
6. At each step, check for and document any: 
   • Interactive elements that do not receive keyboard focus. (WCAG 2.1.1)
   • Elements that do not show a visual indicator (e.g., outline) when focused. (WCAG 2.4.7)
   • Elements that do not recieve focus in a logical order (e.g., left to right, top to bottom). (WCAG 2.4.3)
   • Elements that cause unexpected changes (e.g., reload the page) when they receive focus. (WCAG 3.2.1)
   • Elements than cannot be operated using standard keyboard commands. (WCAG 2.1.1)
     
   • Elements that cause unexpected changes when values are changed. (WCAG 3.2.2)
   • Elements that trap focus (i.e., prevent focus from moving to the next element). (WCAG 2.1.2)
7. If any of the issues listed above are found, report a failure. In the report, clearly identify the element involved, which check it failed, and any steps required to reproduce the failure. 

Visual testing is performed using a combination of a Window High Contrast color theme and browser Zoom:

1. Set your display resolution or browser window to 1280 px wide.
2. Press left Alt + left Shift + PrtSc (Print Screen). If prompted to turn on High Contrast, click Yes. By default, Windows will activate a theme with a black background, white text, and blue or yellow links. (If High Contrast does not activate, check Windows Control Panel > Ease of Access Center > Make the computer easier to see, and confirm “Turn on or off High Contrast…” is checked.)
3. In the browser, open the Settings menu (Alt + F) and set Zoom to 200%.
4. Browse to the screen to be tested. 
5. If there are elements of the screen that are not initially displayed, such as collapsed sections or pop-up dialogs, display as many of them as possible.
6. Visually review all elements of the screen except logos, decorative (meaningless) images, or images of text that are duplicative of actual text provided elsewhere on the screen. Check for:
   • Text that did not increase in size by 200%. (WCAG 1.4.4)
   • Text that did not take on high-contrast colors. (WCAG 1.4.5)
   • Text that was cut off, overlapped, or otherwise became unreadable. (WCAG 1.4.4)
   • Information that was conveyed by color that is now now distinguishable by any means. (WCAG 1.4.1)
7. Press left Alt + left Shift + PrtSc to turn off High Contrast.
8. Follow the instructions in the Color Contrast Guide to measure the contrast of any color combinations except in logos, decorative images, duplicative images, or disabled elements. Check for and document:
   • Regular-sized text with a contrast ratio less than 4.5:1. (WCAG 1.4.3)
   • Large text (24px or 19px bold, or larger) with a contrast ratio less than 3:1. (WCAG 1.4.3)
   • User interface components (e.g., links, buttons, etc.) or graphics (e.g., icons, charts, etc.) with a contrast ratio less than 3:1 (WCAG 1.4.11)
9. If any of the issues listed above are found, report a failure. In the report, clearly identify the element involved, which check it failed, and any steps required to reproduce the failure. For color contrast failures, include the hexadecimal color codes of the foreground and background colors and the computed color contrast ratio. 

Assistive technology testing should only be performed by testers who have been trained to use assistive technology tools. Testers must be certain not to “cheat,” for example by using the mouse or visually reading information on the screen when testing with a screen reader. Do not test with assistive technology unless you are completely confident in your ability to use it as it would be used by someone with a disability.

Assistive technology testing should be performed after automated, keyboard, and visual testing has been completed and passed. Assistive technology testing is normally performed only on a representative sample of screens/pages. The representative sample should be selected by someone with knowledge of the scope and functions of the application and should include:

• Screens required for the most essential functions of the application, and
• Examples of each design patterns or interface component not present on the essential screens.

All findings for a given screen may be reported in a single ticket OR findings may be reported individually, including steps to reproduce, depending on complexity and requirements of the system developer/vendor.

• Screen Reader - Screen reader testing should be performed using the browser and screen reader most likely to be used by users of the system, i.e., Edge & JAWS for internal and Chrome & NVDA for public applications. For details, see Screen Reader Testing (https://doit.illinois.gov/initiatives/accessibility/testing/screen-reader)
• Screen Magnifier - Screen magnifier testing should be performed using ZoomText with magnification set to 4 x, color enhancement active, and speech disabled.
• Speech Recognition - Speech recognition should be performed using Dragon Professional and/or Windows Speech Recognition. Voice training should be completed and recognition accuracy confirmed before testing. Preference should be given to commands targeting specific elements, such as “click first name.” Mouse movement commands, including mouse grid, should be used only if specific commands do not work.