Summary
The recent Web Content Accessibility Guidelines 2.2 update brings improvements to aspects of operating and understanding websites. This is our final post in a three-part blog series giving you a tour of the updates.
Introduction
The long-awaited Web Content Accessibility Guidelines update, WCAG 2.2, is finally slated for release in May 2023.
If you haven’t already, check out our insights into the first four guideline updates in our blog Understanding WCAG 2.2 Part One and the next three guidelines in Understanding WCAG 2.2 Part Two.
We expect WCAG 2.2 to include nine new success criteria. The W3C also now considers the guideline 4.1.1: Parsing deprecated, or no longer applicable, and eliminated it. Let’s take a look at the final four expected changes.
Potential new guidelines
3.3.7: Accessible Authentication (Level AA)
3.3.7 requires authentication on a website doesn’t include cognitive tests, such as remembering usernames and passwords. For example, preventing users from pasting passwords from a password manager violates this guideline.
There are exceptions to this criterion, including the use of captchas. Captchas which require a user to recognize objects are considered okay because the objects are usually commonplace and familiar (e.g., “Select all images with traffic lights.”).
3.3.8: Accessible Authentication No Exceptions (Level AAA)
3.3.8 differs from 3.3.7 in that it does not allow for any exceptions, such as earlier mentioned captchas. Users should be able to authenticate without any cognitive challenges. Websites should include helpful features such as login fields which allow automatic entries from password managers.
3.3.9 Redundant Entry (Level A)
3.3.9 seeks to reduce difficulty for users entering information multiple times. This criterion requires that a method be available to automatically reuse entered data, such as checking a box to use the same address for shipping and billing.
4.1.1: Parsing (Level A)
This criterion required complete HTML start and end tags. Content which violates this guideline would also violate other guidelines, so the W3C removed it. Additionally, there are technical considerations around how assistive technology interacts with HTML code which make this criterion unnecessary.
Conclusion
WCAG 2.2 comes packaged with nine new success criteria designed to improve the operation and understanding of websites. The new and updated criteria will make it easier to authenticate and access content with screen readers on websites. WCAG 2.2 will not replace WCAG 2.1, but it does provide much needed improvements to the current set of guidelines.
Take a moment to bookmark the WCAG 2.2 updates page, explore WCAG 2.2, and start a conversation with us about how we can help you prepare for WCAG 2.2 and beyond. We are always only an email or a phone call away.
/>
/>