Understanding WCAG 2.2: Key Changes and Implications

On October 5, 2023, Web Content Accessibility Guidelines (WCAG) 2.2 officially became a W3C Recommendation​. 

WCAG 2.2 introduces nine new success criteria (guidelines), including two at Level A, four at Level AA, and three at Level AAA. These updates focus on improving access for users with cognitive, learning, mobility disabilities, and low vision​.

Let’s explore the key changes and what they mean for your organization.

Key Updates in WCAG 2.2

WCAG 2.2’s most notable additions are several new Success Criteria designed to improve navigation and interaction for users. A few highlights include: 

• Focus Not Obscured (Level AA): When a user tabs through a page via keyboard, the item that receives focus must not be hidden by other content (e.g. no pop-up or sticky footer should entirely cover the focused element)​. This ensures keyboard-only users can always see where they are on the screen.
  

• Dragging Movements (Level AA): Any action that involves dragging must also be achievable with a simple click or tap alternative.
  

• Target Size (Level AA): Interactive components like buttons, links, and form controls now have a minimum target size requirement. In practice, this means bigger click/tap areas and adequate spacing, reducing the chance that users with limited dexterity or low vision miss their target.
  

• Consistent Help (Level A): If a help option (such as a chat icon, support link, or FAQ) appears on multiple pages, it should be presented in a consistent location each time. This consistency allows users, especially those with cognitive or memory difficulties, to reliably find assistance when they need it.
  

• Redundant Entry (Level A): Users should not be forced to re-enter information that they have already provided earlier in a process​. For example, a returning customer’s shipping address should auto-fill if it was entered previously. Eliminating duplicative input reduces frustration and cognitive load on all users.
  

• Accessible Authentication (Level AA): Login or verification processes must offer alternatives to memory tests or tricky CAPTCHA puzzles. In other words, users should be able to authenticate without having to recall passwords or solve cognitively demanding tasks.

Implementing WCAG 2.2: Best Practices and Tips

Updating to WCAG 2.2 doesn’t have to be overwhelming. Here are some actionable best practices to help your team efficiently implement the new guidelines:

• Start with a Gap Analysis: Begin by auditing your current websites and applications against the new WCAG 2.2 criteria. Identify where you already comply and where gaps exist.
  

• Prioritize Critical Fixes: Focus on the new Level A and AA success criteria first, since these have the most impact on users and are likely to be expected in compliance audits. Tackle quick wins like enabling visible focus styles in your CSS, adding an option to bypass drag-and-drop features, and adjusting UI components to meet minimum size guidelines.
  

• Integrate into Design and Development: To avoid scrambling for compliance at the last minute, bake WCAG 2.2 into your design and development processes now.
  

• Leverage Resources and Expertise: Make use of the wealth of resources available to streamline implementation. For example, the W3C’s official documentation provides techniques for each success criterion​. Consider partnering with digital accessibility consultants or using compliance tools for support – they can help interpret requirements and even handle testing or remediation for you.
  

• Iterate and User-Test: Plan to continuously test with real users, including people with disabilities, to ensure that the changes you make truly improve usability.

Ready to elevate your digital accessibility? Explore our innovative tools and resources on achieving WCAG compliance and empower your team to build inclusive, compliant user experiences.