ADA Website Compliance 2026: Deadlines, Requirements, and How to Audit

April 24, 2026 is the first hard ADA website compliance deadline for state and local governments serving populations over 50,000. Private businesses have operated under litigation risk since 1996 — and that risk is not getting smaller. This guide explains what WCAG 2.2 AA compliance actually requires, who is affected by which rules, and how to run a structured accessibility audit.

What Is ADA Website Compliance?

The Americans with Disabilities Act (ADA) of 1990 prohibits discrimination against people with disabilities in public accommodations. Courts have consistently ruled — and the Department of Justice formally confirmed in 2022 — that websites and mobile apps are "places of public accommodation" covered by ADA Title III (private businesses) and Title II (government entities).

ADA website compliance means ensuring your digital properties are accessible to people with visual, auditory, motor, and cognitive disabilities. The practical standard for compliance is WCAG 2.1 Level AA — the Web Content Accessibility Guidelines published by the W3C — though the DOJ's 2024 final rule for government entities references WCAG 2.1 and does not yet mandate WCAG 2.2.

The Web Accessibility Checker tool can scan any URL against WCAG 2.2 AA criteria and identify failures automatically — covering approximately 30–40% of detectable issues. The remaining issues require manual testing with assistive technologies.

2026 Compliance Deadlines: Who Must Act Now

The DOJ's April 2024 final rule under Title II created the first explicit federal deadlines for ADA website accessibility:

Entity Type	Population Served	Compliance Deadline
State and local governments	50,000 or more	April 24, 2026
State and local governments	Under 50,000	April 26, 2027
Private businesses (Title III)	N/A — all covered entities	No fixed deadline; litigation risk ongoing

Government entities with fewer than 10,000 people served have an additional year beyond the smaller-jurisdiction deadline. Special districts and special purpose entities have until April 26, 2027 regardless of size.

Private businesses — hotels, restaurants, retail, healthcare, financial services, and effectively all commercial websites — have no specific federal deadline but face active litigation. ADA Title III web accessibility lawsuits exceeded 4,000 per year in recent years, and serial filers have established precedents in courts across multiple circuits.

WCAG 2.2 AA: What Compliance Actually Requires

WCAG 2.2 is the current W3C standard, published September 2023. It builds on WCAG 2.1 with nine new success criteria. While the DOJ rule for government entities references WCAG 2.1, proactive organizations should audit against WCAG 2.2 since it is the current published standard and backward-compatible.

WCAG 2.2 AA compliance requires meeting 50 success criteria across four principles — Perceivable, Operable, Understandable, and Robust. The most commonly failed criteria on real websites:

• 1.4.3 Contrast (Minimum) — text must have 4.5:1 contrast ratio against its background (3:1 for large text). Fails on roughly 80% of audited sites.
• 2.4.7 Focus Visible — keyboard focus must be visually apparent when navigating with Tab. Commonly removed by CSS resets.
• 1.1.1 Non-text Content — images need descriptive alt text; decorative images need empty alt attributes.
• 3.1.1 Language of Page — HTML lang attribute must be set correctly.
• 2.4.11 Focus Appearance (new in 2.2) — focus indicator must be at least 2px thick and meet minimum contrast. Stricter than 2.1.
• 2.5.8 Target Size (Minimum) (new in 2.2) — interactive targets must be at least 24x24 CSS pixels or have adequate spacing.

The WCAG 2.2 checklist for 2026 covers all 50 criteria with implementation guidance. The WCAG 2.2 vs 2.1 differences guide details what changed and what stayed the same.

How to Run an ADA Compliance Audit: Step by Step

A structured ADA accessibility audit covers three layers: automated scanning, keyboard navigation testing, and assistive technology testing. Each layer catches different failure types.

Step 1: Automated Scanning

Run your site through an automated checker. The Web Accessibility Checker scans against WCAG 2.2 AA and reports failures by criterion with remediation guidance. Run it against your highest-traffic pages, your forms, and your checkout or conversion flow — not just your homepage. Automated scanning catches:

• Missing alt text on images
• Contrast failures in text and UI components
• Missing form labels
• Missing page language declaration
• Invalid ARIA usage

Step 2: Keyboard Navigation Testing

Disconnect your mouse and navigate your site using only Tab, Shift+Tab, Enter, and arrow keys. Verify that: (a) every interactive element is reachable by keyboard, (b) focus is visually visible on every focused element, (c) focus order is logical, and (d) modal dialogs trap focus appropriately and can be closed without a mouse. This manual step catches failures that automated tools miss — typically 40–50% of real-world issues.

Step 3: Screen Reader Testing

Test with NVDA on Windows (free) or VoiceOver on Mac (built-in) using Chrome and Firefox respectively. Navigate through your page headings, forms, and interactive elements. Verify that: image alt text is meaningful, form fields announce their labels, error messages are announced on validation failure, and dynamic content updates are announced. See the complete guide to checking website accessibility for screen reader testing scripts.

Step 4: Document and Prioritize Failures

Categorize findings by WCAG criterion, frequency (how many instances), and impact (does this block task completion entirely?). Failures that prevent task completion for disabled users — form fields without labels, keyboard traps, missing error messages — are critical. Visual issues like contrast are important but less immediately blocking. Prioritize critical issues first.

Common ADA Compliance Failures and How to Fix Them

The most prevalent failures, with remediation approaches:

Color Contrast Failures

Fix: Use a color contrast checker to verify 4.5:1 for normal text. For CSS, increase font color darkness or background lightness until the ratio is met. The color contrast guide explains ratio calculation and testing tools.

Missing Alt Text

Fix: Add descriptive alt attributes to all meaningful images (alt="Graph showing 40% increase in conversion rate"). Add empty alt attributes to decorative images (alt=""). Never use filenames or "image" as alt text.

Missing Form Labels

Fix: Associate every form input with a visible label element using the for attribute matching the input's id. Where visible labels are not possible, use aria-label or aria-labelledby.

Inaccessible PDFs

Fix: PDFs are their own accessibility domain. At minimum, run Adobe Acrobat Pro's accessibility checker and add document structure (headings, reading order, alt text for images). For high-stakes documents, consider providing an HTML alternative.

Missing Focus Indicators

Fix: Remove any CSS that sets outline: none on :focus states. Add a visible focus style using CSS :focus-visible that meets WCAG 2.2's new stricter requirements: minimum 2px border, minimum 3:1 contrast against adjacent colors. See the full accessibility audit guide for implementation examples.

ADA Compliance for Private Businesses: The Litigation Landscape

Private businesses operating under Title III do not face the April 2026 government deadline, but the litigation environment has been active since the mid-2010s. Several patterns characterize ADA web accessibility litigation against private companies:

• Serial filers: A small number of law firms and plaintiffs file hundreds of cases per year against businesses with accessible failures. Retail, hospitality, healthcare, and financial services are most targeted.
• Demand letters before lawsuits: Many cases begin with a demand letter requiring remediation within 30–60 days. Responding proactively with a remediation timeline typically resolves these without litigation.
• No minimum company size: Small businesses with 15 or more employees are covered by Title III. Courts have found liability against businesses well below enterprise scale.

The practical guidance: treat accessibility as a compliance obligation with ongoing risk, not a one-time fix. Run annual audits, fix critical failures promptly, and maintain an accessibility statement documenting your commitment and known limitations. The ADA compliance guide for websites covers the legal framework in detail.

FAQ: ADA Website Compliance 2026