WCAG 2.1 – AT Testing Guide
Using this page as a guide, you can test a website with assistive technology. This page shows the Missouri State Standard WCAG Success Criteria. This guide provides a correlation between the type of AT to consider when testing different WCAG guidelines.
Various software tools can be used for website testing including screen readers, voice input programs, learning & writing assistant tools, alternative mice and magnification software. Our AT User Guides are prepared for the following assistive technologies: NVDA, VoiceOver, Dragon Professional, HeadMouse Nano, Jelly Bean Switch Activation, Zoomtext and Helperbird Extension.
WCAG 2.1 – POUR Guiding Principles
Describe all content on the site for all types of senses. The following tips will make a website’s content perceivable:
- Add text descriptions to your images.
- Include both closed captions and transcripts for audio content with videos.
- Provide sufficient color contrast in text and background.
- Do not use color alone to encourage an action.
- Ask, does this site content have alternative ways to see, or hear the information presented.
1.1 Text Alternatives
1.1.1 Non-text Content – Test with a screen reader
1.2 Time-based Media
1.2.1 Audio-only and Video-only (Prerecorded)
1.2.3 Audio Description or Media Alternative (Prerecorded)
1.2.5 Audio Description (Prerecorded)
1.2.6 Sign Language (Prerecorded)
1.2.7 Extended Audio Description (Prerecorded)
1.2.8 Media Alternative (Prerecorded)
1.3 Adaptable
1.3.1 Info and Relationships – Test with a reading & writing assistant tool
1.3.2 Meaningful Sequence – Test with a screen reader or voice input software
1.3.3 Sensory Characteristics– Test with a screen reader
1.3.4 Orientation – Test with a screen reader
1.3.5 Identify Input Purpose – Test with a screen reader, a voice input software, a reading & Writing assistant tool, or mouse alternative
1.3.6 Identify Purpose – Test with a reading & Writing assistant tool
1.4 Distinguishable
1.4.1 Use of Color – Test with a magnification software
1.4.2 Audio Control – Test with screen reader or a magnification software or an reading & Writing assistant tool
1.4.3 Contrast (Minimum) – Test with magnification software
1.4.4 Resize Text – Test with magnification software
1.4.5 Images of Text – Test with screen reader or a magnification software
1.4.6 Contrast (Enhanced) – Test with magnification software
1.4.7 Low or No Background Audio
1.4.9 Images of Text (No Exception)
1.4.10 Reflow – Test with a screen reader (Look at Mobile Screen and PC for responsive design)
1.4.13 Content on Hover or Focus – Test with magnification software
Meet the individual where they are at, using their access methods. A user can successfully use controls, buttons, navigation, and other interactive elements. The following tips make a website’s content operable:
- Provide a clear structure with headings.
- Create descriptive and understandable links.
- Label fields for data entry to communicate what is needed.
- Provide sufficient time for entry.
- Avoid content that flashes or quick moving banners.
- Provide the ability to stop or start a motion. (Player, Slide Show)
- Ensure activation targets are a sufficient size.
2.1 Keyboard Accessible
2.1.1 Keyboard – Test with a mouse alternative
2.1.2 No Keyboard Trap – Test with a screen reader, voice input software or a mouse alternative
2.1.3 Keyboard (No Exception) – Test with a screen reader, voice input software or a mouse alternative
2.1.4 Character Key Shortcuts– Test with a screen reader, voice input software or a mouse alternative
2.2 Enough Time
2.2.1 Timing Adjustable – Test with a mouse alternative.
2.2.2 Pause, Stop, Hide – Test with a screen reader, Reading & Writing assistant tool, or a magnification software
2.2.3 No Timing – Test with voice input software.
2.2.4 Interruptions – Test with a screen reader, Reading & Writing assistant tool, or a magnification software
2.2.5 Re-authenticating – Test with a screen reader, Reading & Writing assistant tool, mouse alternative, voice input software or a magnification software
2.2.6 Timeouts – Test with a screen reader, Reading & Writing assistant tool or a mouse alternative
2.3 Seizures and Physical Reactions
2.3.1 Three Flashes or Below Threshold –
2.3.3 Animation from Interactions
2.4 Navigable
2.4.1 Bypass Blocks – Test with voice input software
2.4.2 Page Titled – Test with a screen reader
2.4.3 Focus Order – Test with a screen reader or voice input software
2.4.4 Link Purpose (In Context) – Test with a screen reader or voice input software
2.4.5 Multiple Ways – Test with a mouse alternative
2.4.6 Headings and Labels – Test with a screen reader
2.4.7 Focus Visible – Test with a screen reader and magnification software
2.4.9 Link Purpose (Link Only)
2.4.10 Section Headings – Test with magnification software
2.5 Input Modalities
2.5.1 Pointer Gestures– Test with a mouse alternative
2.5.2 Pointer Cancellation– Test with a mouse alternative
2.5.5 Target Size – Test with a mouse alternative
2.5.6 Concurrent Input Mechanisms – Test with voice input software
Provide content that is intuitive and behaves in a predictable way for the user. Consider the use of the language and the reading level for your audience. To make a website’s content understandable:
- Provide clear directions.
- Aim for consistency and predictability in the page navigation.
- Use plain language.
- Include explanations of acronyms, abbreviations and subject-specific jargon.
3.1 Readable
3.1.1 Language of Page – Test with a screen reader, an onscreen keyboard or reading & writing assistant tool
3.1.2 Language of Parts – Test with a reading & writing assistant tool
3.1.3 Unusual Words – Test with a reading & writing assistant tool
3.1.4 Abbreviations – Test with a reading & writing assistant tool
3.1.5 Reading Level – Test with a reading & writing assistant tool
3.1.6 Pronunciation – Test with a reading & writing assistant tool
3.2 Predictable
3.2.1 On Focus -Test with voice input software or a mouse alternative (test drop down menu engage and leave)
3.2.2 On Input-Test with voice input software, a screen reader or a mouse alternative (Test phone entry field)
3.2.4 Consistent Identification
3.3 Input Assistance
3.3.1 Error Identification – Test with a screen reader or voice input software (Date format error message)
3.3.2 Labels or Instructions – Test with a screen reader or voice input software (form fields, buttons)
3.3.3 Error Suggestion– Test with a screen reader or voice input software (Date format error message)
3.3.4 Error Prevention (Legal, Financial, Data) – Test with a screen reader or voice input software(User is able to review and correct form entries before hitting the submit button)
3.3.6 Error Prevention (All) – Test with a screen reader or voice input software (User is able to review and correct form entries before hitting the submit button)
AT and browsers improve over time. This means it becomes more robust. Content and structure must be robust enough that it can be interpreted reliably by a wide variety of users. People should be able to choose their tech to interact with websites, online documents, multimedia, and other information.
To make a website’s content robust:
- Provide descriptive metadata.
- Perform an accessibility check in more than one browser.
- Allow for any orientation of a screen to view the website.
- Test for accessibility with people and AT.
4.1 Compatible
4.1.1 Parsing – Test with any assistive technologies as it updates.
Resources
Let’s Talk ICT – Device Use Recorded Sessions
Guidance Resources
WCAG 2.1 Accessibility Techniques
WCAG 2.1 Standard and Guidelines
WCAG AT Users
Accessibility Checklists
Missouri State Accessibility Review Checklist
