Checklist of all checks for doing a WCAG 2.0 AA accessibility audit.
| Category | Success 7D0C Criteria | Level | Description | Tool: aXe |
|---|---|---|---|---|
| Images | 1.1.1 | A | Images that present content must have a text alternative | X |
| Images | 1.1.1 | A | Active images must have a text alternative | X |
| Images | 1.1.1 | A | Text alternatives must be descriptive of the content | |
| Images | 1.1.1 | A | Decorative content must have a null text alternative | |
| Media | 1.2.1 | A | Prerecorded audio-only content has a transcript | |
| Media | 1.2.1 | A | Prerecorded video-only content has a transcript or audio description | |
| Media | 1.2.2 | A | Prerecorded video/audio content has captions | X |
| Media | 1.2.3 | A | Prerecorded video/audio content (that should have a transcript or audio description) has a transcript or audio description | |
| Media | 1.2.4 | AA | Live video/audio content (that should have captions) has captions | |
| Media | 1.2.5 | AA | Prerecorded video/audio content (that should have an audio description) has an audio description | X |
| Structure | 1.3.1 | A | Content serving the purpose of a semantic element must be programmaticaly discernable as that semantic element (headings, paragraphs, landmarks, tables, ordered/unordered/description lists, etc.) | |
| Structure | 1.3.1 | A | Content 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.) | |
| Forms | 1.3.1 | A | Inputs and controls must have programmatic labels | X |
| Forms | 1.3.1 | A | Groups of inputs must have programmatic group labels | X |
| Structure | 1.3.1 | A | Table header must be programmatically associated with their respective data cells | X |
| Structure | 1.3.2 | A | Visual content order matches programmatic content order when a mismatch would change or confuse the meaning | |
| Sensory | 1.3.3 | A | Do not use sensory characteristics alone (shape, size, visual location, orientation, or sound) to communicate instructions for page use | |
| Color | 1.4.1 | A | Color alone must not be used to distinguish between interactive text and non-interactive text | |
| Color | 1.4.1 | A | Color alone must not be used to distinguish between information presented in content (charts, graphs, etc.) | |
| Color | 1.4.1 | A | Color alone must not be used to communicate differences in content (e.g. red, green, yellow circles for different classifications) | |
| Media | 1.4.2 | A | For autoplaying audio that lasts longer than 3 seconds, the player must have a pause or stop control OR a volume control | |
| Color | 1.4.3 | AA | The color contrast of text and its background must meet the appropriate contrast minimum | X |
| Presentation | 1.4.4 | AA | Text resizing must not be disabled | |
| Presentation | 1.4.4 | AA | Pinch-to-zoom must not be disabled | X |
| Presentation | 1.4.4 | AA | When text resized to 200%, no page content or information is lost | |
| Presentation | 1.4.4 | AA | When text resized to 200%, interactive elements must still be activateable | |
| Images | 1.4.5 | AA | Images are not used to communicate text when plain-text can be used | |
| Keyboard | 2.1.1 | A | All interactive elements can be activated with keyboard | |
| Keyboard | 2.1.1 | A | Timed keyboard interactions (e.g. "double-clicking" a key) are not required | |
| Keyboard | 2.1.2 | A | All interactive elements can be navigated away from using a standard escape method (tab, shift+tab, arrow keys, Esc, etc.) | |
| Time Limit | 2.2.1 | A | Non-essential time limits (that are less than 20 hours) can be turned off, adjusted, or extended. | |
| Sensory | 2.2.2 | A | 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. | |
| Sensory | 2.2.2 | A | 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. | |
| Sensory | 2.3.1 | A | Content on the page doesn't flash more than 3 times in a second. | |
| Structure | 2.4.1 | A | Pages with headers, navigations, or similar blocks of repeated content before the main content provide a "skip to main content" link. | |
| Structure | 2.4.2 | A | The title element for the page (including pages in iframes) is not empty | X |
| Structure | 2.4.2 | A | Iframes have title attributes | X |
| Structure | 2.4.2 | A | Iframes have unique and descriptive title attributes | |
| Structure | 2.4.2 | A | The values for title (both elements and attributes) are unique and descriptive of the content of the page | |
| Keyboard | 2.4.3 | A | Focus order must closely (but not necessarily exactly) follow the visual design of the page | |
| Keyboard | 2.4.3 | A | If positive tabindex attributes are used, the meaning and operability of the page must be preserved | |
| Keyboard | 2.4.3 | A | Custom components and elements must manage focus logically | |
| Links | 2.4.4 | A | Unambiguous 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. | |
| Structure | 2.4.5 | AA | 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) | |
| Structure | 2.4.6 | AA | Headings must be descripive of their content | |
| Forms | 2.4.6 | AA | Labels must be descriptive of their component | |
| Keyboard | 2.4.7 | AA | Items in the focus order must have a visible focus indicator | |
| Structure | 3.1.1 | A | The default language of the page must be specified | X |
| Structure | 3.1.2 | AA | 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 | |
| Context | 3.2.1 | A | 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) | |
| Context | 3.2.2 | A | 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) | |
| Consistency | 3.2.3 | AA | Navigation on the site or within a set of pages must be presented in the same order | |
| Consistency | 3.2.4 | AA | Components on the site or within a set of pages must have similar labeling and functionality | |
| Forms | 3.3.1 | A | Inline error messages must be announced to screen reader users when displayed visually | |
| Form Info | 3.3.1 | A | Error messages after form submission must be announced to screen readers when displayed visually | |
| Form Info | 3.3.1 | A | Instructional information helpful for completing an input must be programmatically associated with the input | |
| Forms | 3.3.2 | A | Inputs and controls must have visible labels (not to be confused with visible text labels) | |
| Forms | 3.3.2 | A | Groups of inputs must have visible labels (not to be confused with visible text labels) | |
| Form Info | 3.3.3 | AA | 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) | |
| Form Info | 3.3.3 | AA | Error messages must be descriptive enough to help the user resolve the issue without compromising security (e.g. providing details about a password) | |
| Form Info | 3.3.3 | AA | Inline error messages must be programmatically associated with the input | |
| Forms | 3.3.4 | AA | 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. | |
| Code Quality | 4.1.1 | A | Elements must have required start and end tags | |
| Code Quality | 4.1.1 | A | Elements must be nested according to specification | |
| Code Quality | 4.1.1 | A | Elements must not have duplicate attributes | |
| Code Quality | 4.1.1 | A | IDs must be unique | X |
| Code Quality | 4.1.1 | A | Names of elements and attributes must be free of errors (e.g. An "image" tag marked up as instead of |
|
| Custom Elements | 4.1.2 | A | Custom elements and components must have a programmatically determinable name and role | |
| Custom Elements | 4.1.2 | A | Custom element and component states, values, and properties must be programmatically discernable |