Accessibility Audit Checklist
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCFGHIJKLMNOPQRSTUVWXYZ
1
Category
Success Criteria
LevelDescriptionRole: Design
2
Images1.1.1AImages that present content must have a text alternative
3
Images1.1.1AActive images must have a text alternative
4
Images1.1.1AText alternatives must be descriptive of the content
5
Images1.1.1ADecorative content must have a null text alternative
6
Media1.2.1APrerecorded audio-only content has a transcript
7
Media1.2.1APrerecorded video-only content has a transcript or audio description
8
Media1.2.2APrerecorded video/audio content has captions
9
Media1.2.3APrerecorded video/audio content (that should have a transcript or audio description) has a transcript or audio description
10
Media1.2.4AALive video/audio content (that should have captions) has captions
11
Media1.2.5AAPrerecorded video/audio content (that should have an audio description) has an audio description
12
Structure1.3.1AContent serving the purpose of a semantic element must be programmaticaly discernable as that semantic element (headings, paragraphs, landmarks, tables, ordered/unordered/description lists, etc.)
13
Structure1.3.1AContent not serving the purpose of a semantic element must not be programmatically discernable as that semantic element (headings, landmarks, paragraphs, tables, ordered/unordered/description lists, etc.)
14
Forms1.3.1AInputs and controls must have programmatic labels
15
Forms1.3.1AGroups of inputs must have programmatic group labels
16
Structure1.3.1ATable header must be programmatically associated with their respective data cells
17
Structure1.3.2AVisual content order matches programmatic content order when a mismatch would change or confuse the meaning
18
Sensory1.3.3ADo not use sensory characteristics alone (shape, size, visual location, orientation, or sound) to communicate instructions for page use
19
Color1.4.1AColor alone must not be used to distinguish between interactive text and non-interactive text
20
Color1.4.1AColor alone must not be used to distinguish between information presented in content (charts, graphs, etc.)
21
Color1.4.1AColor alone must not be used to communicate differences in content (e.g. red, green, yellow circles for different classifications)
22
Media1.4.2AFor autoplaying audio that lasts longer than 3 seconds, the player must have a pause or stop control OR a volume control
23
Color1.4.3AAThe color contrast of text and its background must meet the appropriate contrast minimum
24
Presentation1.4.4AAText resizing must not be disabled
25
Presentation1.4.4AAPinch-to-zoom must not be disabled
26
Presentation1.4.4AAWhen text resized to 200%, no page content or information is lost
27
Presentation1.4.4AAWhen text resized to 200%, interactive elements must still be activateable
28
Images1.4.5AAImages are not used to communicate text when plain-text can be used
29
Keyboard2.1.1AAll interactive elements can be activated with keyboard
30
Keyboard2.1.1ATimed keyboard interactions (e.g. "double-clicking" a key) are not required
31
Keyboard2.1.2AAll interactive elements can be navigated away from using a standard escape method (tab, shift+tab, arrow keys, Esc, etc.)
32
Time Limit2.2.1ANon-essential time limits (that are less than 20 hours) can be turned off, adjusted, or extended.
33
Sensory2.2.2AMoving, blinking, or scrolling content that starts automatically, lasts more than five seconds, and is presented alongside other content must have a method to pause, stop, or hide the moving blinking or scrolling content.
34
Sensory2.2.2AAuto-updating content (like a slideshow banner) that starts automatically and is presented alongside other content must have a method to pause, stop, or hide the auto-updating content.
35
Sensory2.3.1AContent on the page doesn't flash more than 3 times in a second.
36
Structure2.4.1APages with headers, navigations, or similar blocks of repeated content before the main content provide a "skip to main content" link.
37
Structure2.4.2AThe title element for the page (including pages in iframes) is not empty
38
Structure2.4.2AIframes have title attributes
39
Structure2.4.2AIframes have unique and descriptive title attributes
40
Structure2.4.2AThe values for title (both elements and attributes) are unique and descriptive of the content of the page
41
Keyboard2.4.3AFocus order must closely (but not necessarily exactly) follow the visual design of the page
42
Keyboard2.4.3AIf positive tabindex attributes are used, the meaning and operability of the page must be preserved
43
Keyboard2.4.3ACustom components and elements must manage focus logically
44
Links2.4.4AUnambiguous link text makes sense either on its own or when combined with context from its sentence, paragraph, preceding heading, parent list item, or other content within its data cell when combined with its associated header cell.
45
Structure2.4.5AA
For pages that aren't steps in or the result of a process, two of the following must be provided to help users find a page (links to related pages, table of contents, site map, search mechanism, linking to all pages from the homepage, linking to all pages on every page)
46
Structure2.4.6AAHeadings must be descripive of their content
47
Forms2.4.6AALabels must be descriptive of their component
48
Keyboard2.4.7AAItems in the focus order must have a visible focus indicator
49
Structure3.1.1AThe default language of the page must be specified
50
Structure3.1.2AAContent not in the default language of the page must be specified, except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text
51
Context3.2.1AWhen an item receives keyboard focus, there must be no change of context (user agent, viewport, focus, changing content before the users current position on the page)
52
Context3.2.2AWhen a component receives input, there must be no change of context (user agent, viewport, focus, changing content before the users current position on the page)
53
Consistency3.2.3AANavigation on the site or within a set of pages must be presented in the same order
54
Consistency3.2.4AAComponents on the site or within a set of pages must have similar labeling and functionality
55
Forms3.3.1AInline error messages must be announced to screen reader users when displayed visually
56
Form Info3.3.1AError messages after form submission must be announced to screen readers when displayed visually
57
Form Info3.3.1AInstructional information helpful for completing an input must be programmatically associated with the input
58
Forms3.3.2AInputs and controls must have visible labels (not to be confused with visible text labels)
59
Forms3.3.2AGroups of inputs must have visible labels (not to be confused with visible text labels)
60
Form Info3.3.3AARequired inputs must be communicated either explicitly (i.e. denoting fields that are required, or similar method) or implicitly (i.e. denoting optional fields but not required fields, throwing an error message after input, or similar method)
61
Form Info3.3.3AAError messages must be descriptive enough to help the user resolve the issue without compromising security (e.g. providing details about a password)
62
Form Info3.3.3AAInline error messages must be programmatically associated with the input
63
Forms3.3.4AA
For pages obligating users to a legal commitment, financial transaction, or updating user data, one of the following must be true. A method is provided reverse the submission, data is checked for errors and the user is given the option to correct any errors, or the user is given the opportunity to review and correct information before submission.
64
Code Quality4.1.1AElements must have required start and end tags
65
Code Quality4.1.1AElements must be nested according to specification
66
Code Quality4.1.1AElements must not have duplicate attributes
67
Code Quality4.1.1AIDs must be unique
68
Code Quality4.1.1ANames of elements and attributes must be free of errors (e.g. An "image" tag marked up as <imge> instead of <img> would be incorrect)
69
Custom Elements
4.1.2ACustom elements and components must have a programmatically determinable name and role
70
Custom Elements
4.1.2ACustom element and component states, values, and properties must be programmatically discernable
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Accessibility Audit Checklist