WCAG 2.1 vs. WCAG 2.2: What Changed and What Your District Needs to Know
By Kalin Schoephoerster | KShep Creative
This is the third post in a six-part series on WCAG for K–12 districts. Previous posts cover what WCAG is → and what the conformance levels mean →.
Here's a question that comes up often in K–12 accessibility conversations: ADA Title II requires WCAG 2.1 Level AA — but WCAG 2.2 is the current standard. So which one does a district actually need to meet?
It's a reasonable question, and the answer isn't obvious until someone explains how WCAG versions work. Districts that are just starting their accessibility work need to know which target to aim for. Districts that are already working toward 2.1 conformance need to know whether 2.2 changes anything for them. And anyone evaluating a vendor's accessibility claims needs to understand what it means when a product says it supports one version but not the other.
This post resolves the confusion directly — what changed between versions, what the law actually requires, and what the practical recommendation is for your district.
A quick recap — how WCAG versions work
WCAG versions don't replace each other. They build on each other.
WCAG 2.1 added 17 new success criteria to WCAG 2.0. WCAG 2.2 added 9 new success criteria to WCAG 2.1. Each version contains everything the previous version required, plus additional criteria that address gaps the earlier version didn't fully cover.
This is the backward compatibility rule, and it's the key to understanding why the 2.1 vs. 2.2 question is less complicated than it first appears. A site that conforms to WCAG 2.2 automatically conforms to WCAG 2.1 — because 2.2 includes all of 2.1's requirements plus more. The versions aren't competing standards. They're a progression.
What ADA Title II actually requires
The ADA Title II regulations finalized in 2024 require public school districts to conform to WCAG 2.1 Level AA. That's the specific version cited in the rule. Compliance deadlines are phased: districts serving populations of 50,000 or more had a deadline of April 24, 2026. Smaller districts and special districts have until April 26, 2027.
WCAG 2.1 was the most current published version of WCAG when the rule was being developed and finalized. WCAG 2.2 was published in October 2023, after the regulatory process was already underway. That timing is why 2.1 is in the rule rather than 2.2 — not because regulators preferred the older version, but because 2.2 wasn't available yet when the requirement was being written.
For a full breakdown of what the ADA Title II rule requires and what your district's timeline looks like, see What K–12 Districts Need to Know About the New Federal Digital Accessibility Rules →.
What WCAG 2.2 added
WCAG 2.2 introduced nine new success criteria, grouped around three areas where the previous version had gaps.
Cognitive disabilities. Several new criteria address the needs of people with memory, attention, and processing challenges. Authentication processes can't rely solely on memorizing a password or solving a cognitive puzzle — there must be an accessible alternative such as copy-paste support or a second device. Processes with multiple steps must allow users to access help without losing their work. These are real barriers that affected real users and weren't covered under 2.1.
Low vision and motor accessibility. New criteria address the size and spacing of interactive elements. Buttons, links, and controls must meet minimum target size requirements so they can be activated without accidentally triggering adjacent elements — something that matters especially on mobile devices and for users with limited motor control. Focus appearance requirements were also strengthened, making it easier for keyboard users to see where they are on a page.
One removal. WCAG 2.2 also retired one criterion from 2.1: Success Criterion 4.1.1 Parsing, which required HTML to be structured in a way that assistive technologies could reliably interpret. Modern browsers and screen readers have become sophisticated enough that the underlying problem this criterion addressed is now handled automatically. Retiring it simplified the standard without reducing protection for users.
The additions in 2.2 are meaningful improvements — not arbitrary changes. They reflect real accessibility gaps that affected real users and weren't adequately addressed in the previous version.
The backward compatibility rule — and why it matters for your district
Because WCAG versions are cumulative, the backward compatibility rule has a practical implication that's worth stating plainly: conforming to WCAG 2.2 Level AA automatically satisfies the WCAG 2.1 Level AA legal requirement under ADA Title II.
Districts don't have to choose between meeting the law and following the current standard. Building to 2.2 does both at once.
This also means that districts currently working toward WCAG 2.1 conformance don't need to start over when they decide to build to 2.2. The work transfers. Meeting the 2.1 criteria puts a district most of the way to 2.2 — the additional 2.2 criteria are incremental, not a separate track.
The one exception worth noting: the 4.1.1 Parsing criterion that was removed in 2.2. A site audited against 2.1 may have been evaluated on that criterion. Under 2.2, it's no longer applicable. In practice this is a minor point — meeting 4.1.1 was generally a baseline HTML quality practice anyway — but it's worth knowing if you're comparing audit results across versions.
Should your district build to 2.1 or 2.2?
The direct answer: build to WCAG 2.2.
Three reasons support that recommendation clearly.
2.2 is the current standard. It reflects the most up-to-date thinking on what accessible content requires. It covers user needs that 2.1 didn't fully address. Building to an older standard when a better one is available is a short-term decision that creates more work later.
Backward compatibility means there's no compliance risk. Building to 2.2 satisfies the 2.1 legal requirement automatically. There's no downside to exceeding the stated requirement — only benefit for the users who access your district's content.
Legal requirements tend to follow current standards over time. When ADA Title II regulations are next updated, they're likely to reference WCAG 2.2 rather than 2.1. Districts that have already built to 2.2 won't need to close a gap when that happens. Districts that stopped at 2.1 will.
One honest caveat: some tools and platforms may not yet fully support producing WCAG 2.2 conformant output for every criterion. In those cases, building to 2.1 with those tools is the practical choice while they catch up — but the target should still be 2.2 wherever it's achievable. Ask vendors for their WCAG 2.2 roadmap if their current VPAT only covers 2.1.
What comes next
The next post in this series steps back from versions and levels to look at the underlying framework that organizes all of WCAG: the four principles known as POUR — Perceivable, Operable, Understandable, and Robust. Understanding POUR makes the individual success criteria easier to navigate and helps districts see the logic behind the standard rather than just a list of requirements.
[The Four Principles of WCAG: What POUR Means in Plain Language → coming soon]
The version question has a clear answer
WCAG 2.1 is what ADA Title II requires. WCAG 2.2 is the current standard. Because of backward compatibility, building to 2.2 satisfies both — and positions your district for where requirements are heading, not just where they are today.
Whether your district is just starting its accessibility work or is already working toward conformance, the starting point is the same: knowing where your current content stands. An accessibility audit gives you that picture and a prioritized plan for addressing what you find.
Book a free 30-minute intro call →
Or explore accessibility audit and remediation services → to see what evaluating your district's content against WCAG actually involves.
Kalin Schoephoerster is a CPACC-certified instructional designer and accessibility consultant based in St. Paul, MN. KShep Creative partners with K–12 districts, higher education institutions, and EdTech organizations to develop accessible eLearning, instructor-led training, curriculum, SOPs, and website accessibility audits aligned with WCAG 2.2 and ADA Title II requirements.