| A | B | C | D | E | F | G | |
|---|---|---|---|---|---|---|---|
1 | Category | Description | Link to testing documentation | WCAG 2.0 | WCAG 2.1 | Level | Success Criteria |
2 | Images | Images that present content must have a text alternative | https://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 | A | 1.1.1 | ||
3 | Images | Active images must have a text alternative | https://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructions | A | 1.1.1 | ||
4 | Images | Text alternatives must be descriptive of the content | https://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructions | A | 1.1.1 | ||
5 | Images | Decorative content must have a null text alternative | https://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructions-1 | A | 1.1.1 | ||
6 | Media | Prerecorded audio-only content has a transcript | https://section508coordinators.github.io/ICTTestingBaseline/16AudioVideo.html#test-instructions | A | 1.2.1 | ||
7 | Media | Prerecorded video-only content has a transcript or audio description | https://section508coordinators.github.io/ICTTestingBaseline/16AudioVideo.html#test-instructions-1 | A | 1.2.1 | ||
8 | Media | Prerecorded video/audio content has captions | https://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-3 | A | 1.2.2 | ||
9 | Media | Captions match all spoken content in prerecorded video/audio | https://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-3 | A | 1.2.2 | ||
10 | Media | Captions adequately describe all unspoken content needed to understand the prerecorded video/audio | https://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-3 | A | 1.2.2 | ||
11 | Media | Prerecorded video/audio content (that should have a transcript or audio description) has a transcript or audio description | usually overriden by 1.2.5 | A | 1.2.3 | ||
12 | Media | Live video/audio content (that should have captions) has captions | https://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-5 | AA | 1.2.4 | ||
13 | Media | Prerecorded video/audio content (that should have an audio description) has an audio description | https://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-4 | AA | 1.2.5 | ||
14 | Media | Audio descriptions adequately describe all visual content needed to understand the prerecorded video/audio | https://section508coordinators.github.io/ICTTestingBaseline/17SyncMedia.html#test-instructions-4 | AA | 1.2.5 | ||
15 | Structure | Groups of content presented as sections, regions, or landmarks (header, footer, main content, etc.) should be recognized as landmarks by assistive technology | A | 1.3.1 | |||
16 | Structure | Content not presented as page sections, regions, or landmarks (header, footer, main content, etc.) should not be recognized as landmarks by assistive technology | A | 1.3.1 | |||
17 | Structure | If 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 | A | 1.3.1 | |||
18 | Structure | Headings must not be empty | A | 1.3.1 | |||
19 | Structure | Text presented as a heading should be recognized as a heading by assistive technology | https://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-1 | A | 1.3.1 | ||
20 | Structure | Text not presented as a heading should not be recognized as a heading by assistive technology | https://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-2 | A | 1.3.1 | ||
21 | Structure | Text presented as a heading should be recognized as the appropriate level of heading by assistive technology | https://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-1 | A | 1.3.1 | ||
22 | Structure | Content presented as a list should be recognized as a list by assistive technology | https://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-3 | A | 1.3.1 | ||
23 | Structure | Content not presented as a list should not be recognized as a list by assistive technology | A | 1.3.1 | |||
24 | Structure | Content presented as a list is recognized as the appropriate type of list by assistive technology | https://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions-3 | A | 1.3.1 | ||
25 | Structure | Perceivable content that is not normally recognizable by assistive technology (ex. strikethrough text) is made recognizable by assistive technology. | A | 1.3.1 | |||
26 | Structure | Data tables should be recognized as tables by assistive technology | https://section508coordinators.github.io/ICTTestingBaseline/12DataTables.html#test-instructions | A | 1.3.1 | ||
27 | Structure | Layout tables should not be recognized as tables by assistive technology | https://section508coordinators.github.io/ICTTestingBaseline/12DataTables.html#test-instructions | A | 1.3.1 | ||
28 | Structure | Semantic elements must not be used only for aesthetic purposes (e.g. using fieldset to put content inside a box) | A | 1.3.1 | |||
29 | Forms | Native inputs and controls must have programmatic labels | https://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions | A | 1.3.1 | ||
30 | Forms | Instructions for form elements must be programmatically associated with its form element | A | 1.3.1 | |||
31 | Forms | Groups of related native inputs must have programmatic group labels (especially radio and checkbox groups) | A | 1.3.1 | |||
32 | Structure | Table headers must be programmatically associated with their respective data cells | https://section508coordinators.github.io/ICTTestingBaseline/12DataTables.html#test-instructions | A | 1.3.1 | ||
33 | Structure | Visual content order matches programmatic content order when a mismatch would change or confuse the meaning | https://section508coordinators.github.io/ICTTestingBaseline/18Stylesheet.html#test-instructions-1 | A | 1.3.2 | ||
34 | Sensory | Do not use sensory characteristics alone (shape, size, visual location, or sound) to communicate instructions for page use | https://section508coordinators.github.io/ICTTestingBaseline/07Sensory.html#test-instructions-1 | A | 1.3.3 | ||
35 | Sensory | Do not rely on visual positioning of form inputs to communicate how to complete form inputs (i.e. "fill in the blank" style text inputs) | A | 1.3.3 | |||
36 | Sensory | Content adjusts to the device orientation unless it is considered essential | A | 1.3.4 | |||
37 | Sensory | When auto-rotate setting is disabled (orientation is locked), content does not adjust to the device orientation unless it is considered essential | A | 1.3.4 | |||
38 | Forms | Text 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-purposes | AA | 1.3.5 | |||
39 | Color | Color alone must not be used to distinguish between interactive text and non-interactive text | https://section508coordinators.github.io/ICTTestingBaseline/07Sensory.html#test-instructions | A | 1.4.1 | ||
40 | Color | Color alone must not be used to distinguish between information presented in content (charts, graphs, etc.) | https://section508coordinators.github.io/ICTTestingBaseline/07Sensory.html#test-instructions | A | 1.4.1 | ||
41 | Color | Color 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-instructions | A | 1.4.1 | ||
42 | Media | For autoplaying audio that lasts longer than 3 seconds, the player must have a pause or stop control or the player must have a volume control | https://section508coordinators.github.io/ICTTestingBaseline/21TimedEvents.html#test-instructions-3 | A | 1.4.2 | ||
43 | Color | The color contrast of text and its background must meet the appropriate contrast minimum | https://section508coordinators.github.io/ICTTestingBaseline/08Contrast.html#test-instructions | AA | 1.4.3 | ||
44 | Presentation | Text resizing must not be disabled | AA | 1.4.4 | |||
45 | Presentation | Pinch-to-zoom must not be disabled | AA | 1.4.4 | |||
46 | Presentation | When text resized to 200%, no page content or information is lost | https://section508coordinators.github.io/ICTTestingBaseline/22Resize.html#test-instructions | AA | 1.4.4 | ||
47 | Presentation | When text resized to 200%, interactive elements must still be activatable | https://section508coordinators.github.io/ICTTestingBaseline/22Resize.html#test-instructions | AA | 1.4.4 | ||
48 | Forms | Text-based form controls must resize to accomodate text resizing | AA | 1.4.4 | |||
49 | Images | Images are not used to communicate text when plain-text can be used | https://section508coordinators.github.io/ICTTestingBaseline/06Images.html#test-instructions-3 | AA | 1.4.5 | ||
50 | Presentation | When 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) | AA | 1.4.10 | |||
51 | Color | Visual 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 essential | AA | 1.4.11 | |||
52 | Presentation | When text styled using the linked bookmarklet, no page content or information is lost - https://www.html5accessibility.com/tests/tsbookmarklet.html | AA | 1.4.12 | |||
53 | Interaction | Except 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 content | AA | 1.4.13 | |||
54 | Interaction | Except 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 content | AA | 1.4.13 | |||
55 | Interaction | Except 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) | AA | 1.4.13 | |||
56 | Keyboard | All 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 keyboard | https://section508coordinators.github.io/ICTTestingBaseline/01Keyboard.html#test-instructions | A | 2.1.1 | ||
57 | Keyboard | Non-interactive elements are not reachable with keyboard | A | 2.1.1 | |||
58 | Keyboard | Timed keyboard interactions (e.g. "double-clicking" a key) are not required | https://section508coordinators.github.io/ICTTestingBaseline/01Keyboard.html#test-instructions | A | 2.1.1 | ||
59 | Keyboard | Content available on hover is also available via keyboard (e.g. on keyboard focus or activating a button or other control) | A | 2.1.1 | |||
60 | Keyboard | All 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-1 | A | 2.1.2 | ||
61 | Keyboard | Keyboard shortcuts can be disabled, customized, or only work when a particular element has focus | A | 2.1.4 | |||
62 | Time Limit | Non-essential time limits (that are less than 20 hours) can be turned off, adjusted, or extended. | https://section508coordinators.github.io/ICTTestingBaseline/21TimedEvents.html#test-instructions | A | 2.2.1 | ||
63 | Sensory | Moving, 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-1 | A | 2.2.2 | ||
64 | Sensory | Auto-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-2 | A | 2.2.2 | ||
65 | Sensory | Content on the page doesn't flash more than 3 times in a second. | https://section508coordinators.github.io/ICTTestingBaseline/09Flashing.html#test-instructions | A | 2.3.1 | ||
66 | Structure | Pages 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-instructions | A | 2.4.1 | ||
67 | Structure | Pages (including pages in iframes) must have non-empty title elements | https://section508coordinators.github.io/ICTTestingBaseline/11PageTitles.html#test-instructions | A | 2.4.2 | ||
68 | Structure | Page title elements must be unique within their site/subsite | https://section508coordinators.github.io/ICTTestingBaseline/11PageTitles.html#test-instructions | A | 2.4.2 | ||
69 | Structure | Page title elements must be descriptive of the content of their page | https://section508coordinators.github.io/ICTTestingBaseline/11PageTitles.html#test-instructions | A | 2.4.2 | ||
70 | Structure | Iframes must have non-empty title attributes | https://section508coordinators.github.io/ICTTestingBaseline/19Frames.html#test-instructions | A | 2.4.2 | ||
71 | Structure | Iframe title attributes must be unique and descriptive | https://section508coordinators.github.io/ICTTestingBaseline/19Frames.html#test-instructions | A | 2.4.2 | ||
72 | Keyboard | Focus order must closely (but not necessarily exactly) follow the visual design of the page | https://section508coordinators.github.io/ICTTestingBaseline/03FocusOrder.html#test-instructions | A | 2.4.3 | ||
73 | Keyboard | If positive tabindex attributes are used, the meaning and operability of the page must be preserved | A | 2.4.3 | |||
74 | Keyboard | Custom components and elements must manage focus logically (e.g. moving focus into modal dialog) | https://section508coordinators.github.io/ICTTestingBaseline/03FocusOrder.html#test-instructions | A | 2.4.3 | ||
75 | Keyboard | Keyboard focus must not be lost | https://section508coordinators.github.io/ICTTestingBaseline/03FocusOrder.html#test-instructions | A | 2.4.3 | ||
76 | Links | 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. | https://section508coordinators.github.io/ICTTestingBaseline/14Links.html#test-instructions | A | 2.4.4 | ||
77 | Structure | 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) | https://section508coordinators.github.io/ICTTestingBaseline/23MultipleWays.html#test-instructions | AA | 2.4.5 | ||
78 | Structure | Headings must be descriptive of their content | https://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1 https://section508coordinators.github.io/ICTTestingBaseline/13Structure.html#test-instructions | AA | 2.4.6 | ||
79 | Forms | Labels must be descriptive of their component | https://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1 | AA | 2.4.6 | ||
80 | Keyboard | Items in the focus order must have a visible focus indicator | https://section508coordinators.github.io/ICTTestingBaseline/02FocusVisible.html#tests-instructions | AA | 2.4.7 | ||
81 | Interaction | A 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 essential | A | 2.5.1 | |||
82 | Interaction | For 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. | A | 2.5.2 | |||
83 | Interaction | Programmatic labels contain (or at least start with) the same text used in the visible label | A | 2.5.3 | |||
84 | Interaction | A UI component exists for each motion control unless motion controls are essential or used by assistive technology | A | 2.5.4 | |||
85 | Interaction | Motion controls can be disabled unless essential or used by assistive technology | A | 2.5.4 | |||
86 | Structure | The default language of the page must be specified | https://section508coordinators.github.io/ICTTestingBaseline/15Language.html#test-instructions | A | 3.1.1 | ||
87 | Structure | Content 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 | https://section508coordinators.github.io/ICTTestingBaseline/15Language.html#test-instructions-1 | AA | 3.1.2 | ||
88 | Interaction | When 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-1 | A | 3.2.1 | ||
89 | Interaction | When 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-2 | A | 3.2.2 | ||
90 | Consistency | Navigation on the site or within a set of pages must be presented in the same order | https://section508coordinators.github.io/ICTTestingBaseline/04RepetitiveContent.html#test-instructions-1 | AA | 3.2.3 | ||
91 | Consistency | Components on the site or within a set of pages must have similar labeling and functionality | https://section508coordinators.github.io/ICTTestingBaseline/04RepetitiveContent.html#test-instructions-2 | AA | 3.2.4 | ||
92 | Forms | Inline error messages must be announced to screen reader users when displayed visually | https://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1#test-instructions-3 | A | 3.3.1 | ||
93 | Form Info | Error messages after form submission must be announced to screen readers when displayed visually | A | 3.3.1 | |||
94 | Form Info | Inputs must have instructions necessary to complete an input (i.e. sample date format, type of name "first" "last" "full") | A | 3.3.2 | |||
95 | Forms | Inputs and controls must have visible labels (not to be confused with visible text labels) | A | 3.3.2 | |||
96 | Forms | Groups of inputs must have visible labels (not to be confused with visible text labels) | A | 3.3.2 | |||
97 | Form Info | Required 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-5 | AA | 3.3.3 | ||
98 | Form Info | Error 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-5 | AA | 3.3.3 | ||
99 | Form Info | Inline error messages must be programmatically associated with the input | AA | 3.3.3 | |||
100 | Forms | 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. | https://section508coordinators.github.io/ICTTestingBaseline/10Forms.html#test-instructions#test-instructions-1#test-instructions-6 | AA | 3.3.4 |