AI
Summarize this blog post with:
Web Accessibility · ADA · WCAG 2.2 · Legal Compliance
ADA Website Compliance Guide: WCAG 2.2 Requirements for Businesses
More than 5,000 digital accessibility lawsuits were filed in the U.S. in the latest full-year count, and 94.8% of home pages still have detectable WCAG failures. Ecommerce sites are named in roughly 7 in 10 cases. Here is what compliance actually requires and how to get there.
⚠️ Lawsuits named companies running accessibility overlay widgets more than 1,400 times in the latest full-year count. Overlays are not compliance.
5,000+
Digital accessibility lawsuits filed (UsableNet)
27%
Rise in federal website lawsuit filings year over year
94.8%
Home pages with detectable WCAG 2 failures
69%
Of lawsuits target ecommerce sites
What ADA Website Compliance Actually Means
The Americans with Disabilities Act (ADA) was enacted in 1990, before the commercial internet existed, and its original text focuses on physical access. Courts have increasingly applied it to websites as places of public accommodation, although circuits differ on whether a site needs a connection to a physical location. The DOJ also states that Title III covers web content (see ADA.gov web guidance).
Title III, which covers private businesses, has no federal rule that names a technical standard. In practice, settlements, demand letters and DOJ guidance point to WCAG 2.1 Level AA as the benchmark. A remediation project started now should target WCAG 2.2 Level AA: it is backward compatible with 2.1 AA, the level referenced by EU rules under the European Accessibility Act, and it is the version UK government guidance now asks public-sector sites to meet.
The DOJ’s 2024 rule under Title II (state and local governments) adopted WCAG 2.1 AA, and the DOJ has since pushed the compliance deadlines out by about a year, with larger governments due first and smaller ones a year later. The rule does not apply to private businesses, but it gives courts and plaintiffs a documented federal reference point for WCAG 2.1 AA.
⚠️ The Overlay Myth: Widgets Do Not Deliver Compliance
The FTC ordered accessiBe to pay $1 million over claims that its overlay could make any website WCAG compliant (TechCrunch report). Lawsuits also named companies using accessibility widgets more than 1,400 times in the latest full-year count. Overlays inject JavaScript at runtime, so they cannot reliably fix missing semantic HTML, keyboard failures or unlabeled forms in the source code. They have not protected sites from lawsuits. The dependable path is code-level remediation of the website itself.
WCAG 2.1 and 2.2: The Four Core Principles (POUR)
WCAG is organized around four accessibility principles. Every WCAG success criterion maps to one of these four areas. Understanding the framework helps prioritize remediation work by category.
👁 Perceivable
Content must be available to all users through multiple means. Text alternatives for non-text content (alt text), captions for video, sufficient color contrast, and content that doesn’t rely on color alone to convey meaning.
⌁️ Operable
Users must be able to navigate and operate the website using a keyboard or assistive device. No keyboard traps, skip navigation links, sufficient time to complete tasks, and no content that causes seizures (no content that flashes more than three times per second).
📖 Understandable
Content and interface must be readable and predictable. Language of the page declared in HTML, consistent navigation, error identification in forms, and labels and instructions for all user input.
🔧 Robust
Content must be compatible with current and future assistive technologies. Valid, semantic HTML, proper ARIA landmark roles and labels, and name/role/value for all user interface components.
The Legal Landscape: Why Lawsuits Are Accelerating
Web accessibility litigation has grown for several years. Two forces are behind the recent acceleration: AI-powered scanning tools that find WCAG violations at scale and make demand letters cheap to produce, and a small group of plaintiff firms that file large volumes of ADA web cases.
The numbers: UsableNet counted more than 5,000 digital accessibility lawsuits across federal and key state courts in the latest full-year count, and Seyfarth Shaw tracked 3,117 website accessibility filings in federal court alone, up 27% year over year. Ecommerce accounts for roughly 69% of cases.
Who gets sued: No business is too small to receive a demand letter. Local retailers, restaurants and healthcare providers all appear in filings. The common pattern: a plaintiff firm or scanning service finds a WCAG violation, sends a demand letter, and the case settles. Commonly reported settlements run about $5,000 to $25,000 in attorney fees plus a remediation agreement, and defense costs can reach $15,000 to $50,000 or more even for a business that wins. Treat these as rough industry ranges, not guarantees.
✅ Business Case Beyond Legal Risk
An accessible website serves a large customer group: the WHO estimates that about 1.3 billion people, roughly 1 in 6 worldwide, live with a significant disability. Accessibility work also overlaps with SEO and performance: semantic HTML, descriptive alt text, logical heading hierarchies and clear link text help both assistive technology and search engines. It does not guarantee rankings, but the practices reinforce each other.
WCAG 2.2 vs 2.1: What Changed
WCAG 2.2 was published by the W3C in October 2023 and adds nine new success criteria on top of WCAG 2.1 (what is new in WCAG 2.2). The most impactful additions for most websites are:
Focus Not Obscured, Minimum (2.4.11, AA): When a component receives keyboard focus, it must not be entirely hidden by author-created content such as sticky headers, cookie banners or chat widgets. This matters for keyboard users who need to see where focus sits. A separate Focus Appearance criterion (2.4.13) exists, but only at the AAA level.
Dragging Movements (2.5.7, AA): Any functionality that uses a dragging motion must also be operable by single pointer (click or tap). Drag-and-drop interfaces without alternatives fail this criterion.
Target Size Minimum (2.5.8, AA): Interactive targets (buttons, links, form controls) must be at least 24×24 CSS pixels, particularly important for mobile interfaces where small touch targets are common.
Redundant Entry (3.3.7, A): Information that a user has already entered in a multi-step process should not need to be re-entered (unless security requires it).
Accessible Authentication (3.3.8, AA): Authentication processes (login) cannot require cognitive tests (like CAPTCHA puzzles that require interpreting distorted text) unless alternatives are provided.
WCAG 2.1 Level AA remains the current litigation benchmark, but building to WCAG 2.2 AA is the recommended target, it is backward compatible with 2.1 and positions the site for the direction regulators and courts are moving.
Most Common WCAG Violations That Trigger ADA Lawsuits
WebAIM Million analysis of home pages found 94.8% with detectable WCAG 2 failures, averaging 51 errors per page. The most frequent were low contrast text (79.1% of pages), missing image alt text (55.5%) and missing form labels (48.2%). These issues are among those most often cited in ADA demand letters and court filings.
| Violation | WCAG Criterion | Risk Level | What It Means |
|---|---|---|---|
| Missing image alt text | 1.1.1 Non-text Content | High | Images without descriptive alt attributes are invisible to screen readers. Decorative images need alt=”” to be skipped correctly. |
| Low color contrast | 1.4.3 Contrast (Minimum) | High | Normal text needs 4.5:1 contrast ratio against background. Large text (18pt+) needs 3:1. Fails frequently on grey text on white or light-colored CTA buttons. |
| Missing form labels | 1.3.1 Info and Relationships | High | Form fields without associated <label> elements are unusable with screen readers. Placeholder text is not a label substitute. |
| Keyboard navigation failures | 2.1.1 Keyboard | High | Interactive elements (menus, modals, carousels, tabs) that cannot be reached or operated without a mouse. Keyboard traps (cannot escape a modal with Escape key). |
| Missing video captions | 1.2.2 Captions (Prerecorded) | High | Video content without synchronized captions excludes deaf and hard-of-hearing users. Auto-generated captions alone do not meet this criterion without review and correction. |
| No skip navigation link | 2.4.1 Bypass Blocks | Medium | Sites with repetitive navigation (header nav, sidebar) must provide a “Skip to main content” link so keyboard users can bypass repeated content on every page. |
| Inaccessible PDFs | 1.3.1, 1.1.1 | Medium | PDFs without proper tag structure, reading order, and alt text for images are inaccessible to screen readers. Common in menus, brochures, reports, and forms linked from websites. |
| Missing page title | 2.4.2 Page Titled | Medium | Each page must have a descriptive <title> that identifies its purpose. Duplicate or generic titles (“Home”, “Page 1”) fail this criterion. |
| ARIA misuse | 4.1.2 Name, Role, Value | Medium | Incorrect ARIA roles, missing aria-labels on icon buttons, or aria-hidden applied to visible interactive content creates confusion for assistive technology users. |
| Poor focus visibility | 2.4.7 Focus Visible, 2.4.11 Focus Not Obscured | Medium | CSS that removes browser focus outlines (outline: none) without providing an alternative focus indicator fails keyboard users who rely on visible focus to navigate. |
ADA/WCAG Compliance Audit Checklist
A practical starting checklist for reviewing your site’s accessibility. This covers the highest-risk violation categories. A full WCAG 2.2 AA audit covers 50+ success criteria, this checklist covers the issues that appear in the majority of ADA lawsuits.
Images & Non-Text Content
Meaningful images have alt textEvery image that conveys information has a descriptive alt attribute that communicates the same content.
Decorative images use alt=””Images that are purely decorative have an empty alt attribute so screen readers skip them.
Complex images have long descriptionsCharts, infographics, and diagrams have extended descriptions (via aria-describedby or adjacent text).
Icon buttons have accessible namesButtons that contain only an icon (magnifying glass, hamburger menu) have an aria-label or visually hidden text.
Color Contrast
Body text meets 4.5:1 ratioAll normal-size text (under 18pt regular or 14pt bold) has at least 4.5:1 contrast against its background color.
Large text meets 3:1 ratioText 18pt and above (or 14pt bold and above) meets the 3:1 minimum contrast ratio.
UI components meet 3:1 ratioForm borders, button outlines, focus indicators, and active interface components meet 3:1 contrast against adjacent colors.
Color is not the only signalInformation conveyed with color (error states, required fields) is also communicated by text, icon, or pattern.
Forms & Interactive Elements
All form fields have visible labelsEvery input, select, and textarea has a <label> element programmatically associated via for/id or aria-labelledby.
Error messages identify the fieldValidation errors identify which field has an error and describe what is required to fix it, not just “Error” or a red border.
Required fields are marked clearlyRequired fields are marked with both a visual indicator and an aria-required=”true” attribute.
Form can be completed by keyboardEvery form field and submit button is reachable and operable via Tab key without a mouse.
Keyboard Navigation
All interactive elements are keyboard-reachableMenus, dropdowns, modals, carousels, tabs, accordions, and custom components can be reached and operated using only Tab, Enter, Escape, and arrow keys.
No keyboard trapsKeyboard focus can always be moved away from any component using standard keys, no modals or widgets that trap keyboard focus without an Escape key exit.
Skip navigation link is presentA “Skip to main content” link is the first focusable element on every page, allowing keyboard users to bypass repeated header navigation.
Focus order is logicalTab order follows a visually logical reading sequence, top to bottom, left to right, not a random DOM order disconnected from visual layout.
Video & Audio Content
Prerecorded video has captionsAll prerecorded video with dialogue or important audio has synchronized closed captions. Auto-generated captions reviewed and corrected for accuracy.
Audio-only content has a transcriptPodcasts and audio recordings have a full text transcript available adjacent to or linked from the content.
Video has audio descriptionsPrerecorded video where visual content conveys information not available in the audio track has audio description or a text alternative.
Autoplay is not used (or can be stopped)No audio or video autoplays for more than 3 seconds without a mechanism to pause, stop, or mute it.
Page Structure & Semantics
Page has a unique, descriptive titleThe <title> element describes the page’s purpose specifically, not generic (“Home”) or duplicated across pages.
HTML lang attribute is setThe <html> element has a lang attribute specifying the page’s primary language (lang=”en” for English).
Heading hierarchy is logicalHeadings (h1 through h6) are used to reflect document structure, not for visual styling. One h1 per page; no skipped heading levels.
Landmark regions are presentPage uses semantic HTML landmarks: <header>, <nav>, <main>, <footer>, or equivalent ARIA landmark roles, so screen reader users can navigate by region.
Recommended Audit Process
A defensible accessibility audit combines automated testing, which catches only part of the WCAG issues (commonly estimated at roughly a third to just over half, depending on the study), with manual keyboard testing, screen reader testing and expert review. No automated tool alone can confirm WCAG compliance.
Step 1, Automated scan: Run WAVE (wave.webaim.org), axe DevTools, or Deque’s browser extension across key page templates (homepage, product pages, checkout, contact forms, blog posts). Automated tools catch color contrast failures, missing alt text, missing labels, and structural issues quickly.
Step 2, Keyboard navigation test: Navigate the entire site using only Tab, Shift+Tab, Enter, Escape, and arrow keys. Identify anything that cannot be reached or operated. Test every modal, dropdown, carousel, and form.
Step 3, Screen reader test: Test with NVDA + Chrome (Windows, free) and VoiceOver + Safari (macOS/iOS, built-in). Navigate the homepage, a product page, and the checkout/contact form with screen readers. Listen for what gets announced and what is missed.
Step 4, Expert review: A trained accessibility specialist reviews the automated and manual findings, identifies issues that require human judgment (logical reading order, cognitive clarity, ARIA implementation correctness), and produces a prioritized remediation report.
Step 5, Remediate at code level: Fix identified issues in the website’s source code. Overlays are not remediation. Changes to HTML, CSS, and JavaScript that address root causes are. Priority order: keyboard traps first (most severe), missing form labels, missing alt text, color contrast failures, video captions.
Step 6, Retest and document: After remediation, re-run automated scans and manual tests. Document the testing process, tools used, issues found, and fixes applied. Documented testing can show good-faith accessibility effort if a demand letter arrives.
Related Services and Guides
Our UI/UX design service covers accessibility audits and WCAG 2.2 AA remediation. We also build and fix accessible sites on WordPress, Shopify and WooCommerce, and our ecommerce development service helps stores close accessibility gaps in product pages and checkout. Comparing providers? See the top UI/UX design companies in the USA.
Frequently Asked Questions
What business owners and web teams need to know about accessibility compliance.
What WCAG level is required for ADA compliance?
No federal rule names a technical standard for private businesses under ADA Title III. In practice, demand letters, settlements and DOJ guidance point to WCAG 2.1 Level AA as the benchmark, and the DOJ adopted WCAG 2.1 AA for state and local governments under Title II. Building to WCAG 2.2 Level AA is the safer target: it is backward compatible with 2.1 and covers the newer criteria regulators are moving toward.
Do accessibility overlays and widgets make a website ADA compliant?
No. The FTC ordered accessiBe to pay $1 million over claims that its overlay could make any website WCAG compliant, and lawsuits named companies running accessibility widgets more than 1,400 times in the latest full-year count. Overlays inject JavaScript at runtime, so they cannot reliably fix missing semantic HTML, keyboard failures or unlabeled forms in the source code. The dependable path is code-level remediation.
Who is at legal risk from ADA website accessibility lawsuits?
Any business with a public-facing website can receive a demand letter, and size is no protection. Ecommerce stores account for roughly 69% of cases, followed by food service and healthcare. Businesses that have been sued once are often sued again, and serial plaintiffs file large volumes of cases, so a documented audit and remediation plan matters.
What are the most common WCAG violations that trigger ADA lawsuits?
The most frequent failures found by the WebAIM Million analysis are low contrast text (79.1% of home pages), missing image alt text (55.5%), missing form input labels (48.2%) and empty links (45.4%). Keyboard navigation failures, missing video captions, missing skip links and ARIA misuse also come up often in demand letters.
How much do ADA website accessibility lawsuits cost?
Commonly reported settlements run about $5,000 to $25,000 in attorney fees plus a remediation agreement, and defense costs can reach $15,000 to $50,000 or more even if the business wins. These are rough industry ranges, not guarantees. Fixing the site before a demand letter arrives is almost always cheaper.
How do I choose the best ADA website accessibility audit company in the USA?
Look for a team that combines automated scans with manual keyboard and screen reader testing, fixes issues in the source code instead of selling an overlay, delivers a prioritized remediation report, and retests afterward. Ask for a sample audit report and for experience with your platform. You can start with our UI/UX design service, which includes accessibility audits and WCAG 2.2 AA remediation, or compare the top UI/UX design companies in the USA.
Does the ADA apply to my website if I have no physical location?
Courts are not fully aligned. Some circuits have required a connection between the website and a physical place of business, while others have applied the ADA to online-only businesses. Because plaintiffs file in many jurisdictions, treating accessibility as a requirement everywhere is the lower-risk approach. Talk to a qualified attorney about your specific exposure.
How long does it take to make a website WCAG 2.2 AA compliant?
It depends on site size and how many issues the audit finds. A small brochure site can often be fixed in a few weeks, while a large ecommerce store or web app with custom components can take several months. Start with an audit of your key templates (homepage, product page, checkout, forms), fix keyboard, form label, alt text and contrast issues first, then retest.
Does website accessibility help SEO?
Often, yes, because the practices overlap: descriptive alt text, logical heading structure, clear link text, captions and transcripts, and fast, stable pages help both assistive technology and search engines. It is not a ranking guarantee, but accessibility work and good technical SEO tend to reinforce each other.
Need an ADA/WCAG Accessibility Audit or Remediation for Your Website?
A2Z Dev Center provides website accessibility audits, WCAG 2.2 AA remediation, and ongoing compliance support through our UI/UX design services for business websites, ecommerce stores, and web applications. We fix accessibility at the code level, not with an overlay widget. At $40 to $80 per hour for accessibility audits and remediation on WordPress, Shopify, WooCommerce, and custom web platforms.
Get Free Accessibility Assessment →
Schedule a call
Talk to a subject-matter expert
Web development, SEO, or digital marketing — tell us about your project and we'll get back within one business day. No obligation.
- Free scope & strategy session
- A senior specialist, not a sales rep
- Your details stay confidential
