checklist.md

Accessibility testing jam

This worksheet doesn’t include every test for accessibility, but it will get you on your way. It includes steps for testing:

1. Easy-to-automate tests
2. Color and contrast
3. Images and media
4. Language and structure
5. Motion
6. Keyboard support

The items here target Web Content Accessibility Guidelines (WCAG) 2.1 Level A and AA success criteria.

Checklist

1. Easy-to-automate tests

Use Accessibility Insights for Web to get an idea for the type of tests that can be easily automated.

1. Install Accessibility Insights for Web in Chrome
2. Go to Ad hoc tools, and turn on the Automated checks tool.

2. Color and contrast

• Normal-sized text has a contrast of at least 4.5:1 (automated, 1.4.3 Contrast (Minimum) — Level AA)
• Large text has a contrast of at least 3:1 (automated, 1.4.3 Contrast (Minimum) — Level AA)
• Informative icons have a contrast of at least 3:1 (manual, 1.4.11 Non-text Contrast — Level AA)
• User interface indicators have a contrast of at least 3:1 (manual, 1.4.11 Non-text Contrast — Level AA)
• Color alone isn't used to convey information (manual, 1.4.1 Use of Color — Level A)
• Information displays correctly in Windows High Contrast mode (manual, 1.4.1 Use of Color — Level A)

3. Images and media

• Images that convey information have a helpful text equivalent (automated/manual, 1.1.1 Non-text Content — Level A)
• Videos have captions or transcripts (manual, 1.1.1 Non-text Content — Level A, 1.2.1 Audio-only and Video-only (Prerecorded) — Level A, 1.2.2 Captions (Prerecorded) — Level A, 1.2.4 Captions (Live) — Level AA)
• Audio has transcripts (manual, 1.1.1 Non-text Content — Level A, 1.2.1 Audio-only and Video-only (Prerecorded) — Level A, 1.2.2 Captions (Prerecorded) — Level A, 1.2.4 Captions (Live) — Level AA)

4. Language and structure

• The page has a language (automated, 3.1.1 Language of Page — Level A)
• Headings help convey the page structure and use logical levels (assisted, 1.3.1 Info and Relationships — Level A, 2.4.6 Headings and Labels — Level AA)
• Lists are conveyed programmatically (manual, 1.3.1 Info and Relationships — Level A)
• Tables are used for tabular data (manual, 1.3.1 Info and Relationships — Level A)
• Forms have clear labels and instructions (automated/manual, 2.4.6 Headings and Labels — Level AA, 2.5.3 Label in Name — Level A, 3.3.2 Labels or Instructions — Level A, 4.1.2 Name, Role, Value — Level A)
• Links have clear text (automated/manual, 2.4.4 Link Purpose (In Context) — Level A, 2.5.3 Label in Name — Level A, 4.1.2 Name, Role, Value — Level A)
• Errors are clearly conveyed (manual, 3.3.3 Error Suggestion — Level AA)
• The page has a clear and logical title (automated/manual, 2.4.2 Page Titled — Level A)

5. Motion

• Animations can be paused or stopped (manual, 2.2.2 Pause, Stop, Hide — Level A)
• Animations do not cause seizures (manaul, 2.3.1 Three Flashes or Below Threshold — Level A)

6. Keyboard support

• Links, buttons, form fields and all other controls can get keyboard focus and be used with the keyboard (assisted, 2.1.1 Keyboard — Level A, 2.5.4 Motion Actuation — Level A)
• Keyboard focus order is logical (assisted, 2.4.3 Focus Order — Level A)
• Keyboard focus doesn't get stuck (assisted, 2.1.2 No Keyboard Trap — Level A)
• Keyboard focus is visible (manual, 2.4.7 Focus Visible — Level AA)
• Custom keyboard inputs don't cause conflicts (manual, 2.1.4 Character Key Shortcuts — Level A)