As digital creators, our work shapes how people interact with the web. But not everyone experiences the web the same way. For millions of users with disabilities, websites can either be empowering—or completely inaccessible.
That’s why the Web Content Accessibility Guidelines (WCAG) matter so much. In October 2023, WCAG 2.2 was officially published by the W3C, introducing new success criteria that raise the bar for inclusivity.
Whether you’re a web developer, designer, or product owner, here’s what you need to know—and how you can start applying WCAG 2.2 today.
What Is WCAG?
The Web Content Accessibility Guidelines (WCAG) are internationally recognized standards for making web content more accessible to people with disabilities—including those who are blind, deaf, have mobility impairments, or cognitive disabilities.
These guidelines are organized under four key principles:
Perceivable
Operable
Understandable
Robust
Each version of WCAG introduces or updates “success criteria” that websites must meet to be considered accessible.
What’s New in WCAG 2.2?
WCAG 2.2 builds on 2.1 with 9 new success criteria—mostly focused on cognitive accessibility, low vision, and mobile usability.
Here are some key highlights:
1. Focus Not Obscured (Minimum and Enhanced)
These criteria ensure that when users tab through elements using a keyboard, the focused item isn’t hidden behind sticky headers or overlays.
Why it matters: Users relying on keyboard navigation (e.g., screen reader users or those with motor impairments) need to clearly see where they are on the page.
2. Dragging Movements
If a feature requires dragging (like sliders or drag-and-drop interfaces), there must be an alternative method (like clicking).
Why it matters: This helps users with limited motor skills who can’t perform dragging gestures.
3. Target Size (Minimum)
Touch targets (like buttons and links) must be at least 24 by 24 CSS pixels.
Why it matters: Prevents accidental taps—especially for users with tremors or those using mobile devices.
4. Accessible Authentication (Minimum and Enhanced)
Users must be able to authenticate (e.g., log in) without solving puzzles, remembering passwords, or deciphering complex CAPTCHAs—unless an accessible alternative is provided.
Why it matters: Supports users with cognitive impairments and improves usability for all.
Why Web Creators Should Care
💡 Accessibility Benefits Everyone
Accessible design makes websites easier to use for all users—think better contrast, more intuitive navigation, and mobile-friendly features.
⚖️ It’s a Legal Requirement
In many countries, accessibility is a legal obligation for public sector and private organizations. Non-compliance can lead to lawsuits, fines, or exclusion from key markets.
🧩 It’s Good UX
From clearer buttons to smoother interactions, accessibility overlaps with user-centered design. It’s not just about ticking boxes—it’s about crafting better digital experiences.
How to Start Implementing WCAG 2.2
✅ Audit your website
Use tools like Lighthouse, axe DevTools, or WAVE to check current accessibility levels.
✅ Update your design systems
Ensure spacing, color contrast, font sizes, and touch targets follow the new standards.
✅ Include accessibility in your workflow
Make accessibility a routine part of design reviews, development sprints, and QA testing.
✅ Educate your team
Ensure everyone—from PMs to designers to developers—understands the importance of accessibility and how to implement it.
