WCAG Guidelines

web-accessibility-logo
Using a bandaid as a solution, such as a widget overlay, will leave you exposed to lawsuits and ineffective solutions. An overlay does not fix issues but hides them. To be competitive with the ADA the solution must be fixed from the source. With our proprietary software, you will be able to create accessibility from the ground up and protect yourself from unnecessary lawsuits. 

The Allyable platform provides coverage for WCAG 2.0+ regulation that can be identified and potentially solved by technology. The Allyable platform is not a replacement for manual testing, use case testing, or usability testing; rather, it is an important component of a robust accessibility and quality program and should be viewed as such. In the tables below, you can see which of the WCAG Success Criteria are tested and supported today by Allyable. Allyable works constantly to add additional tests and automated fixes to our award-winning platform.

The following tables show which violations under the Accessibility Guidelines can be automatically detected by our accessibility tools. Most, if not all, of the violations found can be fixed by using simple wizards and code remediation development tools available in our platform.

WCAG Level A WCAG Standard Auto-Identified Auto-Fixed
1.1.1 Non-text Content 2.0 Yes Yes
1.2.1 Audio-only and Video-only (Prerecorded) 2.0
1.2.2 Captions (Prerecorded) 2.0 Yes Yes (Partially)
1.2.3 Audio Description or Media Alternative (Prerecorded) 2.0
1.3.1 Info and Relationships 2.0 Yes Yes (Partially)
1.3.2 Meaningful Sequence 2.0
1.3.3 Sensory Characteristics 2.0
1.4.1 Use of Color 2.0
1.4.2 Audio Control 2.0
2.1.1 Keyboard 2.0 Yes
2.1.2 No Keyboard Trap 2.0
2.1.4 Character Key Shortcuts 2.1
2.2.1 Timing Adjustable 2.0 Yes Yes
2.2.2 Pause, Stop, Hide 2.0 Yes
2.3.1 Three Flashes or Below Threshold 2.0
2.4.1 Bypass Blocks 2.0 Yes Yes
2.4.2 Page Titled 2.0 Yes Yes
2.4.3 Focus Order 2.0
2.4.4 Link Purpose (In Context) 2.0 Yes Yes
2.5.1 Pointer Gestures 2.1
2.5.2 Pointer Cancellation 2.1
2.5.3 Label in Name 2.1 Yes
2.5.4 Motion Actuation 2.1
3.1.1 Language of Page 2.0 Yes Yes
3.2.1 On Focus 2.0
3.2.2 On Input: 2.0
3.3.1 Error Identification 2.0
3.3.2 Labels or Instructions 2.0
4.1.1 Parsing 2.0
4.1.2 Name, Role, Value 2.0 Yes
WCAG Level AAWCAG StandardAuto-IdentifiedAuto-Fixed
1.2.4 Captions (Live)2.0  
1.2.5 Audio Description (Prerecorded)2.0Yes 
1.3.4 Orientation2.1  
1.3.5 Identify Input Purpose2.1Yes 
1.4.3 Contrast (Minimum)2.0Yes 
1.4.4 Resize text2.0Yes 
1.4.5 Images of Text2.0  
1.4.10 Reflow2.1Yes 
1.4.11 Non-Text Contrast2.1Yes 
1.4.12 Text Spacing2.1In progress 
1.4.13 Content on Hover or Focus2.1  
2.4.5 Multiple Ways2.0  
2.4.6 Headings and Labels2.0  
2.4.7 Focus Visible2.0  
3.1.2 Language of Parts2.0Yes 
3.2.3 Consistent Navigation2.0  
3.2.4 Consistent Identification2.0  
3.3.3 Error Suggestion2.0  
3.3.4 Error Prevention (Legal, Financial, Data)2.0  
4.1.3 Status Messages2.1
WCAG Level AAAWCAG StandardAuto-IdentifiedAuto-Fixed
1.2.6 Sign Language (Prerecorded)2.0  
1.2.7 Extended Audio Description (Prerecorded)2.0  
1.2.8 Media Alternative (Prerecorded)2.0  
1.2.9 Audio-only (Live)2.0  
1.3.6 Identify Purpose2.1  
1.4.6 Contrast (Enhanced)2.0  
1.4.7 Low or No Background Audio2.0  
1.4.8 Visual Presentation2.0  
1.4.9 Images of Text (No Exception)2.0  
2.1.3 Keyboard (No Exception)2.0  
2.2.3 No Timing2.0  
2.2.4 Interruptions2.0Yes 
2.2.5 Re-authenticating2.0  
2.2.6 Timeouts2.1  
2.3.2 Three Flashes2.0  
2.3.3 Animation from Interactions2.1  
2.4.10 Section Headings2.0  
2.4.8 Location2.0  
2.4.9 Link Purpose (Link Only)2.0  
2.5.5 Target Size2.1Yes 
2.5.6 Concurrent Input Mechanisms2.1  
3.1.3 Unusual Words2.0  
3.1.4 Abbreviations2.0  
3.1.5 Reading Level2.0  
3.1.6 Pronunciation2.0  
3.2.5 Change on Request2.0Yes 
3.3.5 Help2.0  
3.3.6 Error Prevention (All)2.0

Lets Talk

Allyable’s digital accessibility experts are ready to help.
In a few words how can we help: