all descriptive <img> elements must have a succinct description of the image using alt text, aria-label or aria-labelledby
content
content editor
3
Perceivable
Text Alternatives
1.1.1 Non-text Content
A
2
all complex descriptive <img> element descriptions must be provided adjacent to the image or on a separate page
content
content editor
4
Perceivable
Text Alternatives
1.1.1 Non-text Content
A
2
all controls have an accessible name describing its purpose (often but not always a programmatically linked label)
custom controls, forms and UI
developer
5
Perceivable
Text Alternatives
1.1.1 Non-text Content
A
2
two different modalities of CAPTCHA are provided
content
content editor
6
Perceivable
Text Alternatives
1.1.1 Non-text Content
A
2
or, providing access to a human to bypass CAPTCHA
content
content editor
7
Perceivable
Text Alternatives
1.1.1 Non-text Content
A
2
or, not requiring CAPTCHA for authorised users
content
content editor
8
Perceivable
Text Alternatives
1.1.1 Non-text Content
A
2
a text alternative is provided for charts and graphs
content
content editor
9
Perceivable
Text Alternatives
1.1.1 Non-text Content
A
2
a text or exercise invalid if presented in text has text identification describing the non-text content
content
content editor
10
Perceivable
Time-based media
1.2.1 Audio-only and Video-only (Prerecorded)
A
2
pre-recorded video with no dialogue must come with easily reached text or audio description of what happens visually
audio / video
content editor
11
Perceivable
Time-based media
1.2.1 Audio-only and Video-only (Prerecorded)
A
2
pre-recorded audio must come with easily reached text transcript
audio / video
content editor
12
Perceivable
Time-based media
1.2.2 Captions (Prerecorded)
A
2
video must come with synchronised captions of dialogue, who is speaking and non-speech information including meaningful sound effects
audio / video
content editor
13
Perceivable
Time-based media
1.2.3 Audio Description or Media Alternative (Prerecorded)
A
2
pre-recorded video containing essential information conveyed visually must come with easily reached full-text alternative describing important visual details
audio / video
content editor
14
Perceivable
Time-based media
1.2.3 Audio Description or Media Alternative (Prerecorded)
A
2
or, an audio description track is provided
audio / video
content editor
15
Perceivable
Time-based media
1.2.4 Captions (Live)
AA
2
live audio content must have text-based synchronised captions
audio / video
content editor
16
Perceivable
Time-based media
1.2.5 Audio Description (Prerecorded)
AA
2
video containing essential information conveyed visually must have a synchronised audio description soundtrack
audio / video
content editor
17
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
elements must be used according to their semantics not how they appear
content
developer
18
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
data tables must have header cells created using the <th> element
content
developer
19
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
data tables must have a summary attribute with a concise description of the contents
content
developer
20
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
labels must be programmatically associated to form controls using a
forms and UI
developer
21
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
extra input information is programmatically marked up
forms and UI
developer
22
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
two or more radio buttons, or checkbox controls must be grouped using a <fieldset>
content
developer
23
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
and, the <fieldset> must have a succinct <legend> element
content
developer
24
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
headings must be marked up using heading elements
content
developer
25
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
lists must be marked up using <ul>, <ol>, <dl> elements
content
developer
26
Perceivable
Adaptable
1.3.1 Info and Relationships
A
2
landmark regions have been correctly applied
structure
developer
27
Perceivable
Adaptable
1.3.2 Meaningful Sequence
A
2
the reading order and navigation of content must be logical and intuitive
structure
developer
28
Perceivable
Adaptable
1.3.3 Sensory Characteristics
A
2
instructions for users must rely on more than solely visual cues
content
content editor
29
Perceivable
Adaptable
1.3.3 Sensory Characteristics
A
2
instructions for users must rely on more than sound or auditory cues
content
content editor
30
Perceivable
Adaptable
1.3.4 Orientation
AA
2.1
content orientation is not locked to either landscape or portrait unless essential for functionality
structure
visual designer
31
Perceivable
Adaptable
1.3.5 Identify Input Purpose
AA
2.1
the autocomplete attribute is applied to common user input fields
forms and UI
developer
32
Perceivable
Adaptable
1.3.5 Identify Input Purpose
AA
2.1
and, the autocomplete attribute value uses the correct https://www.w3.org/TR/WCAG21/#input-purposes
forms and UI
developer
33
Perceivable
Distinguishable
1.4.1 Use of Color
A
2
colour must not be the sole method of conveying information or distinguishing visual elements
colour
visual designer
34
Perceivable
Distinguishable
1.4.1 Use of Color
A
2
link colour contrast is at least 3:1 and has an additional non-colour effect when hovered or in focus
colour
visual designer
35
Perceivable
Distinguishable
1.4.2 Audio Control
A
2
a mechanism exists to stop, pause, mute or adjust audio which plays for longer than 3 seconds
audio / video
ux / interaction designer
36
Perceivable
Distinguishable
1.4.3 Contrast (Minimum)
AA
2
text smaller than 24px and not bold has a minimum contrast ratio of 4.5:1 with the background colour
font-size, structure
visual designer
37
Perceivable
Distinguishable
1.4.3 Contrast (Minimum)
AA
2
text smaller than 18.6px and bold has a minimum contrast ratio of 4.5:1 with the background colour
font-size, structure
visual designer
38
Perceivable
Distinguishable
1.4.3 Contrast (Minimum)
AA
2
text at least 24px and not bold has a minimum contrast ratio of 3:1 with the background colour
font-size, structure
visual designer
39
Perceivable
Distinguishable
1.4.3 Contrast (Minimum)
AA
2
text at least 18.6px and bold has a minimum contrast ratio of 3:1 with the background colour
font-size, structure
visual designer
40
Perceivable
Distinguishable
1.4.4 Resize text
AA
2
all text (including controls) is readable at 200% browser zoom
font-size, structure
ux / interaction designer
41
Perceivable
Distinguishable
1.4.5 Images of Text
AA
2
no images of text exists unless essential
content
content editor
42
Perceivable
Distinguishable
1.4.10 Reflow
AA
2.1
no horizontal scrollbars are shown at 400% browser zoom
structure
ux / interaction designer
43
Perceivable
Distinguishable
1.4.11 Non-text Contrast
AA
2.1
if a border is the only way to identify an active control it must have a minimum 3:1 contrast with the adjacent colour
colour, forms and UI
visual designer
44
Perceivable
Distinguishable
1.4.11 Non-text Contrast
AA
2.1
visual state of active control must have a minimum 3:1 contrast with adjacent colour
colour
visual designer
45
Perceivable
Distinguishable
1.4.11 Non-text Contrast
AA
2.1
parts of graphic required to understand the content have a minimum 3:1 contrast with adjacent colour
colour
visual designer
46
Perceivable
Distinguishable
1.4.12 Text Spacing
AA
2.1
there is no loss of content or functionality when the https://dylanb.github.io/bookmarklets.html is applied
structure
ux / interaction designer
47
Perceivable
Distinguishable
1.4.13 Content on Hover or Focus
AA
2.1
additional content triggered on hover or keyboard focus can be dismissed without moving mouse or keyboard focus
dynamic content, keyboard
ux / interaction designer
48
Perceivable
Distinguishable
1.4.13 Content on Hover or Focus
AA
2.1
and, if hover triggers the content pointer can be moved to hovered content without disappearing
dynamic content, keyboard
ux / interaction designer
49
Perceivable
Distinguishable
1.4.13 Content on Hover or Focus
AA
2.1
and, additional content remains visible until hover or focus trigger is removed or user dismisses it
dynamic content, keyboard
ux / interaction designer
50
Operable
Keyboard Accessible
2.1.1 Keyboard
A
2
all functionality must be available from the keyboard
custom controls, forms and UI, keyboard
ux / interaction designer
51
Operable
Keyboard Accessible
2.1.1 Keyboard
A
2
and, shortcut and access keys must not conflict with browser or assistive technology shortcuts
custom controls, forms and UI, keyboard
ux / interaction designer
52
Operable
Keyboard Accessible
2.1.2 No Keyboard Trap
A
2
keyboard focus must not become trapped in a page element
keyboard
ux / interaction designer
53
Operable
Keyboard Accessible
2.1.2 No Keyboard Trap
A
2
and, must be able to navigate to and from all interactive elements using only the keyboard
keyboard
ux / interaction designer
54
Operable
Keyboard Accessible
2.1.4 Character Key Shortcuts
A
2.1
character key shortcuts can be turned off
keyboard
developer
55
Operable
Keyboard Accessible
2.1.4 Character Key Shortcuts
A
2.1
or, character key shortcuts can be remapped
keyboard
developer
56
Operable
Keyboard Accessible
2.1.4 Character Key Shortcuts
A
2.1
or, character key shortcuts are only active when the relevant UI component is in focus
keyboard
developer
57
Operable
Enough Time
2.2.1 Timing Adjustable
A
2
page time limits have an option to turn off, adjust or extend the time limit
dynamic content
ux / interaction designer
58
Operable
Enough Time
2.2.2 Pause Stop Hide
A
2
content that moves, blinks or scrolls automatically lasting longer than 5 seconds must be able to be paused, stopped or hidden
dynamic content
ux / interaction designer
59
Operable
Seizures and Physical Reactions
2.3.1 Three Flashes or Below Threshold
A
2
page content must not flash more than 3 times per second
dynamic content
ux / interaction designer
60
Operable
Navigable
2.4.1 Bypass Blocks
A
2
skip links are provided to avoid page elements that repeat across multiple pages
structure
ux / interaction designer
61
Operable
Navigable
2.4.1 Bypass Blocks
A
2
or, a proper heading structure is provided
structure
ux / interaction designer
62
Operable
Navigable
2.4.1 Bypass Blocks
A
2
or, aria/HTML5 landmarks are provided
structure
ux / interaction designer
63
Operable
Navigable
2.4.1 Bypass Blocks
A
2
iframes must have descriptive, informative and unique titles
structure
ux / interaction designer
64
Operable
Navigable
2.4.2 Page Titled
A
2
page <title> must be descriptive and informative
structure
content editor
65
Operable
Navigable
2.4.3 Focus Order
A
2
the navigation order of link, form elements and interactive components must be logical
structure
ux / interaction designer
66
Operable
Navigable
2.4.4 Link Purpose (In Context)
A
2
each link is understandable solely from the displayed text
content, link
content editor
67
Operable
Navigable
2.4.4 Link Purpose (In Context)
A
2
or, each link is understandable from the immediate surrounding content
content, link
content editor
68
Operable
Navigable
2.4.5 Multiple Ways
AA
2
at least 2 of related pages, table of contents, site map, site search, or list of web pages must be provided for non-workflows
content
ux / interaction designer
69
Operable
Navigable
2.4.6 Headings and Labels
AA
2
labels for form controls and interactive controls must be informative
custom controls, forms and UI
content editor
70
Operable
Navigable
2.4.6 Headings and Labels
AA
2
page headings must be informative
structure
content editor
71
Operable
Navigable
2.4.7 Focus Visible
AA
2
all interactive elements have a visible focus effect
custom controls, forms and UI
visual designer
72
Operable
Input Modalities
2.5.1 Pointer Gestures
A
2.1
path-based multi-point functionality can be operated with single-point actions
custom controls
ux / interaction designer
73
Operable
Input Modalities
2.5.2 Pointer Cancellation
A
2.1
functionality operated by a single mouse click does not use the down-event
custom controls
developer
74
Operable
Input Modalities
2.5.2 Pointer Cancellation
A
2.1
or, the functionality can be undone
custom controls
developer
75
Operable
Input Modalities
2.5.2 Pointer Cancellation
A
2.1
or, the up-event reverses the action of the down-event
custom controls
developer
76
Operable
Input Modalities
2.5.2 Pointer Cancellation
A
2.1
or, the down event is essential for the function (i.e. onscreen keyboard)
custom controls
developer
77
Operable
Input Modalities
2.5.3 Label in Name
A
2.1
UI controls which include a visible label have a matching full (or partial) accessible name
custom controls, forms and UI
developer
78
Operable
Input Modalities
2.5.4 Motion Actuation
A
2.1
functionality triggered by a users motion or gestures can be turned off
structure
ux / interaction designer
79
Operable
Input Modalities
2.5.4 Motion Actuation
A
2.1
and, functionality can be operated without device motion or user gestures
structure
ux / interaction designer
80
Understandable
Readable
3.1.1 Language of Page
A
2
each page must have a lang attribute
structure
developer
81
Understandable
Readable
3.1.2 Language of Parts
AA
2
content in a different language than the page default must be identified using the lang attribute
structure
developer
82
Understandable
Predictable
3.2.1 On Focus
A
2
when an elements receives focus it must not result in a substantial clientside change to the page
forms and UI
ux / interaction designer
83
Understandable
Predictable
3.2.2 On Input
A
2
user initiated input must not result in a substantial clientside change to the page
forms and UI
ux / interaction designer
84
Understandable
Predictable
3.2.3 Consistent Navigation
AA
2
repeated navigation patterns are applied in the same relative order across multiple pages
structure
visual designer
85
Understandable
Predictable
3.2.4 Consistent Identification
AA
2
elements with the same functionality are applied consistently across multiple pages
structure
visual designer
86
Understandable
Input Assistance
3.3.1 Error Identification
A
2
intuitive text based alerts must be provided for form validation cues and errors
forms and UI
developer
87
Understandable
Input Assistance
3.3.2 Labels or Instructions
A
2
a text label (not necessarily a label element) must be provided for form fields
forms and UI
developer
88
Understandable
Input Assistance
3.3.2 Labels or Instructions
A
2
sufficient instructions must be provided for form fields
forms and UI
developer
89
Understandable
Input Assistance
3.3.2 Labels or Instructions
A
2
a text label (not necessarily a label element), instructions or error message must be provided for required form fields
forms and UI
developer
90
Understandable
Input Assistance
3.3.3 Error Suggestion
AA
2
all clientside detected errors provide suggestions to fix the errors
forms and UI
developer
91
Understandable
Input Assistance
3.3.3 Error Suggestion
AA
2
all clientside detected errors are provided in an accessible manner
forms and UI
developer
92
Understandable
Input Assistance
3.3.4 Error Prevention (Legal Financial Data)
AA
2
a mechanism exists to reverse any legal, financial or data transaction mistakes
content
developer
93
Understandable
Input Assistance
3.3.4 Error Prevention (Legal Financial Data)
AA
2
or, a mechanism exists to review and correct any legal, financial or data transaction
content
developer
94
Robust
Compatible
4.1.1 Parsing
A
2
HTML elements must have complete start and end tags
structure
developer
95
Robust
Compatible
4.1.1 Parsing
A
2
elements must be nested according to specification
structure
developer
96
Robust
Compatible
4.1.1 Parsing
A
2
elements must not contain duplicate attributes
structure
developer
97
Robust
Compatible
4.1.1 Parsing
A
2
element ID's must be unique
structure
developer
98
Robust
Compatible
4.1.2 Name Role Value
A
2
user interface elements are used according to their specification
custom controls, forms and UI
developer
99
Robust
Compatible
4.1.2 Name Role Value
A
2
or, custom controls follow the https://www.w3.org/TR/wai-aria-practices-1.1/
custom controls
developer
100
Robust
Compatible
4.1.2 Name Role Value
A
2
a programmatic name, role and value exists for all user interface components
custom controls, forms and UI
developer
101
Robust
Compatible
4.1.3 Status Messages
AA
2.1
all client-side updated success or action outcome messages use role=status
custom controls
developer
102
Robust
Compatible
4.1.3 Status Messages
AA
2.1
all client-side updated error or warning messages use role=alert
custom controls
developer
103
Robust
Compatible
4.1.3 Status Messages
AA
2.1
all client-side updated log or progress messages use role=log