The Plot Twist Nobody Asked For: WCAG 2.2 Just Changed the Rules

Remember when you finally got your website accessible? Congratulations on that herculean effort - you deserve a medal, or at least a coffee that didn't come from the office kitchen. Well, plot twist: the Web Content Accessibility Guidelines just updated their requirements, and unless you've been obsessively checking the W3C website like some kind of standards masochist, your site is probably failing the new tests. It's like your website just walked out of a gym selfie era, only to discover it's now accountable to completely different fitness standards.

WCAG 2.2 dropped in October 2023, and it brought four major new success criteria that are basically the web's way of saying "we can do better than this." The kicker? Industry data suggests that roughly 71% of websites still don't meet these new requirements. Your site is probably in that club. Let's talk about why, and more importantly, what to do about it.

The Four Horsemen of WCAG 2.2: What Actually Changed

Focus Appearance (2.4.7) - Your Invisible Keyboard Users Are Having a Bad Time

This one's been around since WCAG 2.1, but 2.2 made it actually enforceable. Here's the deal: when someone tabs through your website using only a keyboard - and yes, these people exist and they're probably on your site right now - they need to see where the focus is. Like, actually see it. Not guess. Not squint and wonder if anything happened. Not assume their spacebar is broken.

The new rule: focus indicators need to be visible and not hidden by other content. Revolutionary concept, I know. But many sites treat focus outlines like they're visual acne - something to be hidden at all costs with outline: none and a prayer. This is the web development equivalent of removing the steering wheel from a car to make it "look cleaner." Sure, it looks slick until someone actually needs to drive it.

Your focus outline needs at least a 2px border (or equivalent) around the focused element
It can't be hidden behind anything - no sneaky z-index shenanigans
The contrast ratio between the focus indicator and the background needs to be 3:1

Dragging Movements (2.5.7) - Because Not Everyone Can Drag and Drop

So you've built this gorgeous drag-and-drop interface. Looks fantastic. Super intuitive. Perfect for the 80% of your users with a mouse and the physical ability to perform complex pointer movements. Congratulations on excluding the other 20%.

WCAG 2.2 now requires that any drag-and-drop functionality has an alternative method. You know, for people with limited mobility, tremors, or who just prefer using a keyboard because they're living in 1995 and have no regrets about it. This isn't optional anymore - it's required. You need a backup way to do anything that involves dragging. A button, a menu, an input field - something that doesn't require the fine motor skills of a surgeon performing microsurgery while standing on a moving train.

Target Size (2.5.8) - Stop Making Buttons the Size of Molecules

Remember those tiny little icons you thought looked super modern and minimalist? The ones that require you to have the precision of a marksman to click? WCAG 2.2 says: stop that.

Interactive targets now need to be at least 24x24 CSS pixels. That's the minimum. Not a suggestion. Not a "nice to have." An actual requirement. This is particularly important for mobile users, people with arthritis, and honestly, anyone who's ever tried to click a button on their phone while wearing gloves. Which is to say: everyone, at some point in their life.

Accessible Authentication (2.4.13) - Your Login Form Shouldn't Require a PhD

This is the one that makes sites sweat the most. WCAG 2.2 now requires that authentication processes be accessible. That means:

No CAPTCHA solving (or provide an alternative)
No multi-factor authentication that relies solely on complex cognitive function
Password managers should work properly with your forms

That riddle-style security question? The one where you have to remember your first pet's middle name? Probably doesn't pass anymore. Your login form might be inadvertently locking out users with cognitive disabilities, or anyone who just doesn't remember obscure personal details.

What You Should Actually Do About This

Here's the thing - you don't need to panic-hire an accessibility consultant (though they wouldn't mind). You need to run your site through a proper scan and see where you actually stand. Use automated tools to catch the low-hanging fruit, then do actual user testing with real people who use accessibility features.

WCAG 2.2 compliance isn't actually that hard when you think of it as "building for humans" instead of "complying with confusing standards." The new rules are basically the web saying "hey, remember those people who don't use your site exactly like you do? Let's make sure they can actually use it."

Want to know if your site is breaking these new WCAG 2.2 success criteria? Run it through SCOUTb2 and get a real assessment of where you actually stand. It takes about three minutes and might save you from a very awkward accessibility audit later.

Disclaimer: This article is for informational purposes only and does not constitute legal, professional, or compliance advice. SCOUTb2 is an automated scanning tool that helps identify common issues but does not guarantee full compliance with any standard or regulation.

WCAG 2.2 Added New Rules and Your Site Probably Breaks Them