ABCDEFG
1
CategoryDescriptionLink to testing documentationWCAG 2.0WCAG 2.1Level
Success Criteria
2
ImagesImages that present content must have a text alternativehttps://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructions
https://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructions-2
https://section508coordinators.github.io/ICTTestingBaseline/18Stylesheet.html#test-instructions
A1.1.1
3
ImagesActive images must have a text alternativehttps://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructionsA1.1.1
4
ImagesText alternatives must be descriptive of the contenthttps://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructionsA1.1.1
5
ImagesDecorative content must have a null text alternativehttps://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructions-1A1.1.1
6
MediaPrerecorded audio-only content has a transcripthttps://section508coordinators.github.io/ICTTestingBaseline/16AudioVideo.html#test-instructionsA1.2.1
7
MediaPrerecorded video-only content has a transcript or audio descriptionhttps://section508coordinators.github.io/ICTTestingBaseline/16AudioVideo.html#test-instructions-1A1.2.1
8
MediaPrerecorded video/audio content has captionshttps://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-3A1.2.2
9
MediaCaptions match all spoken content in prerecorded video/audiohttps://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-3A1.2.2
10
MediaCaptions adequately describe all unspoken content needed to understand the prerecorded video/audiohttps://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-3A1.2.2
11
MediaPrerecorded video/audio content (that should have a transcript or audio description) has a transcript or audio descriptionusually overriden by 1.2.5A1.2.3
12
MediaLive video/audio content (that should have captions) has captionshttps://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-5AA1.2.4
13
MediaPrerecorded video/audio content (that should have an audio description) has an audio descriptionhttps://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-4AA1.2.5
14
MediaAudio descriptions adequately describe all visual content needed to understand the prerecorded video/audiohttps://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-4AA1.2.5
15
StructureGroups of content presented as sections, regions, or landmarks (header, footer, main content,
etc.) should be recognized as landmarks by assistive technology
A1.3.1
16
StructureContent not presented as page sections, regions, or landmarks (header, footer, main content,
etc.) should not be recognized as landmarks by assistive technology
A1.3.1
17
StructureIf 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
A1.3.1
18
StructureHeadings must not be emptyA1.3.1
19
StructureText presented as a heading should be recognized as a heading by assistive technologyhttps://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-1A1.3.1
20
StructureText not presented as a heading should not be recognized as a heading by assistive technologyhttps://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-2A1.3.1
21
StructureText presented as a heading should be recognized as the appropriate level of heading by assistive technologyhttps://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-1A1.3.1
22
StructureContent presented as a list should be recognized as a list by assistive technologyhttps://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-3A1.3.1
23
StructureContent not presented as a list should not be recognized as a list by assistive technologyA1.3.1
24
StructureContent presented as a list is recognized as the appropriate type of list by assistive technologyhttps://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-3A1.3.1
25
StructurePerceivable content that is not normally recognizable by assistive technology (ex. strikethrough text) is made recognizable by assistive technology.A1.3.1
26
StructureData tables should be recognized as tables by assistive technologyhttps://section508coordinators.github.io/ICTTestingBaseline/12DataTables.html#test-instructionsA1.3.1
27
StructureLayout tables should not be recognized as tables by assistive technologyhttps://section508coordinators.github.io/ICTTestingBaseline/12DataTables.html#test-instructionsA1.3.1
28
StructureSemantic elements must not be used only for aesthetic purposes (e.g. using fieldset to put content inside a box)A1.3.1
29
FormsNative inputs and controls must have programmatic labelshttps://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructionsA1.3.1
30
FormsInstructions for form elements must be programmatically associated with its form elementA1.3.1
31
FormsGroups of related native inputs must have programmatic group labels (especially radio and checkbox groups)A1.3.1
32
StructureTable headers must be programmatically associated with their respective data cellshttps://section508coordinators.github.io/ICTTestingBaseline/12DataTables.html#test-instructionsA1.3.1
33
StructureVisual content order matches programmatic content order when a mismatch would change or confuse the meaninghttps://section508coordinators.github.io/ICTTestingBaseline/18Stylesheet.html#test-instructions-1A1.3.2
34
SensoryDo not use sensory characteristics alone (shape, size, visual location, or sound) to communicate instructions for page usehttps://section508coordinators.github.io/ICTTestingBaseline/07Sensory.html#test-instructions-1A1.3.3
35
SensoryDo not rely on visual positioning of form inputs to communicate how to complete form inputs (i.e. "fill in the blank" style text inputs)A1.3.3
36
SensoryContent adjusts to the device orientation unless it is considered essentialA1.3.4
37
SensoryWhen auto-rotate setting is disabled (orientation is locked), content does not adjust to the device orientation unless it is considered essentialA1.3.4
38
FormsText 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-purposesAA1.3.5
39
ColorColor alone must not be used to distinguish between interactive text and non-interactive texthttps://section508coordinators.github.io/ICTTestingBaseline/07Sensory.html#test-instructionsA1.4.1
40
ColorColor alone must not be used to distinguish between information presented in content (charts, graphs, etc.)https://section508coordinators.github.io/ICTTestingBaseline/07Sensory.html#test-instructionsA1.4.1
41
ColorColor alone must not be used to communicate differences in content (e.g. red, green, yellow circles for different classifications)https://section508coordinators.github.io/ICTTestingBaseline/07Sensory.html#test-instructionsA1.4.1
42
MediaFor autoplaying audio that lasts longer than 3 seconds, the player must have a pause or stop control or the player must have a volume controlhttps://section508coordinators.github.io/ICTTestingBaseline/21TimedEvents.html#test-instructions-3A1.4.2
43
ColorThe color contrast of text and its background must meet the appropriate contrast minimumhttps://section508coordinators.github.io/ICTTestingBaseline/08Contrast.html#test-instructionsAA1.4.3
44
PresentationText resizing must not be disabledAA1.4.4
45
PresentationPinch-to-zoom must not be disabledAA1.4.4
46
PresentationWhen text resized to 200%, no page content or information is losthttps://section508coordinators.github.io/ICTTestingBaseline/22Resize.html#test-instructionsAA1.4.4
47
PresentationWhen text resized to 200%, interactive elements must still be activatablehttps://section508coordinators.github.io/ICTTestingBaseline/22Resize.html#test-instructionsAA1.4.4
48
FormsText-based form controls must resize to accomodate text resizingAA1.4.4
49
ImagesImages are not used to communicate text when plain-text can be usedhttps://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructions-3AA1.4.5
50
PresentationWhen 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)AA1.4.10
51
ColorVisual 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 essentialAA1.4.11
52
PresentationWhen text styled using the linked bookmarklet, no page content or information is lost - https://www.html5accessibility.com/tests/tsbookmarklet.htmlAA1.4.12
53
InteractionExcept 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 contentAA1.4.13
54
InteractionExcept 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 contentAA1.4.13
55
InteractionExcept for title attributes, non-modal content that is revealed on hover or focus is not dismissed until it is not valid or the user dismissed it (by removing hover or focus or some other method)AA1.4.13
56
KeyboardAll 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) and can be used with keyboardhttps://section508coordinators.github.io/ICTTestingBaseline/01Keyboard.html#test-instructionsA2.1.1
57
KeyboardNon-interactive elements are not reachable with keyboardA2.1.1
58
KeyboardTimed keyboard interactions (e.g. "double-clicking" a key) are not requiredhttps://section508coordinators.github.io/ICTTestingBaseline/01Keyboard.html#test-instructionsA2.1.1
59
KeyboardContent available on hover is also available via keyboard (e.g. on keyboard focus or activating a button or other control)A2.1.1
60
KeyboardAll interactive elements can be navigated away from using a standard escape method (tab, shift+tab, arrow keys, Esc, etc.)https://section508coordinators.github.io/ICTTestingBaseline/01Keyboard.html#test-instructions-1A2.1.2
61
KeyboardKeyboard shortcuts can be disabled, customized, or only work when a particular element has focusA2.1.4
62
Time LimitNon-essential time limits (that are less than 20 hours) can be turned off, adjusted, or extended.https://section508coordinators.github.io/ICTTestingBaseline/21TimedEvents.html#test-instructionsA2.2.1
63
SensoryMoving, 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.https://section508coordinators.github.io/ICTTestingBaseline/21TimedEvents.html#test-instructions-1A2.2.2
64
SensoryAuto-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.https://section508coordinators.github.io/ICTTestingBaseline/21TimedEvents.html#test-instructions-2A2.2.2
65
SensoryContent on the page doesn't flash more than 3 times in a second.https://section508coordinators.github.io/ICTTestingBaseline/09Flashing.html#test-instructionsA2.3.1
66
StructurePages with headers, navigations, or similar blocks of repeated content before the main content provide a "skip to main content" link.https://section508coordinators.github.io/ICTTestingBaseline/04RepetitiveContent.html#test-instructionsA2.4.1
67
StructurePages (including pages in iframes) must have non-empty title elementshttps://section508coordinators.github.io/ICTTestingBaseline/11PageTitles.html#test-instructionsA2.4.2
68
StructurePage title elements must be unique within their site/subsitehttps://section508coordinators.github.io/ICTTestingBaseline/11PageTitles.html#test-instructionsA2.4.2
69
StructurePage title elements must be descriptive of the content of their pagehttps://section508coordinators.github.io/ICTTestingBaseline/11PageTitles.html#test-instructionsA2.4.2
70
StructureIframes must have non-empty title attributeshttps://section508coordinators.github.io/ICTTestingBaseline/19Frames.html#test-instructionsA2.4.2
71
StructureIframe title attributes must be unique and descriptivehttps://section508coordinators.github.io/ICTTestingBaseline/19Frames.html#test-instructionsA2.4.2
72
KeyboardFocus order must closely (but not necessarily exactly) follow the visual design of the pagehttps://section508coordinators.github.io/ICTTestingBaseline/03FocusOrder.html#test-instructionsA2.4.3
73
KeyboardIf positive tabindex attributes are used, the meaning and operability of the page must be preservedA2.4.3
74
KeyboardCustom components and elements must manage focus logically (e.g. moving focus into modal dialog)https://section508coordinators.github.io/ICTTestingBaseline/03FocusOrder.html#test-instructionsA2.4.3
75
KeyboardKeyboard focus must not be losthttps://section508coordinators.github.io/ICTTestingBaseline/03FocusOrder.html#test-instructionsA2.4.3
76
LinksLink 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.https://section508coordinators.github.io/ICTTestingBaseline/14Links.html#test-instructionsA2.4.4
77
StructureFor 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)https://section508coordinators.github.io/ICTTestingBaseline/23MultipleWays.html#test-instructionsAA2.4.5
78
StructureHeadings must be descriptive of their contenthttps://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1
https://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions
AA2.4.6
79
FormsLabels must be descriptive of their componenthttps://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1AA2.4.6
80
KeyboardItems in the focus order must have a visible focus indicatorhttps://section508coordinators.github.io/ICTTestingBaseline/02FocusVisible.html#tests-instructionsAA2.4.7
81
InteractionA 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 essentialA2.5.1
82
InteractionFor 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.A2.5.2
83
InteractionProgrammatic labels contain (or at least start with) the same text used in the visible labelA2.5.3
84
InteractionA UI component exists for each motion control unless motion controls are essential or used by assistive technologyA2.5.4
85
InteractionMotion controls can be disabled unless essential or used by assistive technologyA2.5.4
86
StructureThe default language of the page must be specifiedhttps://section508coordinators.github.io/ICTTestingBaseline/15Language.html#test-instructionsA3.1.1
87
StructureContent 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 texthttps://section508coordinators.github.io/ICTTestingBaseline/15Language.html#test-instructions-1AA3.1.2
88
InteractionWhen 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)https://section508coordinators.github.io/ICTTestingBaseline/03FocusOrder.html#test-instructions-1A3.2.1
89
InteractionWhen 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)https://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1#test-instructions-2A3.2.2
90
ConsistencyNavigation on the site or within a set of pages must be presented in the same orderhttps://section508coordinators.github.io/ICTTestingBaseline/04RepetitiveContent.html#test-instructions-1AA3.2.3
91
ConsistencyComponents on the site or within a set of pages must have similar labeling and functionalityhttps://section508coordinators.github.io/ICTTestingBaseline/04RepetitiveContent.html#test-instructions-2AA3.2.4
92
FormsInline error messages must be announced to screen reader users when displayed visuallyhttps://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1#test-instructions-3A3.3.1
93
Form InfoError messages after form submission must be announced to screen readers when displayed visuallyA3.3.1
94
Form InfoInputs must have instructions necessary to complete an input (i.e. sample date format, type of name "first" "last" "full")A3.3.2
95
FormsInputs and controls must have visible labels (not to be confused with visible text labels)A3.3.2
96
FormsGroups of inputs must have visible labels (not to be confused with visible text labels)A3.3.2
97
Form InfoRequired 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)https://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1#test-instructions-5AA3.3.3
98
Form InfoError messages must be descriptive enough to help the user resolve the issue without compromising security (e.g. providing details about a password)https://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1#test-instructions-5AA3.3.3
99
Form InfoInline error messages must be programmatically associated with the inputAA3.3.3
100
FormsFor 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.https://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1#test-instructions-6AA3.3.4