What’s New in Web Content Accessibility Guidelines 2.1 ? Illustration: LexisNexis Content UX Design Team

My Thoughts on Web Content Accessibility Guidelines (WCAG) 2.1

If you are working in the inclusive design or development industry, I am sure you would have heard that Web Content Accessibility Guidelines (WCAG) standard has been officially updated from WCAG 2.0 to WCAG 2.1, with effect from 5th June 2018.

WCAG 2.0 is the most modern and widely known international standard for web accessibility. Even though it is not a law itself, it is the preferred global standard in contemporary web accessibility regulations, which means it affects almost all digital products. WCAG 2.1 builds on WCAG 2.0, and still follows the A, AA, and AAA conformance levels. WCAG 2.0 has 61 success criteria whereas WCAG 2.1 has 78 criteria. The original 61 criteria from WCAG 2.0 remain the same, and 17 new success criteria are added. The additional recommendations address mobile accessibility, people with low vision and people with cognitive and learning disabilities.

Here are my views on the new updates:

1. WCAG 2.0 has been around for 10 years. No doubt, it is the time to update the standard and drive a better user experience for everyone. Throughout the time, assistive technology has been evolving, web and mobile technology have been advancing, and the consumer demand for higher quality products has been growing. Therefore, to maintain a competitive edge, the businesses need to adapt, innovate and meet the new expectations.
2. The new WCAG 2.1 criteria not only benefit those with disabilities but also make the web experience for all better. For example, good contrast between text and background on a large screen, sufficient text spacing on a small mobile screen, and 2.2.6 Timeouts that really benefits everyone by helping people understand instances when websites might lose their data after inactivity. The reality is that with increasing age most people experience multiple minor impairments in areas like eyesight, hearing and mobility. Those techniques evaluate products as you develop them and ensure products are genuinely inclusive.
3. Two noticeable criteria are specifically designed to provide a better user experience for text-to-speech users. 2.5.3 Label in Name — the benefit of this criterion is that the labels that users hear match the visible text labels that they see on the screen. To improve accessibility for the users, the best practice is to have the visible text at the start of the name, not in the middle or at the end. 2.1.4 Character Key Shortcuts — the benefit of this criterion is that users will be able to turn off single-key shortcuts and change the shortcut to utilise a non-alphanumeric letter key. Note that the shortcut is only active when a UI component has focus, like in a combo box.
4. For many organisations, data visualisation is a valuable tool in the drive to improve service, as most people tend to grasp difficult concepts more easily when analytics were presented visually. But while these innovations are making the products more user-friendly, they can also potentially deepen inequality among users. Therefore, it is even more important to follow the best practice and understand the new WCAG 2.1 checkpoints. When it comes to accessible visualizations, 1.4.11 Non-Text Contrast (AA) is my favourite — it benefits users with low vision who have difficulty with seeing graphics and icons with insufficient contrast.
5. Although there are no immediate legal requirements for companies to comply with WCAG 2.1 standard, it would be wise for any forward-thinking companies to begin implementation of these new criteria. The ability to comply with new guidelines doesn’t mean that you are exempt from lawsuits, as there may be other factors that need to be considered, but it would be prudent to act early and apply these new rules in a planned approach before they are required by international laws and regulations.
6. Product owners or business owners need to understand how this will impact the product development process. Consider hiring developers and designers who have working knowledge with the new WCAG guidelines; consider adding the new criteria to the auditing reports of your products, especially mobile applications to assess compliance with the WCAG 2.1 guidelines and investigate options to bridge the gap; and finally consider reviewing your current contracts with third party suppliers who do not cover WCAG standard.

Final thoughts

Web technology and concepts of good accessibility have both changed significantly in the last ten years, therefore WCAG 2.1 is the right call for the industry and policymakers. Since WCAG is such a popular metric for accessibility, following this new set of guidelines should be on every online business’s roadmap. As always, talking to experts who will help you form a better remediation plan, hiring professionals with good design and development skills will help you stay at top of the game. For more information on WCAG 2.1, please visit their website.