Website Accessibility Audit: A Business Owner's Guide (2026)

Almost every website you visit is breaking accessibility law right now. In 2026, 95.9% of the top one million home pages had detectable WCAG failures, with an average of 56.1 errors on a single page (WebAIM Million, 2026). Your site is very likely one of them.

A website accessibility audit is how you find out for sure, and how you fix it before a demand letter or a lost enterprise deal forces your hand. This guide walks you through what an audit actually does, what it costs, and how to run your first one, written for the person signing the invoice rather than the developer writing the code.

Key Takeaways

• 95.9% of home pages fail automated WCAG checks, averaging 56.1 errors each (WebAIM, 2026).
• Over 4,000 digital accessibility lawsuits were filed in 2024, and 77% targeted e-commerce (UsableNet, 2025).
• An audit produces a VPAT or Accessibility Conformance Report, the document enterprise and government buyers ask for before they sign.
• Fixing issues early is far cheaper than fixing them in production, where industry estimates put the cost as high as 100x (Deque).

What Is a Website Accessibility Audit?

A website accessibility audit is a structured review of your site against the Web Content Accessibility Guidelines (WCAG), the global standard that defines whether people with disabilities can actually use your pages. It produces a list of every place your site fails, ranked by severity, plus the fixes. Think of it as a home inspection, but for whether a blind, deaf, or motor-impaired visitor can complete the same tasks everyone else can.

The benchmark almost every law points to is WCAG 2.1 or 2.2 at Level AA. That covers things like color contrast, keyboard navigation, text alternatives for images, and form labels. An audit checks each of those criteria and tells you, in plain terms, what passes and what doesn't.

According to the most recent WebAIM Million report, 95.9% of the top one million home pages had detectable WCAG 2 failures, up from 94.8% the year before (WebAIM, 2026). An audit is simply the act of confirming whether you sit inside that 95.9% and, more importantly, getting a map out of it. For the technical side of testing, our practical guide to testing your website for accessibility goes deeper on the hands-on methods.

Why Does Your Business Need an Audit Now?

Three forces make this urgent: lawsuits, a new European deadline, and a market you're quietly turning away. Over 4,000 digital accessibility lawsuits were filed in 2024, and 77% of them targeted e-commerce businesses (UsableNet, 2025). If you sell anything online, you're in the most-sued category.

The legal pressure is climbing, not leveling off. Federal ADA Title III filings rebounded to roughly 8,800 in 2024, a 7% increase, and around 28% of those involved websites (Seyfarth Shaw, 2025). According to defense-attorney interviews compiled by Accessible.org, a typical website settlement lands between $5,000 and $20,000, and the remediation work it forces on you often costs more than the cash payout (Accessible.org). That's the expensive way to get an audit: after you've been sued.

Then there's Europe. The European Accessibility Act came into force on June 28, 2025, requiring digital products and services to meet accessibility standards aligned with WCAG 2.1 AA (European Commission, 2025). It applies to non-EU companies selling to EU consumers too, and penalties vary by member state. If you ship to Europe, that deadline is already behind you. Our European Accessibility Act deadline guide breaks down who is covered.

What we see in practice: the businesses that treat an audit as a one-time legal chore tend to get sued twice. UsableNet found that 41% of 2024 lawsuit targets were repeat defendants, and roughly 25% of sued sites had an accessibility widget or overlay installed when they were sued. A scan-and-forget approach, or a bolt-on overlay, is not the same as conformance.

There's also money on the table you're ignoring. More than one in four US adults, over 70 million people, report a disability (CDC, 2024), and globally about 1.3 billion people live with a significant disability (WHO, 2024). US adults with disabilities hold an estimated $490 billion in disposable income, a figure from a 2018 study that remains the canonical US number (American Institutes for Research, 2018). Globally, the disability market and its immediate community is estimated to control around $13 trillion in annual disposable income (Return on Disability, 2024). An inaccessible checkout doesn't just risk a lawsuit. It declines the sale.

What Does an Accessibility Audit Actually Check?

An audit checks your site against the WCAG success criteria, but in practice a handful of failures account for almost everything found. The same WebAIM data shows that six categories of error make up 96% of all detected problems, which means the typical audit finds the same recurring issues over and over.

Here's what shows up most often across the web's home pages:

| WCAG failure | Home pages affected | What it breaks | |---|---|---| | Low-contrast text | 83.9% | Text invisible to low-vision users | | Missing image alt text | 53.1% | Screen readers skip your images | | Missing form input labels | 51% | Users can't tell what a field wants | | Empty links | 46.3% | Navigation reads as meaningless | | Empty buttons | 30.6% | Actions can't be triggered or understood |

Source: WebAIM Million, 2026.

A real audit has two halves. Automated scanning catches the high-volume, machine-detectable issues fast, things like contrast ratios and missing alt attributes. But automated tools only catch a portion of WCAG criteria. The rest, like whether your page makes sense when navigated by keyboard alone, or whether a screen reader announces a modal correctly, needs manual testing by a human using assistive technology.

Our take: automated-only audits give business owners false confidence. They'll clear the easy 30% to 40% of criteria and stay silent on the judgment-based failures that get sites sued. When a vendor sells you a "100% automated audit," read that as "we checked the third of the rules a robot can check."

How Much Does an Accessibility Audit Cost?

Cost depends on which of three routes you take, and the cheapest route is rarely the cheapest outcome. The real lever isn't the audit price, it's when you fix what the audit finds. Industry estimates, drawing on IBM software-defect research, put the cost of fixing a defect in production at up to 100x what it costs in design (Deque).

Here are the typical options:

| Approach | Rough cost | Best for | |---|---|---| | Automated scan tool | Free to low monthly fee | Ongoing monitoring, catching the obvious 30 to 40% | | Self-run audit (tool plus your time) | Mostly staff hours | Small sites, early-stage validation | | Expert manual audit / agency | Several thousand and up per site | Conformance claims, VPATs, legal defensibility |

For most business owners, the smart sequence is to run a free automated scan first to gauge how deep the problem goes, then decide whether the gaps justify hiring a specialist. A scan won't make you compliant, but it tells you whether you're looking at a weekend of fixes or a quarter of remediation.

Why does waiting cost so much more? Because an issue baked into a component, a custom date picker with no keyboard support, say, gets copied across dozens of pages before anyone catches it. Fix the component during design and you fix it once. Fix it after launch and you're retesting every page it touched.

Should You DIY or Hire an Expert?

Run it yourself when the stakes are low and the goal is awareness; hire an expert when you need a defensible conformance claim. The dividing line is what you're going to do with the result. A scan to satisfy your own curiosity is a DIY job. A document you'll hand to a procurement officer or wave at a plaintiff's attorney is not.

You can comfortably DIY when:

• Your site is small and mostly static content.
• You want a first read on how bad the problem is.
• You have a developer who can act on the findings.

Bring in a specialist when:

• An enterprise or government buyer is asking for a VPAT.
• You've received a demand letter or want to reduce legal exposure.
• Your site has complex interactions: checkout flows, dashboards, custom widgets.

The good news is these aren't mutually exclusive. Many businesses self-audit continuously with automated tooling and bring in a human expert once or twice a year for the manual layer. If you'd rather not manage that relationship directly, a marketplace of vetted accessibility specialists lets you match the scope of work to the budget. We compared the platform options in VPATify versus Level Access.

What Do You Get at the End? Your VPAT

The deliverable that matters most to buyers is a VPAT, the Voluntary Product Accessibility Template, which once completed becomes an Accessibility Conformance Report (ACR). It documents, criterion by criterion, how your product conforms to WCAG and Section 508. When a federal agency or a large enterprise evaluates your software, this is the document they ask for before signing (Section508.gov).

A good audit feeds straight into a VPAT. The audit finds the gaps, you remediate, and the resulting report states "Supports," "Partially Supports," or "Does Not Support" for each criterion, honestly. That honesty is the point: a VPAT isn't a compliance badge, it's a disclosure. Enterprise buyers trust an accurate "Partially Supports" far more than a suspicious wall of green checkmarks.

For business owners selling to government or large organizations, the VPAT is often the difference between making the shortlist and getting filtered out before the demo. It turns accessibility from a cost center into a sales asset.

How to Run Your First Accessibility Audit: Step by Step

You can complete a meaningful first audit in an afternoon. The goal of this first pass isn't a perfect conformance claim, it's to size the problem and decide your next move. Here's the sequence.

Step 1: Define your scope

List your most important pages and flows: home page, top landing pages, the signup or checkout path, and your contact form. You don't need every URL. You need the journeys that earn revenue, because those are the ones that get sued and the ones that lose customers.

Step 2: Run an automated scan

Use a WCAG scanner to crawl those pages. It will flag the high-volume issues, contrast, alt text, labels, in minutes. Export the report. This is your baseline and your worst-offenders list. Remember the WebAIM finding: expect dozens of issues per page, not a handful.

Step 3: Test with a keyboard

Put your mouse away and tab through each key page. Can you reach every link, button, and form field? Can you see where you are as focus moves? Can you open and close menus and modals? Keyboard access is a huge share of real-world failures and you can test it yourself in minutes, no tools required.

Step 4: Test with a screen reader

Turn on the screen reader already on your computer, VoiceOver on Mac, Narrator or NVDA on Windows, and try to complete one core task with your eyes closed. It's uncomfortable the first time. That discomfort is exactly what your disabled customers experience, and it tells you more than any scan.

Step 5: Prioritize and remediate

Sort findings by severity and reach. Fix anything that blocks a core task first, a checkout button a screen reader can't announce outranks a low-contrast footer link. Map each issue to the relevant WCAG criterion so the work feeds cleanly into a VPAT later. If you're new to the criteria, what's new in WCAG 2.2 explains the current standard.

Step 6: Re-test and monitor

Accessibility isn't a one-and-done project. Every new feature, every content update, can introduce regressions. Schedule recurring scans so you catch new issues before your customers, or a plaintiff, do.

Ready to See Where You Stand?

You don't have to guess whether your site is in the 95.9% that fail. Run a free accessibility scan with VPATify and get a plain-English report of what's broken, ranked by severity, in minutes. If the gaps run deep, you can connect with a vetted specialist to handle the manual audit and your VPAT, all in one place. Start with the scan, then decide.

Frequently Asked Questions

How long does a website accessibility audit take?

An automated scan takes minutes. A thorough manual audit of a typical site takes a few days to a couple of weeks, depending on complexity. Given that 95.9% of home pages fail automated checks alone (WebAIM, 2026), most sites need both the fast scan and the slower human review to reach a defensible conformance claim.

Will an accessibility overlay or widget make my site compliant?

No. Overlays are a common shortcut that doesn't deliver conformance. UsableNet found that roughly 25% of businesses sued in 2024 had an accessibility widget installed at the time (UsableNet, 2025). Real fixes happen in your code, not in a bolt-on script.

What's the difference between an audit and a VPAT?

An audit is the testing process that finds your accessibility gaps. A VPAT is the document that reports how your product conforms to WCAG and Section 508, used by enterprise and government buyers during procurement (Section508.gov). The audit feeds the VPAT: you test, you fix, then you document.

Does accessibility help my SEO?

Yes, the two overlap heavily. Descriptive link text, logical heading structure, image alt text, and clean semantic HTML are core to both accessibility and search visibility. Improving the structure a screen reader relies on also improves what a search crawler understands, so an audit often pays back in rankings as well as compliance.

How often should I audit my website?

Treat scanning as continuous and manual audits as periodic. Run automated scans on every significant release, and schedule a full manual audit at least once a year, or whenever you ship a major feature. Repeat lawsuit targets made up 41% of 2024 cases (UsableNet, 2025), which is what happens when a site is fixed once and never re-checked.

Conclusion

A website accessibility audit is no longer optional housekeeping. With 95.9% of sites failing WCAG, lawsuits climbing past 4,000 a year, and the European Accessibility Act now in force, the question isn't whether your site has problems, it's whether you'll find them on your terms or someone else's.

Start small. Define your key pages, run a free scan, test with a keyboard, and size the gap. From there you can decide whether a weekend of fixes will do or whether it's time to bring in a specialist and produce a VPAT. The cheapest audit is always the one you run before the demand letter arrives, not after.

Ready to begin? Run your free accessibility scan and see exactly where you stand today.