If you’re a compliance officer or decision-maker, you’ve probably seen “WCAG 2.2 Level AA” show up everywhere lately. If you’re wondering what it means for your organization and what to do next, you’re in the right place.
This update is worth your attention. WCAG 2.2 isn’t just a rule to follow. It helps make sure people with disabilities can actually use your website. That means they can access your services, complete tasks, and get information without hitting barriers.
And yes—it also helps reduce legal risk.
In this post, we’ll break down what changed in WCAG 2.2, why it matters, and what to do next. No jargon.
What Actually Changed in WCAG 2.2?
WCAG 2.2 builds on WCAG 2.1 (which built on 2.0). Think of it like an update to the accessibility “rulebook.” The World Wide Web Consortium (W3C) added nine new success criteria. Most of the new rules focus on:
- Mobile use (touch screens, small buttons, scrolling)
- Cognitive accessibility (memory, attention, learning differences)
- Keyboard access (for people who don’t use a mouse)
Here are the highlights you need to know:
Focus Not Obscured (Minimum), Level AA
When someone tabs through your site using a keyboard, the item they’re on (the “focus”) can’t be hidden.
In plain terms: if a person is using the Tab key, they should always be able to see where they are.
This helps people with motor disabilities, people who use keyboard shortcuts & people who can’t use a mouse.
Dragging Movements, Level AA
If something on your site requires dragging (like a slider, drag-and-drop tool, or sortable list) there must be another way to do it.
Not everyone can drag items accurately. Some people use assistive technology. Others may have tremors or limited hand control.
Target Size (Minimum), Level AA
Buttons and links need to be big enough to tap.
WCAG 2.2 sets a minimum target size of 24×24 pixels (with some exceptions).
If you’ve ever tried to tap a tiny button on your phone and hit the wrong thing, you already understand why this matters.
Consistent Help, Level A
If you offer help options (like a contact link, phone number, or chatbot), they need to appear in the same place on every page.
They should also appear in the same order.
This helps people who rely on routine and consistency, especially people with cognitive disabilities; but it makes things easier for everyone.
Redundant Entry, Level A
Don’t make people type the same information again and again.
For example: if someone already entered their email address on step one of a form, don’t ask for it again on step three.
This helps people with memory challenges and reduces frustration for all of us.
Accessible Authentication (Minimum), Level AA
Login systems can’t rely only on memory tests.
That means you shouldn’t require a “remember this password” approach with no other option. You should support alternatives like password managers, One-time codes by email or text, or even fingerprint or face login (when available).
What About the Other Three?
The remaining three new criteria are Level AAA:
- Focus Not Obscured (Enhanced)
- Focus Appearance
- Accessible Authentication (Enhanced)
They’re great goals, but most organizations focus on WCAG 2.2 Level AA because that’s the level most often used for legal and policy compliance, so we’ll keep our focus there, too.
When Do we Need to Act?
Here’s the good news: you usually don’t have to change everything overnight.
WCAG 2.2 was published in October 2023, and many organizations build in time to transition.
But here’s the realistic part: if you’re a government agency, a federal contractor, or you receive federal funding, you should already be planning and making updates.
For colleges and universities that follow Office for Civil Rights (OCR) requirements, WCAG 2.2 is quickly becoming the expected standard.
For private companies—especially in regulated industries or with major online services—the message is also clear: WCAG 2.2 Level AA is becoming the new baseline.
Bottom line: it’s better (and cheaper) to start now than to wait for a complaint or lawsuit.
Why Your Legal Team Is Emailing You
Let’s be honest: lawsuits are a big reason this gets attention.
Digital accessibility lawsuits have been rising for years. They affect:
- Large companies
- Small businesses
- State and local governments
- Colleges and universities
If your website doesn’t meet current accessibility expectations, you may face:
- ADA Title II risk (state and local government)
- ADA Title III risk (businesses open to the public)
- Section 508 issues (federal agencies and contractors)
- OCR complaints (higher education)
- State accessibility laws (like California and New York)
And beyond legal risk, there’s a bigger issue: people may be blocked from using your services.
This is not just a compliance problem—it’s a human problem.
It’s also important to know that WCAG 2.1 is still the main legal standard right now, but we’re clearly moving toward WCAG 2.2.
What This Means for Your Organization (Simple Steps)
Here’s what you need to do, broken down into simple steps:
Assess Where You Stand
Start with an accessibility audit against WCAG 2.1 Level AA. You need a baseline before you can plan.
Focus on:
- High-traffic pages
- Key user tasks (paying bills, applying, registering, purchasing)
- Online services and forms
Prioritize the Biggest Barriers
Fix the issues that block people from completing important tasks first.
Train Your Team
Accessibility can’t live in one person’s job description.
Train:
- Developers
- Content creators
- Designers
- Anyone who updates the website
And remember, one training session isn’t enough. Accessibility needs to be part of your normal process.
Implement Changes in a Planned Way
Create a realistic plan with timelines.
Build accessibility into:
- Design reviews
- Content publishing
- Development and Quality Assurance
That way you’re not always scrambling to fix problems later.
Monitor and Maintain
Accessibility isn’t “done” after one project.
Websites change all the time. New content can create new issues. Ongoing monitoring helps you stay on track.
The Bottom Line: This Is About People
Accessibility work often starts with rules and risk management—and that matters.
It also affects everyday use. When buttons are easier to tap, focus is easier to see, and forms are easier to finish, more people can use your site in more situations.
WCAG 2.2 isn’t the legal baseline yet, but it gives clearer guidance for building digital experiences that are easier to use and maintain. In practice, accessibility improvements also make websites smoother for everyone—especially on mobile.
Ready to Get Started?
WCAG 2.2 can feel like a lot. But you don’t have to figure it out alone.
Start now, take it step by step, and build accessibility into your organization’s culture; not as a one-time project, but as an ongoing practice.
Want something simple to share with your team? We created a practical, jargon-free guide that explains the new WCAG 2.2 success criteria in plain language.
Download our free WCAG 2.2 Quick Reference Guide to get clear next steps and move forward with confidence.
Because accessibility isn’t just about compliance. It’s about building a more inclusive digital world, one website at a time.