ADA Website Compliance Checklist 2026

Published Feb 3, 2026 6 min read

Let me be blunt: ADA website lawsuits have surged past 4,000 per year, and the DOJ's 2024 rule now formally requires government websites to meet WCAG 2.1 AA. If you run a private business, courts are applying the same standard to you through Title III case law. I put this checklist together to give you everything you need to assess where you stand and actually get compliant in 2026.

In This Article

Before we get into the technical checklist, you need to understand why this matters legally. Here's where things stand:

ADA Title III and Websites

The ADA doesn't explicitly mention websites, but courts have consistently ruled that if your business is open to the public, your website counts as a "place of public accommodation" under Title III. The Robles v. Domino's Pizza case cemented this, and hundreds of rulings since have reinforced it. In other words, this isn't a gray area anymore.

DOJ Final Rule (2024)

The DOJ published a final rule requiring state and local government websites to meet WCAG 2.1 Level AA. Deadlines are April 2026 for larger entities and April 2027 for smaller ones. Now, this rule technically applies to government, but here's what you should know: it signals exactly the standard courts will hold private businesses to as well.

State Laws

Several states have their own accessibility requirements. California's Unruh Civil Rights Act, New York state law, and others create additional liability. International regulations like the European Accessibility Act (effective June 2025) affect businesses operating globally.

Key Takeaway

WCAG 2.2 Level AA is the standard you need to hit in 2026. It's your best protection against legal action, full stop. If you're not sure what WCAG actually is or how the levels work, read our breakdown of what WCAG is and why it matters. For a broader overview of the technical requirements, I'd also check our WCAG standards guide.

Technical Compliance Checklist

Here's the checklist I use when evaluating a website against WCAG 2.2 AA. Each item maps to one or more success criteria. Go through them one by one and you'll have a clear picture of where you stand.

Perceivable

  1. Images have alt text (SC 1.1.1): Every meaningful image has descriptive alternative text. Decorative images use alt="". See our alt text guide.
  2. Video has captions (SC 1.2.2): All pre-recorded video content includes synchronized captions.
  3. Audio has transcripts (SC 1.2.1): Pre-recorded audio-only content has a text transcript.
  4. Color contrast meets minimums (SC 1.4.3): Normal text has 4.5:1 ratio, large text has 3:1. Read our color contrast fix guide.
  5. Content doesn't rely on color alone (SC 1.4.1): Information conveyed by color (like error states) also uses text, icons, or patterns.
  6. Text can be resized to 200% (SC 1.4.4): Content remains readable and functional when text is enlarged to 200% without assistive technology.
  7. Content reflows on small screens (SC 1.4.10): No horizontal scrolling required at 320px width (except for data tables, images, etc.).

Operable

  1. All functionality works with keyboard (SC 2.1.1): Every interactive element can be reached and activated using only a keyboard. No keyboard traps.
  2. Focus order is logical (SC 2.4.3): Tabbing through the page follows a meaningful sequence that matches the visual layout.
  3. Focus indicators are visible (SC 2.4.7): Focused elements show a clearly visible outline or highlight. Never use outline: none without a replacement.
  4. Skip navigation link exists (SC 2.4.1): A "Skip to main content" link appears as the first focusable element, letting keyboard users bypass repeated navigation.
  5. Page titles are descriptive (SC 2.4.2): Each page has a unique <title> that describes its content and the site name.
  6. Link text is meaningful (SC 2.4.4): Links describe their destination. No "click here" or "read more" without context.

Understandable

  1. Page language is declared (SC 3.1.1): The <html> element has a lang attribute (lang="en" for English).
  2. Form inputs have labels (SC 3.3.2): Every form field has an associated <label> element. Placeholder text is not a substitute.
  3. Error messages are clear (SC 3.3.1): Form validation errors identify the field and describe the problem in text.
  4. Navigation is consistent (SC 3.2.3): Navigation menus appear in the same location and order across all pages.

Robust

  1. HTML is valid (SC 4.1.1): No duplicate IDs, proper nesting, all tags closed. Validate with the W3C validator.
  2. ARIA is used correctly (SC 4.1.2): Custom components use valid ARIA roles, states, and properties. Native HTML is preferred over ARIA where possible.
  3. Status messages use ARIA live regions (SC 4.1.3): Dynamic content changes (like "item added to cart") are announced to screen readers via aria-live.

Quick Check

Want a head start? Run a free automated scan and you'll instantly check items 1, 4, 5, 8, 10, 11, 12, 13, 14, 15, 18, and 19. The remaining items you'll need to review manually, but that gets you most of the way there.

Testing Your Website

You can't rely on just one testing method. A thorough evaluation combines automated and manual testing. Here's how I'd approach it:

Step 1: Automated Scan

Start by running a free automated scan. Automated tools typically catch 30-40% of WCAG issues, including contrast problems, missing alt text, form label issues, and ARIA errors. I'd recommend scanning your homepage plus 3-5 of your most important pages (checkout, contact form, key content pages).

Step 2: Keyboard Testing

This one's simple but revealing. Put your mouse away and try to navigate your entire site with just your keyboard. Tab to move forward, Shift+Tab to go back, Enter to activate stuff, Escape to close modals. You'll want to verify that:

  • You can reach every interactive element
  • Focus order matches the visual layout
  • You can always see which element is focused
  • You never get trapped in a component
  • Modal dialogs trap focus properly (focus stays within the dialog)

Step 3: Screen Reader Testing

I know this feels intimidating if you've never used a screen reader, but it's one of the most eye-opening things you can do. Try NVDA (it's free on Windows) or VoiceOver (already built into your Mac). Listen for:

  • Images described meaningfully
  • Headings announcing a logical structure
  • Form fields labeled correctly
  • Dynamic content changes announced

Step 4: Visual Review

Zoom to 200% and verify content reflows properly. Check that text over images maintains contrast. Verify nothing is conveyed by color alone.

Maintaining Compliance

Here's the thing most people don't realize: accessibility isn't a one-and-done project. You need to build it into your workflow:

  • Add accessibility checks to your CI/CD pipeline. Catch regressions before they reach production
  • Train your team. Developers, designers, and content authors all play a role in accessibility
  • Scan regularly. Run monthly scans to catch new issues introduced by content updates or code changes
  • Document your efforts. Publish an accessibility statement on your site. This shows good faith, gives users a way to report problems, and can actually help your legal standing if questions arise. Not sure what goes in one? Our accessibility statement guide walks you through it step by step
  • Include users with disabilities. The best testing comes from people who actually use assistive technology

One more thing: if your site runs on WordPress, a lot of this is going to depend on your theme and plugins. Some themes ship with solid accessibility baked in. Others are a mess. I wrote a separate guide on making WordPress sites ADA compliant that covers theme selection, plugin recommendations, and the specific gotchas you'll run into with page builders like Elementor and Divi.

Start Your Compliance Check

Seriously, don't wait for a demand letter. Run a free scan now and see exactly where your website stands against WCAG 2.2 AA. If the results turn up issues, I've got you covered: check out the most common WCAG 2.2 mistakes or my guide on fixing color contrast. And if you're just getting started with all of this, take a look at the accessibility guide and resource library.

Check Your ADA Compliance Now

I'll give you a full WCAG 2.2 AA accessibility report in under 60 seconds, completely free.

Run Free Scan More Articles