WCAG 2.2 Compliance: What changed and who is most at risk

‍

Imagine a playground with sturdy swings, smooth slides and clean sandbox. But there is no ramp for children who use wheel chairs. Isn’t it unfair and unsafe?

Similarly, the internet is a huge playground where everyone should have equal access regardless of their abilities. The Web Content Accessibility Guidelines set rules for equal access. These rules break digital accessibility barriers for users with disabilities.

W3C introduced the WCAG 2.2 version in October 2023. This update added new rules to make websites even more accessible. However, many websites still do not follow these guidelines. This can lead to legal trouble and other issues.

What Is WCAG 2.2

WCAG make websites accessible to people with various disabilities. It sets a framework to make digital content easy for users with vision, hearing or mobility challenges.

WCAG 2.2 is the latest version of these rules. It builds upon previous versions by adding new success criteria that websites should follow to be accessible.

What is new in WCAG 2.2?

WCAG released version 2.2 and added 9 new rules in October 2023. These updates are mostly for people with low vision, cognitive or learning disabilities. 2.2 update ensures people can access websites easily using mobile phones or tablets.

There are three levels of accessibility. Level A is basic or the minimum every website should follow. WCAG AA is what most businesses and governments aim for. Level AAA is the highest level. It is great if you can do it, but it is not always required.

Focus Not Obscured (Minimum) (Level AA)

When someone uses a keyboard to move around a webpage, they should be able to see where they are. Nothing should block or hide the part they are focused on. For instance, someone fills out a form and presses the tab to jump to the next box. Then a sticky header covers it, which is no longer allowed in WCAG.

Focus Not Obscured (Enhanced) (Level AAA)

This is a stronger version of the previous rule. The focused element must be fully visible at all times. When a button is selected using the keyboard, it shouldn’t be half-covered or pushed behind an image, even a little bit.

Focus Appearance (Level AAA)

When someone moves around a site using a keyboard, it should be easy to see which element is selected. The focus indicator must have enough contrast and thickness to stand out. For instance, a thin blue line on a white background may be hard to see. A thick dark border or a color change that stands out clearly is better.

Dragging Movements (Level AA)

If your website needs users to drag things around, you must offer tapping or clicking options to do it. Like a photo app that lets users drag pictures to sort them should also allow using move up or move down buttons for people who cannot drag.

Target Size (Minimum) (Level AA)

Buttons, links, or any clickable items must be big enough to click easily on small screens like phones. A tiny “X” to close a pop-up can be hard to tap. It must be at least 24x24 pixels so that people with shaky hands or touch devices can tap on it.

Consistent Help (Level A)

If your website offers a chat button, phone number, or FAQ, then it should be in the same place on every page. If your Live Chat is on the bottom-right corner of the homepage, it should be in the same spot on the Contact Us or Product pages too.

Redundant Entry (Level A)

Do not make users type the same information over and over. If a user already typed their email in Step 1 of checkout, do not ask for it again in Step 3. Autofill or remembering previous entries helps a lot here.

Accessible Authentication (Minimum) (Level AA)

Logging in or proving your identity should not require solving puzzles that are hard for people with cognitive disabilities. For instance, CAPTCHAs with weird letters are hard. WCAG Accessibility alternatives are sending a code to email or letting users copy-paste from a password manager.

Accessible Authentication (Enhanced) (Level AAA)

Go one step further and ensure no memory tests or puzzles are needed for login or security. Avoid asking users to remember secret images or solve visual puzzles. Let them log in using email links or biometrics.

These updates aim to make web content more usable for the disabled population.

Why is WCAG Compliance important?

Failing to comply with WCAG 2.2 can lead to:

• Legal Risks
• Exclusion of Users
• Negative Publicity

Many countries have laws requiring digital accessibility. Non-compliance invites the risk of lawsuits, fines and reputational damage.

Thousands of ADA lawsuits have been filed in the US federal court. The plaintiffs alleged non-compliance with WCAG standards. Therefore, continuous WCAG testing is crucial for proper litigation risk management.

Moreover, non-compliant websites exclude users with disabilities. There will be a loss of audience and potential customers. Further, accessibility lawsuits and non-compliance can attract negative media attention which can harm a company's reputation.

Who is most at risk?

Certain organizations are more vulnerable to the consequences of non-compliance:

• E-commerce Websites: Online retailers might lose customers or face legal action due to inaccessible websites.
• Educational Institutions: Schools and universities must make digital content accessible to all students.
• Government Agencies: Public sector organizations are often legally required to meet accessibility standards.
• Healthcare Providers: Medical websites must be accessible to provide critical information to all patients.

How to Achieve WCAG 2.2 Compliance

Achieving compliance involves accessibility audits and remediation.

1. Thorough WCAG testing of your website to identify areas that do not meet 2.2 standards.
2. Remediate your website's design and functionality to address identified issues.
3. Continuously assess your website to ensure ongoing compliance, especially when you add new content.

ADACP can handle the entire compliance process for you. We provide in-depth audits, detailed reports and fast, effective remediation services to fix accessibility issues. Our team knows WCAG2.2 inside out. We know more than most in-house teams because accessibility is our forte. Trust us to protect your website from serial litigants.

Conclusion

Making your website accessible to all users is essential in 2025. Understand the changes in WCAG 2.2 to remove accessibility barriers from the online environment. Choose ADACP to protect your organization from legal risks.

For more information on WCAG 2.2 and how to achieve compliance, visit the official guidelines at W3C's WCAG 2.2 Overview. Or schedule a free consultation with us to learn more about WCAG testing.

‍