WCAG 2.2 in Plain English, and What WCAG 3 Will Change

The Web Content Accessibility Guidelines, usually shortened to WCAG, are the technical standard most people mean when they talk about an accessible website. They're written by the World Wide Web Consortium (W3C), and they're precise, which also makes them hard to read if you run a bakery, a law office or a landscaping company rather than a web team.
This post translates the newest version, WCAG 2.2, into plain English, focuses on the parts that are new since WCAG 2.1, and explains what the still-in-progress WCAG 3 draft looks like as of fall 2026.
A quick map of WCAG
WCAG is organized around four principles. Content should be perceivable (people can see or hear it in some form), operable (people can use it with a mouse, keyboard, touch or other tools), understandable (it behaves in predictable ways and helps people avoid mistakes) and robust (it works with browsers and assistive technology like screen readers).
Under those principles sit testable rules called success criteria. Each one has a level: A is the baseline, AA builds on it, and AAA is the most demanding. Level AA is the target most often referenced in the United States. The Department of Justice's rule for state and local government websites, for example, points to WCAG 2.1 Level AA, which we cover in our DOJ Title II deadlines explainer. WCAG versions are built to be backward compatible, so content that meets 2.2 also meets 2.1 and 2.0.
What changed in WCAG 2.2
W3C published WCAG 2.2 as a formal Recommendation on October 5, 2023. It kept almost everything from 2.1, added 9 new success criteria and removed one old one, 4.1.1 Parsing. Parsing dealt with things like duplicate attributes in HTML, and W3C concluded that modern browsers and assistive technology handle those problems well enough that the rule no longer earned its place.
Most of the new criteria help people who use a keyboard instead of a mouse, people with limited hand control, and people with cognitive or memory disabilities. Here are the six that sit at Level A or AA, in everyday terms.
1. Don't hide the thing that has focus (2.4.11, AA)
When someone moves through a page with the Tab key, the item they land on is "in focus." This rule says that item can't be completely covered by something you put on the page, like a sticky header, a cookie banner or a chat bubble. Part of it has to stay visible.
How to check: Press Tab slowly through your home page and a key form. Watch for any moment where the highlighted link or button disappears behind a bar or pop-up.
2. Offer a way that doesn't need dragging (2.5.7, AA)
If something on your site works by dragging, such as a price slider, a reorderable list or a map, there should also be a way to do it with simple clicks or taps. Think plus and minus buttons, arrow buttons or a text box where people can type a value.
How to check: List every drag interaction on your site and try to complete each one without dragging.
3. Make tap targets big enough, or space them out (2.5.8, AA)
Buttons and links should be at least 24 by 24 CSS pixels, or have enough empty space around them that a 24-pixel circle centered on each one wouldn't overlap its neighbors. Links inside a sentence are exempt. This helps anyone with a tremor, and anyone on a bumpy bus.
How to check: On your phone, look for clusters of tiny icons, like social links in the footer or small "x" close buttons, and make sure they aren't crowded together.
4. Keep help in the same place (3.2.6, A)
If you offer help on several pages, such as a phone number, a contact link, a chat tool or an FAQ link, put it in the same relative spot each time. Visitors who struggle to find things shouldn't have to hunt for help on every page.
How to check: Compare your header and footer across a few pages. Your contact details should appear in the same order and area.
5. Don't make people type the same thing twice (3.3.7, A)
In a multi-step process, like a checkout or a booking form, information someone already entered should be filled in for them or offered as a choice. The classic example is a "billing address is the same as shipping" checkbox. There are exceptions for security, such as confirming a new password.
How to check: Walk through your own checkout or intake form and note anything you're asked for more than once.
6. Let people log in without a memory test (3.3.8, AA)
Logging in shouldn't depend on remembering, solving or retyping something unless there's help or another way in. In practice, that means letting password managers fill the password field, allowing copy and paste into password and code fields, and offering an alternative to puzzle-style challenges. Email login links and passkeys are also good options.
How to check: Try pasting a password into your login form. If the site blocks pasting, that's worth fixing.
The three AAA additions
WCAG 2.2 also added three Level AAA criteria: a stricter version of the focus rule where the focused item must be fully visible (2.4.12), a rule for how large and how high-contrast a focus indicator should be (2.4.13), and a stricter login rule that doesn't allow even picture-recognition tests (3.3.9). They aren't usually the baseline, but a clear, thick focus outline is a smart choice anyway. We go deeper on outlines and colors in accessible colors and fonts.
Don't forget the older basics
The new criteria get attention, but most problems on small business sites come from rules that have been around since WCAG 2.0: missing image descriptions, low contrast text, empty links and buttons, form fields without labels and pages that can't be used with a keyboard. If you haven't covered those, start there. Our 10 quick accessibility fixes walks through the common ones, and our roundup of free accessibility testing tools shows how to find them.
Automated tools can catch some of these issues, but not all of them. Several of the new 2.2 rules, like consistent help and redundant entry, need a person to look. And no single tool or widget makes a site conform on its own, a point we explain in Can a widget alone make a site accessible?
Where WCAG 3 stands
WCAG 3 is a separate, much bigger rewrite. Even the name changes: it's planned as the "W3C Accessibility Guidelines," because it's meant to cover apps, tools and newer technologies, not only web content. W3C describes it as an incomplete draft that will change, and says it isn't expected to be a finished standard for a few more years.
The draft W3C updated in September 2026 points to a few big ideas:
- A different structure. Guidelines are written as outcomes, with core requirements, supplemental requirements, assertions and recommended practices underneath.
- A new way to measure progress. In that draft, conforming means meeting all core requirements. Each core requirement gets a tag based on what happens to a person with a disability when it's missed: physical harm, risk, a barrier that stops them, or friction that slows them down. Reporting tiers built on those tags would let an organization show progress toward conformance and beyond it.
- Broader coverage, including more needs of people with cognitive disabilities.
Two points matter most for a business owner. First, WCAG 3 isn't something to build to yet, because its requirements will still be edited, added, combined and removed. Second, W3C says WCAG 2 won't be deprecated for several years after WCAG 3 is finalized, and that the best way to prepare for WCAG 3 is to meet WCAG 2.2 now. In other words, work you do today on 2.2 carries forward.
A simple plan for the next month
- Week 1: Run an automated scan to find the common, machine-detectable issues and fix the quick ones.
- Week 2: Do the keyboard test. Tab through your main pages, and check that focus is always visible and never hidden behind sticky bars.
- Week 3: Check your phone layout for small or crowded buttons, and look for any drag-only controls.
- Week 4: Walk through your forms and login. Remove repeated questions, allow pasting and keep your help links in a consistent spot. Then note what you've done in an accessibility statement.
If you're weighing tools to help with ongoing monitoring, our accessibility tool comparison lays out what each option does, with sources.
The bottom line
WCAG 2.2 is the current version of the standard, and its additions are practical: keep focus visible, give people alternatives to dragging, make targets easy to hit, keep help easy to find, stop asking twice and make login easier. WCAG 3 is worth watching, but W3C's own advice is to keep working on 2.2.
This article is general information, not legal advice. For questions about your specific obligations, talk with a qualified attorney. When you're ready to see where your site stands, run a free scan of your site and get a prioritized list of what to fix first.
Frequently asked questions
What is the current version of WCAG?
WCAG 2.2, published by W3C as a Recommendation on October 5, 2023, is the current version. WCAG 3 is still a working draft.
What's new in WCAG 2.2 compared with 2.1?
WCAG 2.2 adds 9 success criteria covering focus visibility, dragging alternatives, target size, consistent help, redundant entry and accessible login, and it removes 4.1.1 Parsing.
If my site meets WCAG 2.2, does it also meet WCAG 2.1?
Yes. WCAG 2.2 is built to be backward compatible, so content that meets 2.2 also meets 2.1 and 2.0 at the same level.
When will WCAG 3 be finished?
W3C says WCAG 3 isn't expected to be a completed standard for a few more years, and WCAG 2 won't be deprecated for several years after that.
Should I build my site to WCAG 3 now?
Not yet. The draft will change, and W3C recommends meeting WCAG 2.2 now as the best way to prepare.
Comparing tools? See our accessibility widget comparison.
Sources
- W3C: Web Content Accessibility Guidelines (WCAG) 2.2
- W3C WAI: What's New in WCAG 2.2
- W3C WAI: WCAG 2 Overview
- W3C WAI: WCAG 3 Introduction (updated September 2026)
- W3C: W3C Accessibility Guidelines (WCAG) 3.0 Working Draft
- Federal Register: Nondiscrimination on the Basis of Disability; Accessibility of Web Information and Services of State and Local Government Entities (2024)
Disclaimer: This article is general information, not legal advice. Laws and dates can change. A toolbar alone doesn't make a website conform; we help reduce risk and improve access.