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

Comment only
 
 
ABCEGHIJKLMNOPQRSTUVW
1
Category
Success Criteria
LevelDescriptionWCAG 2.1
2
Images1.1.1AImages that present content must have a text alternativeX
3
Images1.1.1AActive images must have a text alternativeX
4
Images1.1.1AText alternatives must be descriptive of the contentX
5
Images1.1.1ADecorative content must have a null text alternativeX
6
Media1.2.1APrerecorded audio-only content has a transcriptX
7
Media1.2.1APrerecorded video-only content has a transcript or audio descriptionX
8
Media1.2.2APrerecorded video/audio content has captionsX
9
Media1.2.3APrerecorded video/audio content (that should have a transcript or audio description) has a transcript or audio descriptionX
10
Media1.2.4AALive video/audio content (that should have captions) has captionsX
11
Media1.2.5AAPrerecorded video/audio content (that should have an audio description) has an audio descriptionX
12
Structure1.3.1AGroups of content presented as sections, regions, or landmarks (header, footer, main content,
etc.) should be recognized as landmarks by assistive technology
X
13
Structure1.3.1AContent not presented as page sections, regions, or landmarks (header, footer, main content,
etc.) should not be recognized as landmarks by assistive technology
X
14
Structure1.3.1AIf more than one of the same type of landmark is used, each landmark of
that type must have a unique label recognized by assistive technology
X
15
Structure1.3.1AText presented as a heading should be recognized as a heading by assistive technologyX
16
Structure1.3.1AText not presented as a heading should not be recognized as a heading by assistive technologyX
17
Structure1.3.1AText presented as a heading should be recognized as the appropriate level of heading by assistive technologyX
18
Structure1.3.1AContent presented as a list should be recognized as a list by assistive technologyX
19
Structure1.3.1AContent not presented as a list should not be recognized as a list by assistive technologyX
20
Structure1.3.1AContent presented as a list is recognized as the appropriate type of list by assistive technologyX
21
Structure1.3.1AData tables should be recognized as tables by assistive technologyX
22
Structure1.3.1ALayout tables should not be recognized as tables by assistive technologyX
23
Structure1.3.1ASemantic elements must not be used only for aesthetic purposes (e.g. using fieldset to put content inside a box)X
24
Forms1.3.1ANative inputs and controls must have programmatic labelsX
25
Forms1.3.1AGroups of related native inputs must have programmatic group labels (especially radio and checkbox groups)X
26
Structure1.3.1ATable headers must be programmatically associated with their respective data cellsX
27
Structure1.3.2AVisual content order matches programmatic content order when a mismatch would change or confuse the meaningX
28
Sensory1.3.3ADo not use sensory characteristics alone (shape, size, visual location, or sound) to communicate instructions for page useX
29
Sensory1.3.3ADo not rely on visual positioning of form inputs to communicate how to complete form inputs (i.e. "fill in the blank" style text inputs)
30
Sensory1.3.4AContent adjusts to the device orientation unless it is considered essentialX
31
Sensory1.3.4AWhen auto-rotate setting is disabled (orientation is locked), content does not adjust to the device orientation unless it is considered essentialX
32
Forms1.3.5AAText inputs that gather user information represented in the list of input purposes must do so. For the list of "input purposes," see https://www.w3.org/TR/WCAG21/#input-purposesX
33
Color1.4.1AColor alone must not be used to distinguish between interactive text and non-interactive textX
34
Color1.4.1AColor alone must not be used to distinguish between information presented in content (charts, graphs, etc.)X
35
Color1.4.1AColor alone must not be used to communicate differences in content (e.g. red, green, yellow circles for different classifications)X
36
Media1.4.2AFor autoplaying audio that lasts longer than 3 seconds, the player must have a pause or stop control OR a volume controlX
37
Color1.4.3AAThe color contrast of text and its background must meet the appropriate contrast minimumX
38
Presentation1.4.4AAText resizing must not be disabledX
39
Presentation1.4.4AAPinch-to-zoom must not be disabledX
40
Presentation1.4.4AAWhen text resized to 200%, no page content or information is lostX
41
Presentation1.4.4AAWhen text resized to 200%, interactive elements must still be activatableX
42
Images1.4.5AAImages are not used to communicate text when plain-text can be usedX
43
Presentation1.4.10AAWhen view zoomed to 400%, user should only have to scroll vertically (for horizontal text) or horizontally (for vertical text) unless it affects usage or meaning (e.g. images, maps, diagrams, video games, presentations, data tables, toolbars)X
44
Color1.4.11AAVisual information required to identify UI components (e.g. buttons, inputs) or understand graphical content (e.g. image icons) has a color contrast ratio at least 3:1 except when essentialX
45
Presentation1.4.12AAWhen text styled using the linked bookmarklet, no page content or information is lost - https://www.html5accessibility.com/tests/tsbookmarklet.htmlX
46
Interaction1.4.13AAExcept for title attributes, non-modal content that is revealed on hover or focus can be dismissed without having to move the mouse pointer or keyboard focus whether the user is using mouse, keyboard, screen reader, or zoomed contentX
47
Interaction1.4.13AAExcept for title attributes, non-modal content that is revealed on hover or focus is not dismissed when the mouse pointer is moved off of the trigger and onto the revealed contentX
48
Interaction1.4.13AAExcept for title attributes, non-modal content that is revealed on hover or focus is not dismissed until it is not validX
49
Keyboard2.1.1AAll interactive elements can be used with keyboardX
50
Keyboard2.1.1AAll interactive elements are reachable with keyboard (in the tab order, part of a widget, keyboard command, or have alternative method to do the same thing)X
51
Keyboard2.1.1ANon-interactive elements are not reachable with keyboard alone
52
Keyboard2.1.1ATimed keyboard interactions (e.g. "double-clicking" a key) are not requiredX
53
Keyboard2.1.1AContent available on hover is also available via keyboard (e.g. on keyboard focus or activating a button or other control)X
54
Keyboard2.1.2AAll interactive elements can be navigated away from using a standard escape method (tab, shift+tab, arrow keys, Esc, etc.)X
55
2.1.4ASingle-character shortcuts can be disabled, customized, or only work when a particular element has focusX
56
Time Limit2.2.1ANon-essential time limits (that are less than 20 hours) can be turned off, adjusted, or extended.X
57
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.X
58
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.X
59
Sensory2.3.1AContent on the page doesn't flash more than 3 times in a second.X
60
Structure2.4.1APages with headers, navigations, or similar blocks of repeated content before the main content provide a "skip to main content" link.X
61
Structure2.4.2APages (including pages in iframes) must have non-empty title elementsX
62
Structure2.4.2APage title elements must be unique within their site/subsiteX
63
Structure2.4.2APage title elements must be descriptive of the content of their pageX
64
Structure2.4.2AIframes must have non-empty title attributesX
65
Structure2.4.2AIframe title attributes must be unique and descriptiveX
66
Keyboard2.4.3AFocus order must closely (but not necessarily exactly) follow the visual design of the pageX
67
Keyboard2.4.3AIf positive tabindex attributes are used, the meaning and operability of the page must be preservedX
68
Keyboard2.4.3ACustom components and elements must manage focus logically (e.g. moving focus into modal dialog)X
69
Keyboard2.4.3AKeyboard focus must not be lostX
70
Links2.4.4ALink 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.X
71
Structure2.4.5AAFor 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)X
72
Structure2.4.6AAHeadings must be descriptive of their contentX
73
Forms2.4.6AALabels must be descriptive of their componentX
74
Keyboard2.4.7AAItems in the focus order must have a visible focus indicatorX
75
Interaction2.5.1AA simple single-pointer (e.g. finger) without a path (e.g. not dragging) gesture or button exists for each multiple-pointer, complex, or path-based gesture unless using a multiple-pointer, complex, or path-based gesture is essentialX
76
Interaction2.5.2AFor button presses or single finger tap actions, either the down-event does not execute the function, the up-event reverses the execution of the function, the user can cancel execution of the function before the up-event triggers execution of the function, or down-event execution of the function is essential.X
77
Interaction2.5.3AProgrammatic labels contain (or at least start with) the same text used in the visible labelX
78
Interaction2.5.4AA UI component exists for each motion control unless motion controls are essential or used by assistive technologyX
79
Interaction2.5.4AMotion controls can be disabled unless essential or used by assistive technologyX
80
Structure3.1.1AThe default language of the page must be specifiedX
81
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 textX
82
Interaction3.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)X
83
Interaction3.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)X
84
Consistency3.2.3AANavigation on the site or within a set of pages must be presented in the same orderX
85
Consistency3.2.4AAComponents on the site or within a set of pages must have similar labeling and functionalityX
86
Forms3.3.1AInline error messages must be announced to screen reader users when displayed visuallyX
87
Form Info3.3.1AError messages after form submission must be announced to screen readers when displayed visuallyX
88
Form Info3.3.1AInstructional information helpful for completing an input must be programmatically associated with the inputX
89
Forms3.3.2AInputs and controls must have visible labels (not to be confused with visible text labels)X
90
Forms3.3.2AGroups of inputs must have visible labels (not to be confused with visible text labels)X
91
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)X
92
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)X
93
Form Info3.3.3AAInline error messages must be programmatically associated with the inputX
94
Forms3.3.4AAFor 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.X
95
Code Quality4.1.1AElements must have required start and end tagsX
96
Code Quality4.1.1AElements must be nested according to specificationX
97
Code Quality4.1.1AElements must not have duplicate attributesX
98
Code Quality4.1.1AIDs must be uniqueX
99
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)X
100
Custom Elements
4.1.2ACustom elements and components must have a programmatically determinable name and roleX
Loading...