Accessibility Check List
The five major categories of official disabilities are:
| Type | Description |
|---|---|
| Visual | Includes blind, low-vision and color blind |
| Hearing | Includes deaf and hard of hearing |
| Motor | Includes people who have issues with touch elements |
| Speech | Includes people who are not able to speak |
| Cognitive | Includes dyslexia, ADD and epilepsy |
The following accessibility items will be checked during the UX/UI Certification gate. Any issues found on this list may result in possible Critical or High Severity issues requiring fixes before an application can pass the gate. As a reminder, branding and usability issues are also checked in the UX/UI Certification gate. Therefore, having no issues from the list below does not guarantee passing the UX/UI Certification gate.
Download version 1.3 of the UX/UI Brand Gate Checklist
- Is color alone used to convey important information?
- Check: View page in grey-scale. Can you still understand all the information and use all the functionality?
- Primarily Benefits: Color Blind
- Requirement: WCAG2.0 SC 1.4.1
- Does the font size meet minimum requirements? (min. 13pt)
- Check: Review non-legal font size to ensure it is set to or greater than the minimum 13pt equivalent for resolution size. Legal font may be minimum 9pt.
- Primarily Benefits: Low-vision
- Requirement: KP Policy
- Is the color contrast of active text readable by people with low-vision? (min. 4.5 : 1)
- Check: Snook Color Contrast Checker does not throw any issues related to color contrast
- Primarily Benefits: Low-vision
- Requirement: WCAG2.0 SC 1.4.3
- Is the color contrast of disabled/inactive text readable by people with low-vision? (min. 2 : 1)
- Check: Snook Color Contrast Checker does not throw any issues related to color contrast
- Primarily Benefits: Low-vision
- Requirement: KP Policy
- Is the color contrast of enabled/active icons readable by people with low-vision? (min. 4.5 : 1)
- Check: Snook Color Contrast Checker does not throw any issues related to color contrast
- Primarily Benefits: Low-vision
- Requirement: KP Policy
- Is the color contrast of disabled/inactive icons readable by people with low-vision? (min. 2 : 1)
- Check: Snook Color Contrast Checker does not throw any issues related to color contrast
- Primarily Benefits: Low-vision
- Requirement: KP Policy
- Is the color contrast of images readable by people with low-vision? (min. 4.5 : 1)
- Check: Snook Color Contrast Checker does not throw any issues related to color contrast
- Primarily Benefits: Low-vision
- Requirement: KP Policy
- If animated content is present, is there an alternate way to view the content?
- Check: Review screen with screen reader can you still get the same meaning from the screen when you cannot see the animation?
- Primarily Benefits: Blind
- Requirement: KP Policy
- Do all form fields have appropriate labels?
- Check: All form fields are required to be labeled and placed prior to input fields to ensure that your application can be understood when using screen reader.
- Primarily Benefits: Blind
- Requirement: WCAG2.0 SC 1.3.1
- Is all content and functionality available to a screen reader?
- Check: Using a screen reader (with your eyes closed) you have access to all information and features on the page. You can complete all tasks independently.
- Primarily Benefits: Blind
- Requirement: WCAG2.0 SC 1.3.1
- Do all screens have a page title?
- Check: View each screen and check to make sure each unique screen has an intuitive page title.
- Primarily Benefits: Blind
- Requirement: KP Policy
- Is meaningful link text used? (don’t use “more”, “read more”, etc)
- Check: Review links with screen reader on. Can you understand what the link is for without referencing surrounding content?
- Primarily Benefits: Blind
- Requirement: KP Policy
- Is there interactive space around touch controls?
- Check: Use your thumb to tab interactive elements make sure you can easily tap the item you intended without hitting multiple elements
- Primarily Benefits: Cognitive
- Requirement: KP Policy
- Are form fields laid out in intuitive order?
- Check: Use screen reader on screen with forms. Make sure the order of the form titles and input fields are intuitive
- Primarily Benefits: Blind
- Requirement: KP Policy
- Do form fields in error, have a visual indicator?
- Check: Review the form in error state and ensure the individual fields in error are clearly identified and instructions are provided to the user on the methods to address the errors.
- Primarily Benefits: Blind and Cognitive
- Requirement: KP Policy
- Do multimedia elements have playback controls?
- Check: Review video or multimedia using a player to make sure there are adequate controls to start, stop and pause
- Primarily Benefits: Blind and Cognitive
- Requirement: KP Policy
- Are you using flashing or blinking elements?
- Check: Review application screens to ensure there are no intended flashing or blinking elements
- Primarily Benefits: Cognitive
- Requirement: KP Policy
- Are you using a marquee?
- Check: Review application screens to ensure there are no intended moving/scrolling text, images or animations.
- Primarily Benefits: Cognitive
- Requirement: KP Policy
The following tools can be used to help validate the requirements above:
The following resources can assist in learning more about Accessibility and Usability: