WCAG 2.2: The Newest Update in Digital Accessibility

Have you been hearing about WCAG 2.2 and want to ensure your site meets the latest standards? Don’t worry – we’re here to break it down with a simple, straightforward checklist to guide you.

What is WCAG 2.2?

WCAG 2.2 is the newest version of the Web Content Accessibility Guidelines (WCAG). The WCAG aims to make web content more accessible for people living with disabilities.
The recent update looks to enhance accessibility for people with cognitive disabilities by introducing supportive features. The update is backwards compatible, so you can implement it and know your site remains fully compliant with all previous web accessibility standards.

The Importance of Implementing WCAG 2.2

Now you’re familiar with WCAG 2.2, it’s crucial to recognise why complying with the latest standards matters.

1. Implementing all requirements ensures your site complies with US and international laws, which is particularly important for Australian businesses operating overseas.
2. Staying current with the latest WCAG updates helps you stay ahead of evolving regulations, both locally and internationally.
3. Their regular updates create seamless user experiences, allowing you to better serve users while demonstrating a commitment to inclusion.

Essential Website Requirements for WCAG 2.2

WCAG 2.2 outlines three levels of success criteria to assess how compliant your site is with regulations.

The levels range from the minimum requirements to the highest accessibility standards: A – AA – AAA

Each new requirement falls under one of the following WCAG guidelines:

• Guideline 2.2 – Navigable
• Guideline 2.5 – Input Modalities
• Guideline 3.2 – Predictable
• Guideline 3.3 – Input Assistance

Your WCAG 2.2 Compliance Checklist

Level A: Minimum

• Consistent Help (3.2.6)

Place ‘help’ features in the same location across multiple pages to make it easier for users to find.

This falls under the ‘predictable’ guideline (3.2), ensuring your web pages appear and function in predictable ways.

• Redundant Entry (3.3.7)

Avoid asking for the same information more than once during a session to help users who have difficulty remembering what they entered before.

This falls under the ‘input assistance’ guideline (3.3), ensuring users can avoid and correct mistakes.

Level AA: Acceptable

• Focus Not Obscured (2.4.11)

Items with keyboard focus should remain partially visible and unobstructed (e.g., by sticky footers) for users who cannot use a mouse.

This falls under the ‘navigable’ guideline (2.4), ensuring your site includes features to help users navigate, find content and know where they are on the page.

• Dragging Movements (2.5.7)

Provide a simpler alternative for any dragging movements to assist users who cannot use a mouse to drag items.

This falls under the ‘input modalities’ guideline (2.5), ensuring web pages include features to make it easier for users to operate through various inputs.

• Target Size (2.5.8)

Ensure targets (buttons) meet a minimum size or have sufficient spacing to help users with physical impairments who cannot click smaller buttons that are too close together.

This falls under the ‘input modalities’ guideline (2.5), ensuring web pages include features to make it easier for users to operate through various inputs.

• Accessible Authentication Minimum (3.3.8)

Avoid requiring users to move, recall, or transcribe information when logging in to accommodate users with cognitive disabilities. Instead, allow users to enter their email address and send a link via email to access the page or content.

This falls under the ‘input assistance’ guideline (3.3), ensuring users can avoid and correct mistakes.

Level AAA: Highest

• Accessible Authentication Enhanced (3.3.9)

Avoid requiring users to recognise objects or user-supplied images and media when logging in to accommodate users with cognitive disabilities. Instead, allow them to copy and paste a password.

This falls under the ‘input assistance’ guideline (3.3), ensuring users can avoid and correct mistakes.

• Focus Appearance (2.4.13)

Ensure you use a focus indicator of sufficient size and contrast to help users who have difficulty seeing small changes in visual appearance. For example, ensure the keyboard focus is visible when navigating the website.

This falls under the ‘navigable’ guideline (2.4), ensuring your site includes features to help users navigate, find content, and determine their location.

• Focus Not Obscured Enhanced (2.4.12)

When an item has a keyboard focus, it should be completely visible for users who cannot use a mouse. This means it should not be hidden by author-created content (e.g. by sticky footers).

This falls under the ‘navigable’ guideline (2.4), ensuring your site includes features to help users navigate, find content, and determine their location.

Set Your Website Up for Success!

WCAG 2.2 and the levels of compliance are backwards compatible, which means website developers only need to build on WCAG 2.1.

Level AA meets basic legal accessibility requirements. However, aiming for level AAA ensures you follow best practices and remove any barriers that could exclude users.

In short, meeting all requirements benefits both your website and organisation. Plus, they’ve made it straightforward by ensuring all elements are compatible with previous versions.

If you need help ensuring your website complies with WCAG 2.2, get in touch with our Perth website designers today!