Web Content Accessibility Guidelines (WCAG) 2.1

Plain English Summary

WCAG 2.1 is the successor to WCAG 2.0, published by the W3C in June 2018. It includes all of the requirements from WCAG 2.0 and adds 17 new success criteria that address three areas where WCAG 2.0 had gaps: mobile device accessibility, support for people with low vision, and support for people with cognitive and learning disabilities.

This matters because the web has changed dramatically since WCAG 2.0 was published in 2008. In 2008, most web browsing happened on desktop computers. By 2018, mobile devices accounted for the majority of web traffic, and touch interfaces had become the norm. WCAG 2.1 ensures that accessibility standards keep pace with how people actually use the web.

WCAG 2.1 Level AA has become the emerging legal standard. The DOJ's landmark 2024 Title II rule explicitly adopted WCAG 2.1 Level AA for state and local government websites and mobile apps. Courts and settlement agreements are increasingly referencing WCAG 2.1 rather than 2.0. For any organization seeking to be compliant with current accessibility expectations, WCAG 2.1 AA is the target.

Who This Applies To

Legally Required:

• State and local governments under the 2024 Title II web accessibility rule (WCAG 2.1 AA explicitly required)
• Organizations in the EU subject to the European Accessibility Act and EN 301 549 (which references WCAG 2.1)
• Organizations in Canada subject to the Accessible Canada Act

Practically Expected:

• Private businesses subject to ADA Title III (courts increasingly reference WCAG 2.1)
• Federal agencies (Section 508 currently references WCAG 2.0, but updates to align with 2.1 are expected)
• Any organization entering into an accessibility settlement agreement (most now reference WCAG 2.1 AA)
• Organizations seeking to meet current best practices for accessibility

Key Requirements

Everything in WCAG 2.0 Plus 17 New Success Criteria

WCAG 2.1 includes all 61 success criteria from WCAG 2.0 and adds 17 new ones:

New Level A Criteria (5):

• 2.1.4 Character Key Shortcuts: If keyboard shortcuts use single character keys, users must be able to turn them off or remap them. This prevents accidental activation, especially for speech input users.
• 2.5.1 Pointer Gestures: Functionality that uses multipoint or path-based gestures must also be operable with single-point activation. This helps users who cannot perform complex gestures.
• 2.5.2 Pointer Cancellation: For single-pointer functions, at least one of the following is true: the down-event is not used, completion is on the up-event with an abort mechanism, or the up-event reverses the down-event.
• 2.5.3 Label in Name: For UI components with visible text labels, the accessible name must contain the visible text. This ensures speech input users can activate controls by speaking their visible label.
• 2.5.4 Motion Actuation: Functionality triggered by device motion (like shaking or tilting) must also be available through a user interface, and motion activation can be disabled.

New Level AA Criteria (7):

• 1.3.4 Orientation: Content does not restrict its view and operation to a single display orientation unless a specific orientation is essential.
• 1.3.5 Identify Input Purpose: The purpose of input fields collecting user information can be programmatically determined, enabling autofill and personalized presentations.
• 1.4.10 Reflow: Content can be presented without loss of information at 320 CSS pixels wide (equivalent to 400% zoom) without horizontal scrolling.
• 1.4.11 Non-text Contrast: UI components and graphical objects have a contrast ratio of at least 3:1 against adjacent colors.
• 1.4.12 Text Spacing: No loss of content or functionality when users adjust text spacing properties (line height, paragraph spacing, letter spacing, word spacing).
• 1.4.13 Content on Hover or Focus: Content that appears on hover or focus can be dismissed, hovered over, and persists until dismissed.
• 4.1.3 Status Messages: Status messages can be programmatically determined through role or properties so they can be presented to assistive technology users without receiving focus.

New Level AAA Criteria (5):

• 1.3.6 Identify Purpose: The purpose of UI components, icons, and regions can be programmatically determined.
• 2.2.6 Timeouts: Users are warned of inactivity timeouts unless data is preserved for 20+ hours.
• 2.3.3 Animation from Interactions: Motion animation triggered by interaction can be disabled unless essential.
• 2.5.5 Target Size: Touch targets are at least 44x44 CSS pixels.
• 2.5.6 Concurrent Input Mechanisms: Content does not restrict input modalities (users can switch between touch, keyboard, mouse, etc.).

Enforcement and Penalties

Title II (2024 Rule)

The DOJ's 2024 final rule explicitly adopts WCAG 2.1 Level AA for state and local government web content and mobile apps. This is the first federal regulation to mandate WCAG 2.1 specifically. Enforcement follows standard Title II mechanisms: DOJ investigation, private lawsuits, compensatory damages, and potential loss of federal funding.

Title III (Private Businesses)

While no federal regulation mandates WCAG 2.1 for private businesses, courts and settlement agreements are increasingly referencing WCAG 2.1 AA rather than 2.0. Plaintiffs' attorneys routinely test against WCAG 2.1.

International

WCAG 2.1 AA is the standard in the EU's EN 301 549, the European Accessibility Act, and accessibility laws in Canada, Australia, and numerous other countries.

Penalties Mirror the Underlying Law

Since WCAG 2.1 is enforced through other laws, penalties depend on the legal context:

• Title II: Compensatory damages (no cap), injunctive relief, attorneys' fees
• Title III: Injunctive relief, civil penalties up to $150,000, attorneys' fees
• Section 508: Administrative remedies, injunctive relief
• State laws: Varies by state; some allow significant monetary damages

Practical Implications

For Organizations Currently at WCAG 2.0 AA

The upgrade from WCAG 2.0 AA to WCAG 2.1 AA requires meeting 12 additional success criteria (5 at Level A and 7 at Level AA). Key areas to focus on:

• Mobile responsiveness: Ensure content reflows at 320px width without horizontal scrolling (1.4.10). This is often the most labor-intensive new requirement.
• Non-text contrast: Audit all UI elements -- buttons, form field borders, icons, chart elements -- for 3:1 contrast ratio (1.4.11).
• Text spacing: Test that your layouts handle increased text spacing without breaking (1.4.12). Avoid fixed-height containers.
• Tooltips and popovers: Ensure hover/focus content can be dismissed, hovered, and is persistent (1.4.13).
• Touch target sizes: While 44x44 is AAA, aim for it in practice, especially on mobile.

For New Projects

• Start with WCAG 2.1 AA from day one. There is no reason to build to WCAG 2.0 when 2.1 is the current standard.
• Design for mobile first. Many of the new WCAG 2.1 criteria address mobile and touch interaction patterns.
• Test on real mobile devices. Desktop browser dev tools do not fully replicate mobile assistive technology behavior.

For Government Entities

• The clock is ticking. Large government entities (50,000+ population) must comply by April 24, 2026. Smaller entities have until April 26, 2027.
• Audit against WCAG 2.1, not 2.0. The Title II rule specifically requires WCAG 2.1 AA. Auditing against 2.0 will miss required criteria.

Key Dates and Deadlines

| Date | Event | |------|-------| | June 5, 2018 | WCAG 2.1 published as a W3C Recommendation | | September 21, 2023 | WCAG 2.1 confirmed as part of ISO/IEC 40500 | | April 24, 2024 | DOJ Title II rule adopts WCAG 2.1 AA for government web accessibility | | April 24, 2026 | Title II compliance deadline for large government entities | | April 26, 2027 | Title II compliance deadline for small government entities |

---

This content is provided for educational and informational purposes only and does not constitute legal advice. For guidance on your specific situation, consult a qualified attorney. Laws and regulations are subject to change, and this information may not reflect the most current legal developments.