WAS Certification Prep
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
WCAG 2.1
2
PrinciplesGuidelinesSuccess CriteriaConformanceTechniquesDisability Aided
3
Perceivable:
Content & interface must be perceivable
1.1 Text alternatives1.1.1 Non-text contentAShort text alternativeVisually impaired, hearing impaired
4
Long text alternative
5
Alternatives for controls & inputs
6
Alternatives for time-based media, exams, or specific sensory experiences
7
CAPTCHA
8
Decorations or items meant to be ignored by AT
9
1.2 Time based media1.2.1 Audio-only & video-only
(pre-recorded)
AVisually impaired, hearing impaired
10
1.2.2 Captions
(pre-recorded)
Ahearing impaired
11
1.2.3 Audio description or media alternative
(pre-recorded)
AVisually impaired, hearing impaired
12
1.2.4 Captions
(live)
AAhearing impaired
13
1.2.5 Audio description
(pre-recorded)
AAVisually impaired
14
1.2.6 Sign Language
(pre-recorded)
AAAhearing impaired
15
1.2.7 Extended audio description
(pre-recorded)
AAAVisually impaired
16
1.2.8 Media alternatives
(pre-recorded)
AAAVisually impaired, hearing impaired
17
1.2.9 Audio-only
(live)
AAAhearing impaired
18
1.3 Adaptable1.3.1 Info and relationshipsASemantic structure (markup)Visually impaired
19
Text formatting
20
1.3.2 Meaningful sequencesADOM order == visual orderVisually impaired, motor impaired
21
Logical reading order
22
1.3.3 Sensory characteristicsACouple text with other operational cuesVisually impaired, hearing impaired
23
1.3.4 OrientationAAAllow landscape and portraitCognitive, Visually impaired, motor impaired
24
1.3.5 Identify input purposesAAHTML5 input typesCognitive, Visually impaired
25
1.3.6 Identify purposeAAALabels for iconsCognitive, Visually impaired
26
1.4 Distinguishable1.4.1 Use of colorAVisually impaired
27
1.4.2 Audio controlAVolume control; play/pauseVisually impaired
28
1.4.3 Contrast (minimum)AAVisually impaired
29
1.4.4 Resize textAAClear at 200% zoomVisually impaired
30
1.4.5 Images of textAAVisually impaired
31
1.4.6 Contrast (enhanced)AAAVisually impaired
32
1.4.7 Low or no background audioAAA
33
1.4.8 Visual presentationAAAVisually impaired
34
1.4.9 Images of text (no exception)AAAVisually impaired
35
1.4.10 ReflowAACognitive, Visually impaired
36
1.4.11 Non-text contrastAAVisually impaired
37
1.4.12 Text spacingAACognitive, Visually impaired
38
1.4.13 Content on hover or focusAATooltips are dismissable and persistentCognitive, Visually impaired, motor impaired
39
Operable:
User interface components and navigation must be operable.
2.1 Keyboard accessible2.1.1 KeyboardATab orderVisually impaired, motor impaired
40
keyboard event handlers
41
2.1.2 No keyboard trapAUser shouldn't get trapped in a componentVisually impaired, motor impaired
42
2.1.3 Keyboard (no exception)AAAVisually impaired, motor impaired
43
2.1.4 Character key shortcutsAVisually impaired, motor impaired
44
2.2 Enough time2.2.1 Timing AdjustableAUser can extend time with a keystroke (spacebar)Motor impaired
45
2.2.2 Pause, Stop, HideAUser can stop, pause, or hide scrolling content (carousels, feeds, etc)Visually impaired, motor impaired
46
2.2.3 No timingAAAMotor impaired
47
2.2.4 InterruptionsAAAVisually impaired, motor impaired
48
2.2.5 Re-authenticatingAAASave user's data to be added during re-authenticationMotor impaired
49
2.2.6 TimeoutsAAAWarn user before timeout to avoid data lossCognitive, motor impaired
50
2.3 Seizures and physical reaction2.3.1 Three flashes or below thresholdA
51
2.3.2 Three flashesAAA
52
2.3.3 Animation from interactionsAAAUser can disable any motion animation that happens after an interactionCognitive
53
2.4 Navigable2.4.1 Bypass blocksASkip to main linkVisually impaired, motor impaired
54
2.4.2 Page titledAEach page needs a unique titleVisually impaired
55
2.4.3 Focus orderALogical tab orderVisually impaired, motor impaired
56
DOM order == visual order
57
2.4.4 Link purpose (in context)AUse text within a hyperlink, and not an ambiguous URLVisually impaired
58
2.4.5 Multiple waysAASearchVisually impaired, motor impaired
59
Table of contents
60
Site map
61
Related resources links
62
2.4.6 Headings and labelsAAHeadings are unique and descriptiveVisually impaired
63
2.4.7 Focus visibleAAVisible keyboard focus on links and inputsVisually impaired, motor impaired
64
2.4.8 LocationAAABreadcrumbsVisually impaired
65
Active tab on navigation bar
66
Sitemap
67
2.4.9 Link purpose (link only)AAALink purpose is clear when taken out of context (like a link list presented by a screen reader)Visually impaired
68
2.4.10 Section headingsAAAHeadings for each sectionVisually impaired
69
2.5 Input modalities2.5.1 Pointer gesturesA Offer simplified alternatives for complex pointer gesturesCognitive, motor impaired
70
2.5.2 Pointer cancellationAMotor impaired
71
2.5.3 Label in nameACognitive, Visually impaired
72
2.5.4 Motion actuationAAllow alternatives to motion gesturesCognitive, motor impaired
73
2.5.5 Target sizeAAAMake interactive controls big (> 44x44pxVisually impaired, motor impaired
74
2.5.6 Concurrent input mechanismsAAAAllow for keyboard useCognitive, Visually impaired, motor impaired
75
Understandable
Information and the operation of user interface must be understandable.
3.1 Readable3.1.1 Language of PageAUse lang attributeVisually impaired
76
3.1.2 Language of PartsAAUse lang attributeVisually impaired
77
3.1.3 Unusual WordsAAALink to definitions or glossaryCognitive
78
3.1.4 AbbreviationsAAAUse abbr elementCognitive
79
3.1.5 Reading LevelAAAProvide text summary or simplify all of textCognitive
80
3.1.6 PronunciationAAAUse ruby markupCognitive
81
3.2 Predictable3.2.1 On focusAAvoid using "focus" change to submit a form. Use a means to activate/submit.Visually impaired, motor impaired
82
3.2.2 On inputAProvide a submit button for formsVisually impaired, motor impaired
83
3.2.3 Consistent navigationAAKeep repetitive components in the same orderCognitive, Visually impaired
84
3.2.4 Consistent identificationAAKeep labels, names, alt text consistent Cognitive, Visually impaired
85
3.2.5 Change on requestAAAProvide control to request content updates, rather than forced to use autoupdatesCognitive, Visually impaired
86
3.3 Input Assistance3.3.1 Error identificationAAfter error occurrs, identify the error (required, invalid, etc)Cognitive, Visually impaired
87
3.3.2 Labels or instructionsAProvide labels with additional descriptionCognitive, Visually impaired
88
3.3.3 Error suggestionAAUse more descriptive error messages to pinpoint what corrections need to happenCognitive, Visually impaired
89
3.3.4 Error prevention (legal, financial, data)AAAllow user to review and correct before final submissionCognitive, Visually impaired, motor impaired
90
3.3.5 HelpAAAProvide text instructions or help linkCognitive
91
3.3.6 Error prevention (all)AAAAllow user to review and correct before final submissionCognitive, Visually impaired, motor impaired
92
Robust
Content must be robust enough that it can be interpreted by by a wide variety of user agents, including assistive technologies.
4.1 Compatible4.1.1 ParsingAValid HTMLVisually impaired
93
4.1.2 Name, role, valueACustom widgets have name and role assignedVisually impaired
94
4.1.3 Status messagesAAAT can receive status messages without focusVisually impaired
95
96
97
98
99
100
Loading...