WCAG 2.2 vs. WCAG 2.1: What’s the difference, and what does it mean?

The World Wide Web Consortium (W3C) has recently released an update to the Web Content Accessibility Guidelines (WCAG) from version 2.1 to 2.2. These revised guidelines aim to improve web accessibility for all users, especially those with various forms of disabilities. But what sets 2.2 apart from 2.1?

Differences in WCAG 2.2

The latest version, WCAG 2.2, introduces nine new criteria focusing on enhancing the user experience for individuals with different disabilities. These include requirements such as avoiding completely or partially hidden elements, increased emphasis on keyboard navigation, improved usability on touchscreens, and larger interactive click areas.

New additions in WCAG 2.2:

• 2.4.11 (AA): When an element receives focus, it must not be entirely hidden by other elements on the page.

• 2.4.12 (AAA): A focused element must not be partially hidden by other elements on the page.

• 2.4.13 (AAA): Keyboard focus must be clearly defined.

• 2.5.7 (AA): Functions where the user moves an object with the mouse or finger on a touchscreen should be achievable through alternative methods without drag gestures.

• 2.5.8 (AA): Interactive objects must have a minimum click size of 24 x 24 pixels.

• 3.2.6 (A): If the website has help features, they must be consistent and accessible on all pages.

• 3.3.7 (A): Repetition of information in a process should be avoided.

• 3.3.8 (AA): Authentication functions must be accessible without requiring cognitive function, such as remembering passwords.

• 3.3.9 (AAA): Similar to 3.3.8, but with fewer exceptions.

Significance of the update:

For public entities and businesses with websites, the update indicates the increasing importance of complying with web accessibility standards. While WCAG 2.1 still forms the basis for many websites, transitioning to 2.2 will be crucial to ensure that websites are more accessible to all users.

Although the transition to WCAG 2.2 is not necessarily required immediately, organisations should begin preparing to meet these updated guidelines to enhance user experience and comply with future web accessibility standards.

WCAG 2.2 marks a step forward in ensuring that websites are more accessible and user-friendly for everyone. The shift from 2.1 to 2.2 involves a focus adjustment and improvement of standards that will benefit all users, regardless of their abilities and disabilities.

How to comply with WCAG 2.2:

Using tools like Assist Pro can help ensure that your documents are accessible and meet all WCAG requirements. For Dania Software A/S, it is crucial to support this important legislation, and therefore, we ensure that Assist Pro is continuously updated to meet the requirements. For you, this means you can confidently continue using Assist Pro to comply with WCAG 2.2.

What is Assist Pro?

Assist Pro is a tool to ensure accessibility in your documents. The solution seamlessly integrates with Microsoft Office, making it easy to create accessible documents directly in Word, Excel, and PowerPoint. With Assist Pro, you can scan and correct documents for accessibility before exporting them to formats such as PDF, PDF/UA, or HTML.

In a world where 20% of the population lives with disabilities that significantly limit their ability to access online information, the need for accessibility is crucial. The desire for a more accessible future is not just about complying with the law; it’s about doing the right thing.

Automate WCAG 2.2 compliance in your documents with Assist Pro before exporting them as PDF, PDF/UA, or HTML.

The future of WCAG:

The upcoming WCAG 3.0 aims to introduce a new compliance model that addresses a broader spectrum of user needs, tests a wider range of technologies, and supports innovative testing methods. W3C is exploring different compliance strategies and presenting promising concepts based on feedback from previous drafts.

The goals of this new compliance model are developed for continuous improvement of web accessibility beyond the existing AA level. The aim is to better reflect all content for users with disabilities and thus have fewer errors and inconsistencies in content, as long as they do not significantly impact users with disabilities.

The versatility of WCAG can be integrated in various ways. The W3C working group plans to rigorously test these approaches in terms of validity, reliability, sensitivity, adequacy, complexity, and fairness. They actively seek input to improve these approaches and address concerns about their potential impact on accessibility, with plans to choose or modify options based on feedback, prototypes, and testing.

W3C no longer provides an expected release date for WCAG 3.0: “WCAG 3.0 is intended to evolve into a W3C standard within the next few years.”

Source: DIGG