Accessibility checklist and guidance for developers
This checklist contains information and guidance on the Web Content Accessibility Guidelines (WCAG) success criteria. It can be used to help carry out an initial evaluation of your service.
Success criteria | Level | Description | What this affects | Severity | Who is responsible | Knowledge to test | Time to test | Test procedure |
---|---|---|---|---|---|---|---|---|
1.1.1 Non-text Content | A | Images that convey meaning have suitable alternative text and images that serve a decorative purpose have a null alternative text assigned | Screen reader |
|
|
Medium | Medium |
|
1.3.1 Info and Relationships | A | Font icons are not used | Contrast | Moderate |
|
Medium | Medium |
|
1.3.1 Info and Relationships | A | Form code is implemented correctly | Screen reader |
|
Developer | Medium | Medium |
|
1.3.1 Info and Relationships | A | The HTML structure and semantices reflects the intent - landmarks, headings, lists, data tables | Screen reader |
|
|
Medium | Medium |
|
1.3.1 Info and Relationships | A | Inline CSS is not used |
|
Minor |
|
Medium | Medium |
|
1.3.2 Meaningful Sequence | A | Content is in a logical order in the code | Screen reader |
|
Developer | Medium | Medium |
|
1.3.4 Orientation | AA | Orientation is not locked | Mobile | Severe | Developer | Easy | Quick |
|
1.3.5 Identity Input Purpose | AA | Autocomplete is used on inputs when appropriate | Cognition | Moderate | Developer | Medium | Medium |
|
1.4.4 Resize Text | AA | You can make text at least 200% larger without losing content/functionality | Magnification |
|
Developer | Easy | Quick |
|
1.4.5 Images of Text | AA | Graphics are not used for text (except logos) | Magnification |
|
|
Medium | Quick |
|
1.4.10 Reflow | AA | You can zoom in 400% without losing content/functionality or horizontal scrolling | Magnification |
|
|
Easy | Quick |
|
1.4.12 Text Spacing | AA | The current text spacing can be overridden without loss of content or functionality | Magnification | Severe | Developer | Easy | Quick |
|
1.4.13 Content on Hover or Focus | AA | Pop-overs that appear on keyboard focus can be dismissed using the keyboard | Keyboard | Moderate | Developer | Easy | Quick |
|
1.4.13 Content on Hover or Focus | AA | Pop-ups are not used on hover, unless they are dismissable and robust | Magnification | Severe | Developer | Easy | Quick |
|
2.1.1 Keyboard | A | All functionality is operable with a keyboard | Keyboard | Blocker | Developer | Medium | Medium |
|
2.1.2 No Keyboard Trap | A | Keyboard focus does not get trapped | Keyboard | Blocker | Developer | Easy | Quick |
|
2.1.4 Character Key Shortcuts | A | Keyboard short cuts are not used, unless the user can override them | Keyboard | Blocker |
|
Medium |
|
|
2.2.1 Timing Adjustable | A | There is time to read and act on things | Cognition | Blocker |
|
Medium | Medium |
|
2.3.3 Animations from Interactions | AAA | Animation respects reduce-motion settings | Cognition |
|
Developer | Easy | Quick | Manual |
2.4.1 Bypass Blocks | A | There is a mechanism to skip to content, or skip past navigation | Keyboard |
|
|
Easy | Quick |
|
2.4.2 Page Titles | A | Page titles are unique and reflect the purpose of the page | Screen reader |
|
|
Easy | Quick |
|
2.4.3 Focus Order | A | The focus order is logical and intuitive | Keyboard | Moderate |
|
Easy | Quick |
|
2.4.4 Link Purpose | A | Ambiguous link phrases have not been used. The purpose of the link can be determined from the link text alone or it has been programmatically defined. |
|
Moderate |
|
Medium | Quick |
|
2.4.7 Focus Visible | AA | The location of the keyboard focus is visually obvious | Keyboard |
|
|
Easy | Quick |
|
2.4.11 Focus Not Obscured (Minimum) | AA | A focus indicator is not restricted in any way | Keyboard | Moderate |
|
Easy | Quick |
|
2.5.2 Pointer Cancellation | A | Down events for links/buttons are not used unless there is a cancel method | Mobile | Severe | Developer | Easy | Quick |
|
2.5.3 Label in Name | A | The visible label must be included in the accessible name (mostly applies to images and where labels are over-ridden) |
|
Severe | Developer | Medium | Medium |
|
2.5.5 Target Size (Enhanced) | AAA | Touch targets are large enough to touch accurately (at least 44px x 44px) | Mobile | Moderate |
|
Easy |
|
|
2.5.7 Dragging Movements | AA | No click and drag function is required, or an alternative is provided |
|
Moderate |
|
Medium | Medium |
|
2.5.8 Target Size (Minimum) | AA | Components have a minimum target size | Mobile | Moderate |
|
Medium |
|
|
3.1.1 Language of Page | A | The default human language of each web page has been set | Screen reader | Moderate | Developer | Medium | Quick |
|
3.1.2 Language of Parts | AA | Correct language codes for different languages on the page has been set where applicable | Screen reader | Moderate |
|
Medium | Quick |
|
3.2.1 On Focus | A | Landing on an element does not change the context | Keyboard | Blocker | Developer | Easy | Quick |
|
3.2.2 On Input | A | Changing a widget (e.g. drop down) doesn't automatically take you somewhere else | Keyboard | Severe | Developer | Easy | Quick |
|
3.3.3 Error suggestion | AA | Error messages are actually useful, e.g. provide a useful next step or way of entering valid data | Cognition | Medium |
|
Medium | Medium |
|
3.3.7 Redundant Entry | A | Users do not have to enter the same information more than once | Cognition | Moderate |
|
Medium | Medium |
|
3.3.8 Accessible Authentication (Minimum) | AA | Users are not required to complete a function test, except under certain conditions | Cognition | Severe |
|
Medium | Medium |
|
4.1.2 Name, Role, Value | A | Custom controls have expected keyboard interactions | Keyboard |
|
Developer | Expert | Medium |
|
4.1.2 Name, Role, Value | A | Use standard controls appropriately and ensure that non-standard controls are properly marked up using WAI-ARIA and thoroughly tested | Screen reader |
|
Developer | Expert | Medium |
|
4.1.3 Status Messages | AA | Important dynamic changes in content, that are not given focus, are announced by screen readers | Screen reader | Blocker | Developer | Medium | Quick |
|
None | Best practice | The interface is usable in Windows High Contrast mode | Contrast | Moderate | Developer | Easy | Quick |
|