What is WCAG 2.2 and Why Your Website Could Be Violating It Right Now

In 2025, ADA website accessibility lawsuits hit a record high — over 4,000 cases filed in US federal court alone. The businesses named in those suits were not dark-web operators or fly-by-night shops. They were e-commerce brands, SaaS companies, and healthcare portals with functional, professionally built websites. The common thread: their sites failed WCAG 2.2, the international standard for web accessibility — and nobody caught it before a plaintiff's attorney did.

If you've never audited your site for WCAG 2.2 compliance, there's a high probability you're violating it right now. This guide explains what WCAG 2.2 is, why it carries real legal weight in 2026, the seven violations that show up on almost every site we scan, and how to find and fix them before a demand letter lands in your inbox.

What is WCAG 2.2?

WCAG stands for Web Content Accessibility Guidelines — a set of technical criteria published by the World Wide Web Consortium (W3C) to make web content usable by people with disabilities. The guidelines cover visual, auditory, cognitive, and motor impairments.

The standard has evolved over time:

• WCAG 2.0 (2008) — the foundation. Established the baseline for accessibility law compliance.
• WCAG 2.1 (2018) — added 17 new criteria addressing mobile accessibility and low-vision users.
• WCAG 2.2 (September 2023) — the current version, adding 9 more criteria focused on keyboard navigation, focus visibility, and touch target sizing.

The Four Principles: POUR

Every WCAG criterion maps to one of four principles:

1. Perceivable — users can detect all information on the page (text alternatives for images, captions for video, sufficient color contrast).
2. Operable — users can interact with all controls (keyboard navigation, no time traps, accessible drag operations).
3. Understandable — content and interfaces are clear and predictable (descriptive error messages, consistent navigation).
4. Robust — content works with current and future assistive technologies (semantic HTML, valid markup).

Conformance Levels: A, AA, and AAA

WCAG uses three conformance levels:

• Level A — minimum accessibility. Failing these criteria creates barriers for users with disabilities.
• Level AA — the legal target in the US, EU, and Canada. This is what courts, regulators, and accessibility policies require.
• Level AAA — enhanced accessibility. Aspirational for most products; not required by law.

When a compliance checklist says "WCAG 2.2 compliant," it means WCAG 2.2 Level AA — all Level A and all Level AA criteria.

What's New in WCAG 2.2

The nine new criteria in 2.2 include:

• Focus Appearance (2.4.11, 2.4.12) — keyboard focus indicators must be visible and meet minimum size/contrast thresholds.
• Dragging Movements (2.5.7) — any operation using a drag gesture must have a single-pointer alternative.
• Target Size (Minimum) (2.5.8) — interactive targets must be at least 24x24 CSS pixels (or have sufficient spacing).

These additions directly affect keyboard-only users, mobile users, and people with motor impairments.

Why WCAG Compliance Is Now a Legal Requirement

WCAG is not a government regulation — it's a technical standard. So why do so many lawsuits reference it?

ADA Title III and the Courts

The Americans with Disabilities Act (ADA), passed in 1990, requires that places of "public accommodation" be accessible. Courts have consistently ruled that websites operated by businesses open to the public are covered under Title III. The landmark Robles v. Domino's Pizza ruling (9th Circuit, 2019) confirmed that the ADA applies to websites and apps, not just physical locations.

Since the DOJ has not issued prescriptive regulations specifying a technical standard for private-sector websites, plaintiffs' attorneys use WCAG 2.1 AA — and increasingly WCAG 2.2 AA — as the de facto benchmark for "accessible." If your site fails those criteria, you're exposed.

The DOJ's March 2024 Final Rule

In March 2024, the Department of Justice issued a final rule requiring state and local government websites to conform to WCAG 2.1 Level AA by specific deadlines. While this rule directly targets government entities, it establishes WCAG 2.1/2.2 as the regulatory standard — a benchmark plaintiff attorneys now cite in private-sector cases.

For DOJ Title II deadline context for government portals, see our article on the April 24, 2026 DOJ Title II deadline.

Global Scope

ADA exposure is US-specific, but WCAG compliance is a global requirement:

• EU Web Accessibility Directive — requires public-sector sites and certain apps to meet EN 301 549, which references WCAG 2.1 AA.
• European Accessibility Act (EAA) — extends requirements to private-sector products and services from June 2025.
• AODA (Canada) — Ontario's Accessibility for Ontarians with Disabilities Act mandates WCAG 2.0 AA, with 2.1 AA increasingly referenced in enforcement.

Who Gets Sued

ADA web accessibility suits are not random. The most targeted industries are:

• E-commerce — product pages, checkout flows, image-heavy catalogs
• SaaS — dashboards, form-heavy UIs, interactive data visualizations
• Healthcare — patient portals, appointment booking, prescription management
• Education — LMS platforms, course catalogs, video content
• Government portals — by regulation, not just lawsuit

The financial exposure is real: settlements average $25,000–$100,000 per case, and serial litigants file dozens of suits per week using automated scanning to identify vulnerable sites.

Accessibility overlays marketed as instant compliance fixes do not protect you. We cover why in detail in our article Accessibility Overlays Get You Sued and explore the implications of the FTC's recent action in accessiBe Alternatives After the FTC Fine.

The 7 Most Common WCAG 2.2 Violations

After scanning thousands of sites, TrueComply's AI engine has identified the violations that appear most frequently — and are most likely to form the basis of a demand letter.

1. Missing Alt Text on Images (WCAG 1.1.1)

What it is: Images without descriptive alt attributes are invisible to screen readers. Users relying on assistive technology get no information about the image's content or function.

Real-world example: A product photo with alt="" or alt="image_1234.jpg" — a screen reader user has no idea what the product is.

Severity: High. This is one of the most frequently cited violations in ADA demand letters.

2. Insufficient Color Contrast (WCAG 1.4.3)

What it is: Text must have a contrast ratio of at least 4.5:1 against its background (3:1 for large text). Light gray text on a white card, or white text over a mid-tone photo, typically fails.

Real-world example: A "Submit" button with #a0a0a0 text on a #ffffff background — contrast ratio ~1.6:1, well below the 4.5:1 threshold.

Severity: Medium-High. Automated scanners catch this reliably, making it easy for plaintiffs to document and cite.

3. Non-Keyboard-Navigable Interactive Elements (WCAG 2.1.1)

What it is: Every interactive element — buttons, links, dropdowns, modals, sliders — must be reachable and operable using only a keyboard (Tab, Enter, Arrow keys, Escape).

Real-world example: A custom-built dropdown menu that works on hover but is unreachable via Tab key, locking out keyboard-only users entirely.

Severity: High. Keyboard accessibility is a foundational requirement; failures often block entire workflows.

4. Missing Form Labels and Error Messages (WCAG 1.3.1, 3.3.1, 3.3.2)

What it is: Every form input must have a programmatically associated label. Error messages must identify the field in error and describe the problem — not just highlight it in red.

Real-world example: A contact form using placeholder text as the only label — once a user starts typing, they've lost all context about what the field is for. Error feedback that says "Invalid entry" without specifying which field or why.

Severity: High. Form failures directly prevent users from completing key conversion flows.

5. No Skip Navigation Link (WCAG 2.4.1)

What it is: Pages must provide a mechanism to skip repeated navigation blocks. Keyboard users must Tab through every menu item on every page load without it.

Real-world example: A site with a 12-item navigation bar and no "Skip to main content" link — a keyboard user must press Tab 12+ times before reaching any page content.

Severity: Medium. Common, easily fixed, and frequently cited.

6. Videos Without Captions (WCAG 1.2.2)

What it is: Pre-recorded video content with audio must have synchronized captions. Auto-generated captions do not always meet the accuracy threshold required.

Real-world example: A product demo video embedded without captions — deaf and hard-of-hearing users receive no audio information.

Severity: Medium-High. Video-heavy sites (SaaS demos, course platforms, marketing pages) are especially exposed.

7. Focus Not Visible (WCAG 2.4.7, 2.4.11 NEW in 2.2)

What it is: As users Tab through a page, the currently focused element must be visually identifiable. Many sites remove the default browser focus ring (outline: none) for aesthetic reasons without providing an alternative — leaving keyboard users unable to see where they are on the page.

WCAG 2.2 strengthened this requirement with Focus Appearance (2.4.11): focus indicators must meet minimum size and contrast thresholds, not just be "visible."

Real-world example: A site that applies *:focus { outline: none; } globally in its CSS — keyboard users see no focus indicator anywhere on the site.

Severity: Critical for keyboard users. Very common, very fixable.

How to Check Your Website for WCAG 2.2 Violations

There are two approaches to accessibility testing: manual and automated.

Manual Testing

• Keyboard-only navigation: Unplug your mouse and navigate your site using Tab, Shift+Tab, Enter, and Arrow keys. Can you reach every interactive element? Can you complete a purchase, sign up, or contact you?
• Screen reader testing: Use NVDA (Windows, free) or VoiceOver (Mac/iOS, built-in). Navigate your site and listen. Is every image described? Every form labeled? Every button named?

Manual testing finds issues that automated tools miss — but it's slow and requires training.

Automated Tools

• axe DevTools (browser extension) — good for catching technical violations in the DOM.
• Google Lighthouse — built into Chrome DevTools, gives an accessibility score and flags specific issues.
• WAVE (WebAIM) — visual overlay that highlights errors on the rendered page.

Critical limitation: Automated tools catch approximately 30-40% of WCAG issues. They cannot reliably assess alt text quality, logical reading order, or the usability of interactive components without human judgment.

The TrueComply Approach

TrueComply scans your site against the full WCAG 2.2 AA criterion set and uses AI to generate code-level fixes — not just a list of errors. You get a full report in 60 seconds, with suggested changes you can copy directly into your codebase.

Scan your site free — join our waitlist!

How to Fix WCAG Violations Without Rewriting Your Whole App

Accessibility remediation does not require starting from scratch. The most practical approach:

1. Prioritize Level A violations first. These represent the most severe barriers. Fix missing alt text, broken keyboard navigation, and unlabeled forms before moving to Level AA items like contrast ratios.

2. Integrate into your dev workflow. Add axe or a similar linter to your CI/CD pipeline so new violations are caught before they ship. Accessibility regressions are far cheaper to fix at commit time than after deployment.

3. Use AI-generated fix suggestions. The shift from "here's a list of your problems" to "here's the code that fixes them" is where TrueComply differentiates. Rather than routing a 40-page audit report to your dev team, you get specific, implementable code changes — image alt attributes, ARIA labels, focus styles — generated from the context of your actual markup.

4. Verify with assistive technology. Automated fixes should always be validated with a screen reader and keyboard test. AI-generated suggestions are a starting point, not a final audit.

If you've received a demand letter and need to understand your immediate exposure and response timeline, see our guide:

I Received an ADA Demand Letter: Your 72-Hour Action Plan.

The Bottom Line

WCAG 2.2 compliance is not a nice-to-have — it's a legal baseline that courts, regulators, and plaintiffs' attorneys treat as the standard of accessibility. The seven violations above are on nearly every site that has never been audited. They are findable in minutes by automated scanning tools, which is exactly how most demand letters start.

The good news: most violations are fixable. Alt text, color contrast, focus styles, and form labels are not architectural overhauls — they're targeted, testable changes that a focused sprint can resolve.

Do not wait for a lawsuit to find out where your site fails.

Join our waitlist!

This post is part of TrueComply's accessibility content series. Related reading: DOJ Title II Deadline April 24, 2026 | accessiBe Alternatives After the FTC Fine | Accessibility Overlays Get You Sued