Accessibility checklist and guidance for developers
| Success criteria | Level | Description | Interaction | Severity | Responsibility | Knowledge to test | Time to test | Test procedure |
|---|---|---|---|---|---|---|---|---|
| Success criteria 1.1.1 Non-text Content | Level A | Description Images that convey meaning have suitable alternative text and images that serve a decorative purpose have a null alternative text assigned | Interaction Screen reader | Severity Minor, Moderate, Severe |
Responsibility Content, Developer |
Knowledge to test Medium | Time to test Medium |
Test procedure ARC Toolkit, Manual, Some support from tools, Screen reader |
| Success criteria 1.3.1 Info and Relationships | Level A | Description Font icons are not used | Interaction Contrast | Severity |
Responsibility Designer, Developer |
Knowledge to test Medium | Time to test |
Test procedure Manual, Request details, Web inspector tools |
| Success criteria 1.3.1 Info and Relationships | Level A | Description Form code is implemented correctly | Interaction Screen reader | Severity Minor, Moderate, Severe | Responsibility Developer | Knowledge to test Medium | Time to test Medium |
Test procedure ARC Toolkit, Manual, Screen reader, Some support from tools, Web developer extension |
| Success criteria 1.3.1 Info and Relationships | Level A | Description The HTML structure and semantices reflects the intent - landmarks, headings, lists, data tables | Interaction Screen reader | Severity Minor, Moderate, Severe |
Responsibility Content, Developer |
Knowledge to test Medium | Time to test Medium |
Test procedure ARC Toolkit, Manual, Screen reader, Some support from tools, Web inspector tool |
| Success criteria 1.3.1 Info and Relationships | Level A | Description Inline CSS is not used | Interaction Contrast, Magnification | Severity |
Responsibility Designer, Developer |
Knowledge to test | Time to test |
Test procedure Inspect code, Manual, Web inspector tools |
| Success criteria 1.3.2 Meaningful Sequence | Level A | Description Content is in a logical order in the code | Interaction Screen reader | Severity | Responsibility Developer | Knowledge to test | Time to test |
Test procedure Manual, Some support from tools, Web developer extension |
| Success criteria 1.3.4 Orientation | Level AA | Description Orientation is not locked | Interaction Mobile | Severity Severe | Responsibility Developer | Knowledge to test Easy | Time to test Quick |
Test procedure Manual, Mobile |
| Success criteria 1.3.5 Identity Input Purpose | Level AA | Description Autocomplete is used on inputs when appropriate | Interaction Cognition | Severity Moderate | Responsibility Developer | Knowledge to test | Time to test |
Test procedure ARC Toolkit, Manual, Web Inspector Tool |
| Success criteria 1.4.4 Resize Text | Level AA | Description You can make text at least 200% larger without losing content/functionality | Interaction Magnification | Severity | Responsibility Developer | Knowledge to test | Time to test |
Test procedure Browser, Manual |
| Success criteria 1.4.5 Images of Text | Level AA | Description Graphics are not used for text (except logos) | Interaction Magnification | Severity |
Responsibility Designer, Developer |
Knowledge to test Medium | Time to test Quick |
Test procedure ARC Toolkit, Manual, Some support from tools |
| Success criteria 1.4.10 Reflow | Level AA | Description You can zoom in 400% without losing content/functionality or horizontal scrolling | Interaction Magnification | Severity Moderate, Severe |
Responsibility Designer, Developer |
Knowledge to test Easy | Time to test Quick |
Test procedure ARC Toolkit, Bookmarklet, Browser, Manual, Some support from tools |
| Success criteria 1.4.12 Text Spacing | Level AA | Description The current text spacing can be overridden without loss of content or functionality | Interaction Magnification | Severity Severe | Responsibility Developer | Knowledge to test Easy | Time to test Quick |
Test procedure ARC Toolkit, Bookmarklet, Manual, Some support from tools |
| Success criteria 1.4.13 Content on Hover or Focus | Level AA | Description Pop-overs that appear on keyboard focus can be dismissed using the keyboard | Interaction Keyboard | Severity Moderate | Responsibility Developer | Knowledge to test Easy | Time to test Quick |
Test procedure Keyboard, Manual |
| Success criteria 1.4.13 Content on Hover or Focus | Level AA | Description Pop-ups are not used on hover, unless they are dismissable and robust | Interaction Magnification | Severity Severe | Responsibility Developer | Knowledge to test Easy | Time to test Quick |
Test procedure Cursor, Manual, Visual inspection |
| Success criteria 2.1.1 Keyboard | Level A | Description All functionality is operable with a keyboard | Interaction Keyboard | Severity Blocker | Responsibility Developer | Knowledge to test Medium | Time to test Medium |
Test procedure Keyboard, Manual, Some support from tools |
| Success criteria 2.1.2 No Keyboard Trap | Level A | Description Keyboard focus does not get trapped | Interaction Keyboard | Severity Blocker | Responsibility Developer | Knowledge to test Easy | Time to test Quick |
Test procedure Keyboard, Manual |
| Success criteria 2.1.4 Character Key Shortcuts | Level A | Description Keyboard short cuts are not used, unless the user can override them | Interaction Keyboard | Severity Blocker |
Responsibility Designer, Developer |
Knowledge to test Medium |
Time to test Medium, Quick |
Test procedure Keyboard, Manual, Request details, Screen reader |
| Success criteria 2.2.1 Timing Adjustable | Level A | Description There is time to read and act on things | Interaction Cognition | Severity |
Responsibility Designer, Developer |
Knowledge to test | Time to test |
Test procedure Manual, Visual inspection |
| Success criteria 2.3.3 Animations from Interactions | Level AAA | Description Animation respects reduce-motion settings | Interaction Cognition | Severity | Responsibility Developer | Knowledge to test | Time to test | Test procedure Manual |
| Success criteria 2.4.1 Bypass Blocks | Level A | Description There is a mechanism to skip to content, or skip past navigation | Interaction Keyboard | Severity Moderate, Severe |
Responsibility Designer, Developer |
Knowledge to test Easy | Time to test Quick |
Test procedure Keyboard, Manual |
| Success criteria 2.4.2 Page Titles | Level A | Description Page titles are unique and reflect the purpose of the page | Interaction Screen reader | Severity |
Responsibility Content, Developer |
Knowledge to test Easy | Time to test Quick |
Test procedure ARC Toolkit, Browser, Inspect code, Manual, Screen reader |
| Success criteria 2.4.3 Focus Order | Level A | Description The focus order is logical and intuitive | Interaction Keyboard | Severity Moderate |
Responsibility Designer, Developer |
Knowledge to test Easy | Time to test Quick |
Test procedure Keyboard, Manual, Some support from tools |
| Success criteria 2.4.4 Link Purpose | Level A | Description Ambiguous lonk phrases have not been used. The purpose of the link can be determined from the link text alone or it has been programmatically defined. | Interaction Cognition, Screen reader | Severity |
Responsibility Content, Designer, Developer |
Knowledge to test Medium | Time to test Quick |
Test procedure Manual, Screen reader, Some support from tools, Visual inspection |
| Success criteria 2.4.7 Focus Visible | Level AA | Description The location of the keyboard focus is visually obvious | Interaction Keyboard | Severity Moderate, Severe |
Responsibility Designer, Developer |
Knowledge to test Easy | Time to test Quick |
Test procedure Keyboard, Manual, Some support from tools |
| Success criteria 2.5.2 Pointer Cancellation | Level A | Description Down events for links/buttons are not used unless there is a cancel method | Interaction Mobile | Severity Severe | Responsibility Developer | Knowledge to test Easy | Time to test Quick |
Test procedure Manual, Request details |
| Success criteria 2.5.3 Label in Name | Level A | Description The visible label must be included in the accessible name (mostly applies to images and where labels are over-ridden) | Interaction Screen reader, Speech recognition | Severity Severe | Responsibility Developer | Knowledge to test Medium | Time to test Medium |
Test procedure Manual, Some support from tools |
| Success criteria 2.5.5 Target Size | Level AAA | Description Touch targets are large enough to touch accurately (at least 44px x 44px) | Interaction Mobile | Severity Moderate |
Responsibility Designer, Developer |
Knowledge to test | Time to test |
Test procedure Manual, Some support from tools |
| Success criteria 3.1.1 Language of Page | Level A | Description The default human language of each web page has been set | Interaction Screen reader | Severity | Responsibility Developer | Knowledge to test Medium | Time to test Quick |
Test procedure ARC Toolkit, Fully automated, Inspect code, Manual |
| Success criteria 3.1.2 Language of Parts | Level AA | Description Correct language codes for different languages on the page has been set where applicable | Interaction Screen reader | Severity |
Responsibility Content, Developer |
Knowledge to test Medium | Time to test Quick |
Test procedure Manual, Web inspector tool |
| Success criteria 3.2.1 On Focus | Level A | Description Landing on an element does not change the context | Interaction Keyboard | Severity Blocker | Responsibility Developer | Knowledge to test Easy | Time to test Quick |
Test procedure Keyboard, Manual |
| Success criteria 3.2.2 On Input | Level A | Description Changing a widget (e.g. drop down) doesn't automatically take you somewhere else | Interaction Keyboard | Severity Severe | Responsibility Developer | Knowledge to test Easy | Time to test Quick |
Test procedure Keyboard, Manual |
| Success criteria 3.3.3 Error suggestion | Level AA | Description Error messages are actually useful, e.g. provide a useful next step or way of entering valid data | Interaction Cognition | Severity |
Responsibility Content, Designer, Developer |
Knowledge to test | Time to test |
Test procedure Manual, Visual inspection |
| Success criteria 4.1.1 Parsing | Level A | Description Elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes | Interaction Screen reader | Severity Minor | Responsibility Developer | Knowledge to test | Time to test |
Test procedure ARC Toolkit, Bookmarklet, Manual, Some support from tools |
| Success criteria 4.1.2 Name, Role, Value | Level A | Description Custom controls have expected keyboard interactions | Interaction Keyboard | Severity Moderate, Severe | Responsibility Developer | Knowledge to test Expert | Time to test Medium |
Test procedure Keyboard, Manual |
| Success criteria 4.1.2 Name, Role, Value | Level A | Description Use standard controls appropriately and ensure that non-standard controls are properly marked up using WAI-ARIA and throughly tested | Interaction Screen reader | Severity Blocker, Minor, Moderate, Severe | Responsibility Developer | Knowledge to test Expert | Time to test Medium |
Test procedure ARC Toolkit, Manual, Screen reader, Web inspector tool |
| Success criteria 4.1.3 Status Messages | Level AA | Description Important dynamic changes in content, that are not given focus, are announced by screen readers | Interaction Screen reader | Severity Blocker | Responsibility Developer | Knowledge to test | Time to test |
Test procedure ARC Toolkit, Manual, Screen reader, Web inspector tool |
| Success criteria None | Level Best practice | Description The interface is usable in Windows High Contrast mode | Interaction Contrast | Severity | Responsibility Developer | Knowledge to test Easy | Time to test Quick |
Test procedure Manual, Windows |