November 30, 2017
Updated Web Accessibility Checklist – Perceivable
Back in 2010, we have published a Quick Web Accessibility Checklist that received a good response and we have also received a good feedback. It’s true that users prefer to have a quick checklist along with large documentation to achieve their accessibility mission. So we are bringing you this updated Web Accessibility Checklist reflecting success criterions of Web Content Accessibility Guidelines (WCAG) 2.1. Please note this checklist gets updated once again when WCAG 2.1 becomes a W3C recommendation (expected to be in 2018). Also, note that all external links on this page opens in a new window. We will be publishing this as a series of 4 posts so that it will be easy for users to refer.
| Level | WCAG 2.1 Success Criterion | What to check for? |
|---|---|---|
| A | 1.1.1 Non-text content |
|
| A | 1.2.1 Audio-only and video-only (prerecorded) |
|
| A | 1.2.2 Captions (prerecorded) | Ensure that captions are provided for all audio based content except where audio description is alternative to visual content |
| A | 1.2.3 Audio description or media alternative (prerecorded) | Ensure that audio description is provided for all prerecorded video content except where video itself is alternative to audio content |
| AA | 1.2.4 Captions (Live) | Ensure that captions are provided for live video content in synchronised manner |
| AA | 1.2.5 Audio description (prerecorded) | Ensure that audio description is provided for all prerecorded video content in synchronised media |
| A | 1.3.1 Info & relationships |
|
| A | 1.3.2 Meaningful sequence | Is the reading order meaningful from its presentation? |
| A | 1.3.3 Sensory Characteristics | Ensure that no instructions are provided in way that requires use of a specific sense of users such as using shape, color, visual location, size, orientation or sound |
| AA | 1.3.4 Purpose of control | This is a new Success Criterion and needs some interpretation to understand. This talks about personalisation of controls. While icons for different purpose may have standard icons, it’s recommended that user should be able personalise it. |
| A | 1.4.1 Use of Colour | Do not use colour as a sole means of information. Example: Normally “green” is shown to indicate success and “red” to indicate failure. While showing the same in color, it is also important to show as “text”. |
| A | 1.4.2 Audio-control |
|
| AA | 1.4.3 Contrast – Minimum | Ensure that there is minimum contrast ratio of 4.5:1 for regular text between foreground and background. For large text, minimum contrast ratio should be 3:1. Incidental text such as inactive controls and logotypes do not require to have minimum ratio of contrast. |
| AA | 1.4.4 Resize Text | Ensure that user should be able to zoom in content upto 200% without use of any assistive technologies. This is not applicable for captions and images of text |
| AA | 1.4.5 Images of text | Use natural text to provide information unless it’s essential to embed text to an image. Logotype is known as essential |
Tags :
[…] is 2 of 4 in our series to put together an updated web accessibility checklist. As mentioned in our earlier post Updated Web Accessibility Checklist – Perceivable, this post may get updated once Web Content Accessibility Guidelines (WCAG) 2.1 becomes candid […]