Differences Between WCAG 2.1 and WCAG 2.2
The web content accessibility guidelines WCAG is an international standard focused on making web content accessible to people with disabilities. It was a group of individuals and organizations, the world wide web consortium, which took a proactive stance in developing the WCAG. These accessibility advocates created the WCAG guidelines to create a single standard for web accessibility. This article will teach you about WCAG 2.1 and WCAG 2.2 Differences!
On February 27th, 2020, the W3C released the first working draft of WCAG 2.2, an extension of WCAG 2.1. So while there are not many changes between the two, the WCAG 2.2 does have nine additional success criteria, including one that was promoted from AA to A!
These updates mainly focused on new helpful guidelines for using ebooks and other digital content types. They mainly focus on compliance and web accessibility on touchscreens and mobile platforms. Read on to learn more about these differences and how they help people with disabilities!
Differences between WCAG 2.1 and WCAG 2.2 success criteria
The WCAG 2.2 is a comprehensive guideline for web developers, website owners, students, content creators, policymakers, and others to follow while making web content accessible to everyone. The main difference between WCAG 2.2 and WCAG 2.1 lie in improved accessibility based on the same three conformance levels for three groups of users with disabilities. They are:
# Users with low vision
# Users with cognitive limitations or learning disabilities
# Users with restrictions like large fingers or motor disabilities that make using mobile devices challenging
The main reason and need for this update and to take a more proactive stance towards web compliance was the increase if mobile users. The update helps web owners and developers create websites with optimal mobile device accessibility. While developing or updating web content, it is better to comply with the latest WCAG 2.2 version than the previous WCAG version!
New guidelines accommodate people with disabilities
WCAG 2.2 is backward-compliant, extending WCAG 2.0 and 2.1 without significantly changing the previous versions. In other words, you know you conform to the earlier versions, 2.0 and 2.1 if you conform to WCAG 2.2. The WCAG 2.2 in total introduces nine new success criteria, which are:
1. Guideline 2.4.7 Focus Visible (A)
2. Guideline 2.4.11 Focus Visible (Enhanced AA compliant)
3. Guideline 2.5.7 Dragging (AA)
4. Guideline 2.5.8 Pointer Target Spacing (AA)
5. Guideline 3.2.6 Consistent Findable Help (A)
6. Guideline 3.2.7 Visible Controls (Level AA)
7. Guideline 3.3.7 Accessible Authentication (A)
8. Guideline 3.3.8 Redundant Entry (A)
2. Guideline 2.4.11 Focus Visible (Enhanced AA compliant)
3. Guideline 2.5.7 Dragging (AA)
4. Guideline 2.5.8 Pointer Target Spacing (AA)
5. Guideline 3.2.6 Consistent Findable Help (A)
6. Guideline 3.2.7 Visible Controls (Level AA)
7. Guideline 3.3.7 Accessible Authentication (A)
8. Guideline 3.3.8 Redundant Entry (A)
WCAG working drafts help web developers plan for updates
With these new success criteria greatly enhancing users’ experiences through proper access to resources and various assistive technologies, developers can plan updates based on WCAG 2.2. And even though there is a chance of the draft changing before publication, developers know that the new criteria will become a final recommendation after the official release!
There is no doubt that there are some significant differences between WCAG 2.1 and 2.2, which may initially seem somewhat overwhelming. However, web owners and developers must continue testing their websites and apps to ensure continual web compliance for users of assistive technology. With constant evaluation, you can ensure you do not miss anything critical in web compliance. You, in the process, will also know that your digital product is up to date and conforms with the latest WCAG version. This is especially important because the WCAG is not final, and the W3C will constantly update even the final version as technology advances!
We at https://adasitecompliance.com/differences-between-wcag-2-1-wcag-2-2/ can help ensure your website or app remains web compliant. We provide web compliance using various strategies like a digital accessibility cognitive function test to detect accessibility issues in digital products. Our team of accessibility professionals will not just guide you on removing any obstacles you may have in your digital product. They will also help you take a proactive stance by teaching you how to avoid these barriers in the first place!
