WCAG 2.2 is a lot like previous upgrades of WCAG where all previous criteria are included, and additional criteria are added. To be specific, there are 9 new criteria. Most of the criteria revolve around auditing the "focus display" and form/login interactions.
In our Policy Library, we have a Policy Set for WCAG 2.2 - Success Criteria recommended manual review. We made policies to review forms for criteria 3.3.8 and 3.3.9. We're exploring the automation of these policies for a future release of DubBot. Criteria 2.5.8 will likely also be included in automated testing in the future.
2.4.11 Focus Appearance (AA)
Requires a visual appearance around content in focus when using a keyboard to navigate content.
How to test: Manually audit web page templates to ensure that focus is visible, encapsulates all the components, and meets new visual standards.
2.4.12 Focus Not Obscured (Minimum) (AA)
Ensure that part of the focus indicator is visible and not completely covered by other content.
How to test: Manually audit web page templates to ensure the focus indicator is at least partially visible.
2.4.13 Focus Not Obscured (Enhanced) (AAA)
Ensure that all of the focus indicators are visible and none of the indicators is covered by other content.
How to test: Manually audit web page templates to ensure the focus indicators are completely visible.
2.5.7 Dragging Movements (AA)
Focuses on making applications/websites that require users to drag content using a cursor accessible using assistive technology.
How to test: Audit website for interaction with content that requires dragging action. Most websites do not have this. Review slideshows on mobile/tablet devices.
2.5.8 Target Size (Minimum) (AA)
The size of the target for pointer inputs is at least 24 by 24 CSS pixels with exceptions outlined in WCAG including in blocks of text.
How to test: Manually review webpage templates for button positioning where clickable areas reside in closer proximity.
3.2.6 Consistent Help (A)
Any help mechanism used across pages is maintained in the same relative order of the page.
For example, a chat app button should be available in the same area of the page across a website.
How to test: A manual review of webpage templates is required.
3.3.7 Redundant Entry (A)
Ensure that forms that require entry of the same content multiple times allow for simple reuse of entered content.
How to test? Audit forms for fields that could use the same data. Allow for content to be pre-populated from other content already filled in.
3.3.8 Accessible Authentication (Minimum) (AA)
Focuses on making a login process more accessible for users with learning disabilities.
The expectation is to provide support for password entry by password managers to reduce memory need and copy and paste to reduce the cognitive burden of re-typing.
How to test: Manually review any login processes.
How can DubBot help? We have created a policy that flags pages in a site's inventory that contain a form with a password field for you to audit.
3.3.9 Accessible Authentication (Enhanced) (AAA)
A more strict success criterion similar to 3.3.7.
Provides another authentication method that does not rely on a cognitive function test. IE not having to remember a personal secret to login.
How to test? Manually review any login processes
How can DubBot help? We have created a policy that flags pages in a site's inventory that contain a form with a password field for you to audit.
Related Articles
If you have questions, please contact our DubBot Support team via email at help@dubbot.com or via the blue chat bubble in the lower right corner of your screen. We are here to help!