What Is an ADA Website Accessibility Audit? How to Audit Your Website

Author : adina watson | Published On : 03 Nov 2026

 

If you own a website in the USA, you've likely heard the term "ADA compliance" thrown around. But here's what most business owners actually want to know: Is my website at risk, and how do I find out?

The answer lies in something called an ADA website accessibility audit. It's the process of systematically evaluating your website against the Web Content Accessibility Guidelines (WCAG)—the technical standard courts and regulators use to determine whether your site discriminates against people with disabilities.

In this guide, I'll break down exactly what an ADA audit is, what it includes, and how you can audit your own website—whether you're doing a quick self-check or preparing for a professional evaluation.

What Is an ADA Website Accessibility Audit?

An ADA website accessibility audit is a structured evaluation of how well your website works for people with disabilities. It measures your site against WCAG success criteria, documents every barrier it finds, and provides a roadmap for fixing them.

Think of it like a building inspection—but for your digital storefront.

When you get an accessibility audit, you're essentially answering three questions:

  1. What barriers exist? (Missing alt text, keyboard traps, poor contrast, unlabeled forms)

  2. Who do these barriers affect? (Blind users, keyboard-only users, people with motor impairments)

  3. How severe are they? (Critical, serious, moderate, or minor)

The audit report maps every issue to the specific WCAG success criterion it violates, so you have a clear technical target for remediation.

Why This Matters More Than Ever

The legal landscape has shifted dramatically. In 2025 alone, 3,117 federal website accessibility lawsuits were filed in the U.S.—a 27% increase from the previous year. Including state courts, total digital accessibility lawsuits exceeded 5,000.

And here's the part that should concern every business owner: companies using accessibility widgets or overlays were still sued. The data shows superficial fixes don't prevent litigation.

But beyond legal risk, an audit reveals something more valuable: how many potential customers you're accidentally turning away. Over 1 in 4 U.S. adults lives with a disability. If your website creates barriers, you're losing revenue.

What's Included in a Proper ADA Accessibility Audit?

Not all audits are created equal. A scan printout is not an audit. Here's what a legitimate ADA website accessibility audit should include:

Component

What It Covers

Executive Summary

Overall compliance score and risk assessment

Full Issue List

Every finding mapped to its WCAG 2.2 success criterion

Severity Ranking

Critical, serious, moderate, and minor classifications

User Impact Analysis

Who is blocked, and from what

Code Locations

Screenshots and exact HTML locations for every issue

Remediation Guidance

Step-by-step fixes written for your development team

Manual Testing Results

Keyboard, focus order, and screen reader findings

Retest Validation

Proof that fixes actually work after implementation

Critical distinction: Automated tools alone only catch 30–40% of WCAG issues. The rest—meaningful alt text, logical reading order, real screen reader usability—requires human judgment. That's why a proper audit combines automated scanning with manual expert testing.

How to Audit Your Website: A Step-by-Step Process

You can conduct a meaningful accessibility audit yourself. It won't replace a professional evaluation for high-risk industries, but it will give you a clear picture of where you stand.

Step 1: Run Automated Scans (Your Starting Baseline)

Automated tools are fast, free, and will catch the obvious issues. Use them to establish a baseline, not a finish line.

What they find well:

  • Missing image alt text

  • Insufficient color contrast

  • Missing form labels

  • Basic HTML structure errors

  • Missing page language attributes

Recommended free tools:

  • WAVE (Web Accessibility Evaluation Tool)

  • axe DevTools (browser extension)

  • Lighthouse (built into Chrome DevTools)

  • EqualWeb Accessibility Checker (WCAG 2.2 validation)

Run scans on your top 10–20 pages—homepage, product/service pages, checkout or contact flows, and any form-heavy pages.

Step 2: Conduct Manual Keyboard Testing (The Critical Layer)

This is where you find issues automated tools miss. It takes 15–30 minutes and requires no special equipment.

The Test: Put your mouse aside. Navigate your entire site using only Tab, Shift+Tab, Enter, and Spacebar.

What to look for:

  • Can you reach every interactive element (links, buttons, forms, menus)?

  • Is there a visible focus indicator showing where you are?

  • Are there keyboard traps where you get stuck and can't move forward?

  • Can you open and close menus and modals?

  • Can you complete a purchase or form submission?

If you get stuck anywhere, a keyboard user gets stuck there too. That's a barrier.

Step 3: Test with a Screen Reader

This is the most accurate way to understand the experience of a blind or low-vision user.

Free screen readers to try:

  • NVDA (Windows)

  • VoiceOver (Mac, built-in)

  • TalkBack (Android)

What to listen for:

  • Does the screen reader announce images meaningfully, or just say "image" or read a filename?

  • Are form fields properly labeled?

  • Does the reading order make sense?

  • Are error messages announced when they appear?

  • Can you understand the page structure from the headings?

This can be humbling, but it's the fastest way to find real barriers.

Step 4: Test Zoom and Reflow

Users with low vision often zoom in significantly. Test your site at 200% zoom and even 400% zoom.

What to check:

  • Does content remain readable?

  • Does the layout break or require horizontal scrolling?

  • Is any text cut off?

  • Do interactive elements still work?

Step 5: Evaluate Color and Contrast

Color is a common barrier that's easy to overlook.

The standards:

  • Body text: 4.5:1 contrast ratio

  • Large text (18pt+ or 14pt bold): 3:1

  • UI components and graphics: 3:1

Tools: WebAIM's Contrast Checker, or the color contrast features in axe DevTools.

Critical rule: Never rely on color alone to convey information (e.g., "Required fields are in red"). Use text labels, icons, or patterns as well.

Step 6: Review Content Structure

Good structure is essential for both accessibility and SEO.

Check for:

  • One H1 per page that describes the content

  • Logical H2, H3, H4 hierarchy (no skipping levels for styling)

  • Semantic HTML (using <nav>, <main>, <button> instead of generic <div> tags)

  • Descriptive link text (not "click here" or "read more")

  • Sufficient white space and readable line length

Step 7: Test with Real Users (The Gold Standard)

The most valuable feedback comes from people who actually use assistive technology every day.

If you're serious about compliance, engage testers with disabilities. Their lived experience will reveal barriers that no automated tool or checklist can catch.

WCAG 2.2: What's New in 2026

If your last audit was against WCAG 2.1, you're most of the way there. But WCAG 2.2 adds nine new success criteria—six at Level AA—that address real-world gaps.

Here are the new Level AA criteria you need to check:

Criterion

What It Requires

2.4.11 Focus Not Obscured

Sticky headers and chat widgets must not completely hide focused elements

2.5.7 Dragging Movements

Anything done by dragging must also work with simple clicks

2.5.8 Target Size

Interactive targets must be at least 24×24 CSS pixels

3.2.6 Consistent Help

Help mechanisms must appear in the same location on every page

3.3.7 Redundant Entry

Never force users to re-enter information already provided

3.3.8 Accessible Authentication

No memorization or transcription tests for login

Important context: The DOJ extended compliance deadlines for state and local governments under Title II. Entities with populations of 50,000+ now have until April 26, 2027, and smaller entities until April 26, 2028. But private businesses under Title III face no such delay—lawsuits continue regardless.

DIY Audit vs. Professional Audit: Which Do You Need?

Here's an honest breakdown:

DIY audit is sufficient if:

  • You have a small, static website (under 50 pages)

  • You're not in a high-risk industry (e-commerce, healthcare, food service, finance)

  • You have basic HTML/CSS knowledge

  • You haven't received any legal complaints

Professional audit is recommended if:

  • You're in e-commerce, healthcare, finance, or food service

  • You have a complex, dynamic website or web application

  • You've received an ADA demand letter

  • You need formal documentation (VPAT/ACR) for procurement or contracts

  • You want a defensible record of good-faith compliance efforts

A professional audit typically costs 3,000–15,000 depending on site complexity, but it provides thorough coverage and documented evidence that DIY testing can't match.

Common Mistakes to Avoid

Mistake #1: Relying solely on an accessibility widget or overlay.
Data from 2025 shows companies using overlays were still targeted by lawsuits. The FTC has also scrutinized overlay providers. Real compliance requires code-level fixes, not just a JavaScript band-aid.

Mistake #2: Treating it as a one-time project.
Accessibility decays. Every new page, plugin, or design update can introduce new barriers. Continuous monitoring is essential.

Mistake #3: Ignoring third-party tools.
Your chat widget, payment processor, review platform, and booking system are all part of the user experience. If they create barriers, you may still be held responsible.

Mistake #4: Assuming "we're too small to be sued."
Plaintiff firms don't discriminate by company size. Of 2025 lawsuits, a significant portion targeted small and mid-sized businesses.

How Accessibility Audits Drive SEO and Traffic

Here's what most SEO agencies won't tell you: accessibility audits directly improve your search visibility.

Why? Because accessible websites are easier for search engines and AI systems to understand.

  • Better structure → WCAG requires semantic HTML, logical heading hierarchy, and meaningful link text. These are exactly what Google's crawlers need to understand your content.

  • More indexable content → Captions, transcripts, and alt text create additional content that search engines can index.

  • Lower bounce rates → When everyone can use your site comfortably, engagement signals improve.

  • AI discoverability → AI systems (Google AI Overviews, ChatGPT, Perplexity) rely on structured, machine-readable content. Accessible sites are naturally more AI-friendly.

The businesses that treat accessibility as an SEO strategy aren't just avoiding lawsuits—they're winning more traffic and conversions.

Your Action Plan

Here's how to get started:

  1. Run a free automated scan on your top 10 pages to get a baseline

  2. Do a 15-minute keyboard test on your homepage and checkout/contact flow

  3. Fix the quick wins (alt text, contrast, form labels, heading structure)

  4. Document what you find and fix—this becomes your evidence of good-faith effort

  5. Consider a professional audit if you're in a high-risk industry or want formal documentation

  6. Build accessibility into your workflow—training, CMS standards, and regular testing

Ready to see where your website stands? Ariaprobe offers accessibility testing tools and expert guidance to help you identify gaps, prioritize fixes, and build a more inclusive—and compliant—website.

Frequently Asked Questions

Is there an official "ADA certification"?
No. The ADA doesn't offer certification. Compliance is demonstrated through conformance with WCAG standards, documented testing, and an accessibility statement. Third-party audits and VPATs/ACRs can provide evidence, but they're not government-issued.

How often should I audit my website?
At minimum, annually. But best practice is continuous monitoring combined with testing after any major update, redesign, or new content deployment.

Can I just install an accessibility widget and be done?
No. While widgets can provide helpful user-facing tools, they don't fix underlying code issues. Courts and experts agree that overlays alone are not sufficient for compliance.

What's the difference between an audit and a scan?
A scan is automated and catches 30–40% of issues. An audit combines automated scanning with manual expert testing, user impact analysis, and remediation guidance. Scans are a starting point; audits are the complete picture.

I'm a small business. Do I really need an audit?
If you have a website, you have legal exposure. A basic audit—even a DIY one—demonstrates good-faith effort and helps you prioritize fixes. The accessibility improvements also benefit your SEO and user experience.

 


 

Accessibility isn't just about avoiding lawsuits. It's about building a website that works for everyone—and in doing so, building a website that search engines, AI systems, and humans all understand better. That's good for compliance, good for SEO, and good for business.