WCAG 2.1 Explained: What It Means for Website Accessibility

CAG 2.1, the Web Content Accessibility Guidelines version 2.1, is the technical standard published by the World Wide Web Consortium (W3C) that most accessibility laws now point to. W3C released it on June 5, 2018, as an extension of WCAG 2.0. It adds criteria for mobile devices, low vision, and cognitive disabilities.

WCAG 2.1 compliance matters today because it is the standard named in the DOJ’s ADA Title II rule and the HHS Section 504 rule. It is also the benchmark most often cited in private-sector settlements. This article covers what WCAG 2.1 is, where the law requires it, what Level AA demands, and whether it is still enough.

What Is WCAG 2.1?

The WCAG 2.1 guidelines keep the structure of WCAG 2.0 and add new criteria on top of it. Every original success criterion remains in place with the same number, so organizations that already meet WCAG 2.0 only need to check the new additions rather than start over.

A Brief History: From WCAG 2.0 to 2.1

W3C published WCAG 2.1 ten years after WCAG 2.0, to close gaps the older standard left open, particularly for touch screens and users with low vision. It does not replace WCAG 2.0. It extends it, keeping every original criterion and its numbering.

The Four Principles and Conformance Levels

WCAG 2.1 is organized around four principles: perceivable, operable, understandable, and robust. It contains 78 success criteria across three conformance levels. Level A covers the basics, Level AA addresses the most common barriers, and Level AAA is the most demanding. Meeting Level AA means meeting all Level A and Level AA criteria, 50 in total.

What WCAG 2.1 Added to WCAG 2.0

WCAG 2.1 added 17 success criteria: five at Level A, seven at Level AA, and five at Level AAA. For organizations already meeting WCAG 2.0 AA, that means 12 new criteria to address. They fall into three groups: mobile accessibility, low vision, and cognitive and input support.

Where WCAG 2.1 Is Required by Law

Several laws now name WCAG 2.1 directly, and others rely on it in practice.

ADA Title II

The DOJ’s 2024 rule requires state and local governments to meet WCAG 2.1 AA for web content and mobile apps. Entities serving 50,000 or more people had to comply by April 24, 2026, a deadline that has passed. Smaller entities and special district governments have until April 26, 2027. Our ADA Title II article covers the rule in detail.

Section 504 and the HHS Rule

HHS’s 2024 rule requires organizations receiving HHS funding to meet WCAG 2.1 Levels A and AA. After the May 2026 extension, recipients with 15 or more employees must comply by May 11, 2027, and smaller recipients by May 10, 2028. Our Section 504 article covers who is covered.

ADA Title III and Settlements

Title III has no codified technical standard for private businesses. In practice, WCAG 2.1 AA is the benchmark most often used in demand letters, settlements, and consent decrees, which makes it the safest working target for businesses open to the public.

What WCAG 2.1 AA Requires for Websites

The criteria WCAG 2.1 added at Levels A and AA fall into three areas, each aimed at a distinct group of users.

Mobile and Touch Accessibility

• Orientation (1.3.4): content must work in both portrait and landscape.
• Pointer Gestures (2.5.1): any function that needs a multi-finger or path-based gesture must also work with a single tap or click.
• Pointer Cancellation (2.5.2): actions should not fire on the down-click, so users can cancel a mistaken touch.
• Motion Actuation (2.5.4): features triggered by shaking or tilting a device need a standard alternative.

Low Vision Accessibility

• Reflow (1.4.10): content must adapt to a narrow screen or high zoom without horizontal scrolling.
• Non-text Contrast (1.4.11): buttons, form borders, and icons need a contrast ratio of at least 3:1.
• Text Spacing (1.4.12): content must stay readable when users increase line, letter, and word spacing.
• Content on Hover or Focus (1.4.13): pop-ups and tooltips must be dismissible without moving the pointer or focus.

Cognitive and Input Support

• Identify Input Purpose (1.3.5): form fields for personal data must be programmatically identified so browsers can autofill them.
• Label in Name (2.5.3): an element’s accessible name must include its visible label, which helps voice control users.
• Character Key Shortcuts (2.1.4): single-key shortcuts must be able to be turned off or remapped.
• Status Messages (4.1.3): updates such as “item added to cart” must be announced to screen reader users without moving focus.

Reflow, text spacing, and hover behavior are hard to check with automated scans, so a manual website accessibility audit is the reliable way to confirm them.

WCAG 2.1 vs. WCAG 2.0 and 2.2

WCAG 2.1 builds on WCAG 2.0, so content that meets 2.1 AA also meets the 2.0 requirements. WCAG 2.2, released in 2023, builds on 2.1 in turn. It adds nine criteria, including Focus Not Obscured, Target Size (Minimum), and Accessible Authentication, and it removes 4.1.1 Parsing as obsolete.

Is WCAG 2.1 AA Enough for Compliance?

For ADA Title II and the HHS Section 504 rule, yes. Both name WCAG 2.1 AA as the required standard. For Title III, it is the strongest practical benchmark available. Section 508 formally names WCAG 2.0 AA, so meeting 2.1 AA exceeds that requirement.

The remaining question is whether to build to WCAG 2.2 AA. It is not yet the named standard in these laws, but building to it now covers 2.1 AA and prepares a site for future updates.

FAQ

What is WCAG 2.1?

WCAG 2.1 is the 2018 version of the Web Content Accessibility Guidelines, published by W3C. It contains 78 success criteria and extends WCAG 2.0 with criteria for mobile, low vision, and cognitive accessibility.

What is the difference between WCAG 2.0 and 2.1?

WCAG 2.1 keeps every WCAG 2.0 criterion and adds 17 more. Twelve of them are at Level A or AA, which are the levels most laws require.

Does the ADA require WCAG 2.1?

The ADA itself names no technical standard. The DOJ’s Title II rule requires WCAG 2.1 AA for state and local governments, and Title III has no codified standard, though WCAG 2.1 AA is the benchmark most often used in settlements.

How many success criteria are in WCAG 2.1 AA?

WCAG 2.1 Level AA includes 50 success criteria: all 30 Level A criteria and all 20 Level AA criteria.

Should I build to WCAG 2.1 or WCAG 2.2?

Most laws currently name WCAG 2.1 AA, so it is the minimum target. Building to WCAG 2.2 AA satisfies 2.1 AA as well and adds protection as laws and settlements begin to reference the newer version.