WCAG 2.2 Compliance: Complete Guide for Small Businesses 2026

Web accessibility is no longer optional. With over 4,500 digital accessibility lawsuits filed in the US in 2025, the European Accessibility Act in full effect, and WCAG 2.2 introducing stricter requirements, small businesses must prioritize WCAG 2.2 compliance or face serious legal and SEO consequences.

This complete pillar guide covers everything you need to know about WCAG 2.2 compliance: what changed from 2.1, the three conformance levels, an actionable checklist, legal risks by jurisdiction, how to audit your site, the best tools, common failures, and mobile accessibility requirements. Whether you are a business owner, developer, or SEO professional, this guide will help you achieve and maintain WCAG 2.2 compliance.

Table of Contents

• What Is WCAG 2.2?
• WCAG 2.2 Levels: A vs AA vs AAA
• WCAG 2.2 Compliance Checklist by Level
• Legal Landscape: WCAG 2.2 and Accessibility Lawsuits
• How to Perform a WCAG 2.2 Audit
• WCAG 2.2 Audit Tools Comparison
• Common WCAG 2.2 Failures (And How to Fix Them)
• Mobile Accessibility Under WCAG 2.2
• FAQ
• Conclusion

What Is WCAG 2.2?

WCAG stands for Web Content Accessibility Guidelines, the internationally recognized standard published by the World Wide Web Consortium (W3C). WCAG 2.2, finalized in October 2023, is the latest version. It defines how to make web content more accessible to people with disabilities, including visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities.

WCAG 2.2 builds directly on WCAG 2.1 and includes all of its criteria. The key difference is the addition of nine new success criteria that address gaps identified since 2.1 was published in 2018. These new criteria focus heavily on improving the experience for users with cognitive and learning disabilities, low vision, and users on mobile devices.

What Changed From WCAG 2.1 to 2.2

• Focus Not Obscured (AA): When a UI component receives keyboard focus, it must not be hidden behind other content. This prevents focus from being lost behind sticky headers, modals, or overlays.
• Dragging Movements (AA): All functionality that requires dragging movement must have an alternative using single-pointer taps or clicks. This helps users who cannot perform precise drag gestures.
• Target Size Minimum (AA): Interactive targets must be at least 24x24 CSS pixels. This replaced the proposed 44x44 requirement from the draft and is critical for mobile usability.
• Consistent Help (A): If a website provides help mechanisms like live chat, contact details, or FAQ links, they must appear in the same location and order across all pages.
• Accessible Authentication (AA): Authentication processes must not rely on cognitive function tests like remembering passwords, solving puzzles, or transcribing text. Alternative methods like magic links or biometrics are acceptable.
• Focus Appearance (AAA): The focus indicator must have a minimum size and contrast. This AAA criterion ensures keyboard focus is always visually unmistakable.

These changes make WCAG 2.2 significantly more stringent than its predecessor. If you already achieved WCAG 2.1 Level AA compliance, you still need to address the new 2.2 criteria to maintain compliance with the latest standard.

WCAG 2.2 Levels: A vs AA vs AAA

WCAG 2.2 organizes its success criteria across three conformance levels. Understanding the difference is critical for planning your compliance strategy, budgeting, and timelines.

Level A: Minimum Compliance

Level A is the minimum baseline. It covers the most critical accessibility barriers that would otherwise make it impossible or very difficult for users with disabilities to access content. Examples include missing alt text on images, no keyboard support, and missing form labels. Level A criteria are mandatory stepping stones for higher compliance. Most websites must meet all Level A criteria as a starting point.

Examples of Level A criteria: non-text content must have text alternatives, captions must be provided for prerecorded video, information must not rely solely on sensory characteristics, and all functionality must be operable through a keyboard interface.

Level AA: The Legal Standard

Level AA includes all Level A and AA criteria. This is the standard referenced by virtually every accessibility law worldwide, including the ADA, Section 508, the European Accessibility Act, and most state laws. For small businesses, Level AA is the practical target. It covers the most impactful barriers: color contrast ratios of at least 4.5:1, consistent navigation, descriptive headings and labels, and resizable text up to 200%.

Under WCAG 2.2, Level AA also includes the new criteria: target size minimum (24x24px), dragging movement alternatives, focus not obscured, consistent help, and accessible authentication. Meeting Level AA is sufficient for legal compliance in almost all jurisdictions.

Level AAA: Highest Standard

Level AAA is the highest level of WCAG compliance. It includes all Level A, AA, and AAA criteria. Meeting Level AAA is significantly more difficult and may not be achievable for all types of content. Examples of AAA-only requirements include sign language interpretation for videos, extended audio descriptions, and contrast ratios of at least 7:1. The W3C recommends Level AAA as a long-term goal but acknowledges it is not required for most legal compliance.

WCAG 2.2 Compliance Checklist by Level

Use this actionable checklist to audit your website against WCAG 2.2 requirements. Each item includes the conformance level and a brief description of what to check.

Level A Checklist

• All non-text content has text alternatives (alt text on images, transcripts for audio)
• Captions are provided for prerecorded video content
• Information is not conveyed by color alone
• Audio does not autoplay or can be stopped within 3 seconds
• All functionality is available from a keyboard interface
• Keyboard focus does not get trapped in any component
• Users can pause, stop, or hide moving, blinking, or auto-updating content
• No content flashes more than three times per second
• Skip navigation links are provided to bypass repeated content
• Page titles are descriptive and unique
• Link purpose can be determined from the link text alone
• Page language is specified in the HTML lang attribute
• Form inputs have associated labels
• Error messages are provided when input errors are detected
• ARIA attributes are used correctly and follow spec
• Consistent help mechanisms appear in the same location across pages (WCAG 2.2 new)

Level AA Checklist

• Live video has captions
• Audio descriptions are provided for prerecorded video
• Color contrast ratio is at least 4.5:1 for normal text and 3:1 for large text
• Text can be resized up to 200% without loss of content or functionality
• Images of text are not used (use real text with CSS instead)
• Navigation is consistent across all pages
• Headings and labels describe topic or purpose
• Focus order preserves logical meaning and operability
• Link purpose can be determined from link text plus context
• Multiple ways are available to find pages (search, sitemap, navigation)
• Input assistance includes suggestions for fixing errors
• Language changes in content are indicated with lang attributes
• Interactive targets are at least 24x24 CSS pixels (WCAG 2.2 new)
• Dragging movements have a single-pointer alternative (WCAG 2.2 new)
• Focus is not fully obscured when a component receives focus (WCAG 2.2 new)
• Authentication does not rely on cognitive function tests (WCAG 2.2 new)

Level AAA Checklist

• Sign language interpretation is provided for prerecorded video
• Extended audio descriptions are provided for video content
• Color contrast ratio is at least 7:1 for normal text
• No background audio or audio can be turned off
• Content does not require horizontal scrolling at 320px viewport width
• Pre-recorded video content has sign language interpretation
• Images of text are not used in any circumstances
• Section headings organize content
• Context-sensitive help is available
• Focus indicator has minimum area and contrast (WCAG 2.2 new)

Legal Landscape: WCAG 2.2 and Accessibility Lawsuits

The legal landscape for web accessibility has shifted dramatically. In 2025, over 4,500 digital accessibility lawsuits were filed in the United States alone, and the European Accessibility Act now mandates compliance across the EU. Small businesses are increasingly targeted because they are less likely to have compliant websites.

United States Federal Law

The Americans with Disabilities Act (ADA) Title III prohibits discrimination on the basis of disability in places of public accommodation. Courts have increasingly interpreted that websites are covered under the ADA. While the DOJ has not issued explicit web accessibility regulations, the trend is clear: courts routinely rule that inaccessible websites violate the ADA. There is no federal safe harbor for small businesses.

State Law Risks

Individual states are becoming more aggressive. California AB 1757 formally references WCAG 2.1 Level AA for state agency websites. New York, Florida, and Texas see high volumes of federal ADA lawsuits. California also has the Unruh Civil Rights Act, which allows plaintiffs to seek $4,000 in damages per violation. Every state with an accessibility law effectively follows WCAG as the standard.

European Accessibility Act (EAA)

The European Accessibility Act (Directive 2019/882) requires products and services, including websites and mobile apps, to meet WCAG 2.1 Level AA (with 2.2 adoption expected). From June 2025, all new public sector websites must comply; from June 2030, all private sector websites must comply. Non-compliance can result in fines, injunctions, and mandatory remediation.

Other Jurisdictions

The UK Equality Act 2010 and Public Sector Bodies Accessibility Regulations require WCAG 2.2 compliance for public sector and increasingly for private sector. Canada's Accessible Canada Act (ACA) and provincial laws in Ontario (AODA) and Quebec reference WCAG 2.0 AA, with updated regulations expected. Australia's Disability Discrimination Act (DDA) has led to high-profile cases, and the Australian Human Rights Commission recommends WCAG 2.2 compliance. Japan, Israel, and South Korea all have accessibility standards aligned with WCAG.

How to Perform a WCAG 2.2 Audit

A proper WCAG 2.2 compliance audit combines automated scanning with manual testing. Automated tools catch roughly 30% of issues, while manual testing reveals the remaining 70% that require human judgment. Here is a step-by-step process that balances thoroughness with efficiency.

Step 1: Automated Scan

Run an automated accessibility scanner across your entire website. Tools like Scanly, axe DevTools, WAVE, and Lighthouse can identify technical issues like missing alt text, low color contrast, missing form labels, and broken ARIA attributes in minutes. Run this scan on every page template type (homepage, product page, blog post, checkout).

Step 2: Manual Keyboard Testing

Navigate every page using only the keyboard (Tab, Shift+Tab, Enter, Escape, arrow keys). Verify all interactive elements are reachable, focus indicators are visible, no focus traps exist, and the tab order follows the logical reading order. This test catches issues automated tools often miss.

Step 3: Screen Reader Testing

Test your site with a screen reader. Use VoiceOver on macOS or NVDA on Windows. Listen to how your content is announced. Check that headings, links, forms, images, and dynamic content updates are properly communicated. Ensure that ARIA attributes are correctly implemented and that custom components follow WAI-ARIA patterns.

Step 4: Visual and Zoom Testing

Test with browser zoom at 200% to ensure content does not overlap or get cut off. Verify color contrast ratios using a contrast checker (minimum 4.5:1 for normal text, 3:1 for large text). Test high contrast mode and dark mode if supported. Check that content is readable and functional at all zoom levels.

Step 5: Mobile and Touch Testing

Test on actual mobile devices or emulators. Verify touch targets meet the 24x24px minimum. Check that draggable interfaces have single-tap alternatives. Test with mobile screen readers (TalkBack on Android, VoiceOver on iOS). Ensure responsive layouts do not break at any viewport width.

Step 6: Document and Prioritize

Document every issue with the page URL, a description, the WCAG criterion it violates (e.g., 1.1.1 Non-text Content), the impact severity, and a recommended fix. Prioritize by impact: Level A issues first, followed by Level AA, then AAA. Focus on high-traffic pages and critical user flows (login, checkout, contact forms) first.

For a more detailed process, read our complete SEO audit checklist which covers how to integrate accessibility testing into your broader website maintenance routine.

WCAG 2.2 Audit Tools Comparison

Choosing the right accessibility audit tool depends on your budget, technical expertise, and scope of work. The table below compares four popular solutions across key features relevant to WCAG 2.2 compliance.

No single tool covers every aspect of WCAG 2.2 compliance. For comprehensive coverage, pair an automated scanner with manual testing. Scanly offers the broadest coverage of WCAG levels combined with SEO, performance, and security auditing in one platform, making it ideal for small businesses that want a complete picture.

Common WCAG 2.2 Failures (And How to Fix Them)

Based on WebAIM million site analysis and our own audit data, these are the most common WCAG 2.2 failures we see on small business websites. Each comes with a practical fix you can implement today.

1. Insufficient Color Contrast

The problem: Text on background lacks sufficient contrast, making it difficult or impossible to read for users with low vision. This is the single most common accessibility failure, affecting over 86% of homepages.

The fix: Use a color contrast checker to verify ratios. Normal text requires 4.5:1 minimum (Level AA). Large text (18px+ bold or 24px+ regular) requires 3:1. Choose darker text colors or lighter backgrounds until ratios pass. Avoid light gray text on white backgrounds.

2. Missing or Poor Alt Text

The problem: Images missing alt text or using non-descriptive alt text like "image.jpg" or "photo1." Screen readers cannot convey the image content, leaving users with visual impairments without context.

The fix: Every informative image needs descriptive alt text that conveys the image content and function. Decorative images should use empty alt text (alt="") to be ignored by screen readers. Be specific but concise: instead of "image of a dog," use "Golden retriever playing fetch in a park."

3. Touch Targets Smaller Than 24x24px

The problem: Buttons, links, and interactive elements are too small to tap accurately on mobile devices, particularly for users with motor disabilities. This is a new WCAG 2.2 Level AA criterion.

The fix: Ensure all interactive targets are at least 24x24 CSS pixels. Increase padding on small buttons and links. If a target cannot be made 24x24px due to design constraints, ensure it has sufficient adjacent spacing (at least 24px from other targets that meet the minimum size).

4. No Dragging Movement Alternatives

The problem: Interfaces that require dragging (sliders, sortable lists, kanban boards, range sliders) are unusable for users who cannot perform precise drag gestures. This is a new WCAG 2.2 Level AA criterion.

The fix: Provide single-pointer alternatives for any dragging interaction. For range sliders, add increment and decrement buttons. For sortable lists, add move up and move down buttons. For maps, provide pan buttons instead of requiring drag-to-pan.

5. Focus Not Obscured

The problem: When keyboard focus lands on an element, it is hidden behind a sticky header, cookie banner, or other overlay. Users cannot see where their keyboard focus is.

The fix: Add offset to scrollIntoView for focused elements or ensure sticky headers allow enough clearance. Use CSS scroll-margin-top on focusable elements. Test keyboard navigation with sticky headers enabled to verify focus visibility.

6. Documents Without Structure

The problem: PDFs, Word documents, and other downloadable files lack headings, tags, and proper reading order. These documents cannot be navigated by screen reader users.

The fix: Run an accessibility check on all documents before publishing. In Adobe Acrobat, use the Accessibility Checker and Auto-Tag Document features. For web content, always use semantic HTML instead of PDFs when possible. Add a brief accessibility statement to documents that explains how to request accessible versions.

For a broader approach to website health, also review our website security audit checklist and Core Web Vitals guide — accessibility, security, and performance are interconnected pillars of a well-maintained website.

Mobile Accessibility Under WCAG 2.2

WCAG 2.2 places significant emphasis on mobile accessibility. With over 60% of web traffic coming from mobile devices, the new success criteria directly address the most common mobile usability barriers. Mobile accessibility is not a separate standard — WCAG 2.2 criteria apply to all platforms, but several criteria specifically benefit mobile users.

Touch Target Sizing (2.5.8 Target Size Minimum)

The most impactful mobile addition is the 24x24 CSS pixel minimum target size. This applies to all interactive elements: buttons, links, form controls, and custom interactive components. Small nav links, close buttons, and social share icons are common offenders. Google also considers this a mobile usability signal, so fixing it benefits both accessibility and SEO.

Pointer Gestures (2.5.1 Pointer Gestures)

All functionality that uses multipoint or path-based gestures (pinch zoom, swipe, drag) must be operable with a single pointer without a path-based gesture. For example, a photo gallery that requires swiping must also offer arrow buttons. A map that pinch-zooms must also have zoom in and zoom out buttons.

Dragging Alternatives (2.5.7 Dragging Movements)

This new WCAG 2.2 criterion affects mobile interfaces heavily. Any dragging interaction must have a single-tap alternative. For example, a color picker that uses drag to select a shade must also allow direct input or tap-to-select. A reorganization UI that drags cards must also provide move controls.

Motion Actuation (2.5.4 Motion Actuation)

Functionality triggered by device motion (shake to undo, tilt to scroll) must also be operable via standard UI controls. This ensures that users who cannot physically shake their device can still access all features. Provide visible buttons as alternatives.

Responsive Zoom and Layout

Content must be usable at 200% zoom without loss of content or horizontal scrolling. On mobile, this means text reflows properly, buttons do not overlap, and form fields remain usable. Avoid fixed-width containers and ensure your layout uses responsive units (rem, %, vw) rather than fixed pixels.

Mobile accessibility testing should be part of every WCAG 2.2 audit. Use real mobile devices or emulators, test with mobile screen readers, and verify touch interactions manually. Run an automated audit first to identify the most common mobile WCAG issues automatically.

FAQ: WCAG 2.2 Compliance

Conclusion: Start Your WCAG 2.2 Compliance Journey Today

WCAG 2.2 compliance is not just about avoiding lawsuits — it is about building a better website for everyone. Accessible websites rank higher in search, convert better, reach a wider audience, and demonstrate your commitment to inclusion. With over 1.3 billion people worldwide living with disabilities, the business case is as strong as the moral and legal case.

The path to compliance is straightforward: understand the requirements, run an audit, fix issues by priority, and maintain compliance over time. The hardest part is getting started. Our recommendation is to begin with an automated scan to understand your current baseline, then work through the Level A checklist, followed by Level AA. Most small businesses can achieve WCAG 2.2 Level AA compliance within 4-8 weeks with focused effort.

For further reading, explore our related guides: SEO Audit Checklist, Website Security Audit Checklist, and Core Web Vitals Explained.