What Is an Accessibility Audit?
An accessibility audit is a structured evaluation of a website against accessibility standards — most often WCAG 2.1 or 2.2 Level AA — to identify barriers that prevent people with disabilities from using it. It combines automated scanning with manual testing using keyboards and screen readers, then documents each issue, its severity, the WCAG criterion it fails, and how to fix it. For US businesses, an audit is the foundation for both ADA-related compliance and genuinely usable, inclusive websites.
- Benchmark standard
- Typically WCAG 2.1 or 2.2 Level AA (W3C)
- Two methods
- Automated scanning plus manual and assistive-technology testing (industry-typical)
- Automation coverage
- Automated tools catch only about a third to half of WCAG issues (industry-typical)
- Output
- A report listing each issue, severity, WCAG reference, and remediation steps (industry-typical)
What is the purpose of an accessibility audit? #
An accessibility audit answers a specific question: can people with disabilities actually use this website, and where does it fall short? It measures the site against an agreed standard — usually WCAG 2.1 or 2.2 Level AA — and produces a clear inventory of barriers along with guidance to remove them. Businesses commission audits for several reasons: to reduce legal risk under the ADA, to fulfill a compliance requirement, to prepare for a redesign, or simply to serve more customers well. Unlike a quick automated scan, a proper audit is thorough and human-verified, catching the many issues software cannot detect. The result is not just a pass or fail but a prioritized roadmap. For a local business, an audit turns a vague worry about accessibility into concrete, actionable steps. It is typically the starting point before any remediation work, whether that is handled in-house or through our /services/web-design and /services/website-rescue services.
Automated scanning: the first pass #
Every audit begins with automated testing, because scanners are fast, cheap, and catch a meaningful set of issues instantly. Automated tools crawl pages and flag problems like missing image alt text, insufficient color contrast, empty links and buttons, missing form labels, and certain structural errors. Our free /tools/website-grader and /tools/ada-compliance-checker give any business a quick first read on where a site stands. The critical caveat is coverage: automated tools detect only a portion of WCAG success criteria — commonly estimated at a third to half — because many criteria require human judgment. A scanner can confirm an image has alt text but not whether that text is meaningful; it can find a form field's label but not whether the focus order makes sense. So automation is a valuable filter that catches low-hanging fruit and quantifies obvious problems, but a scan alone is never an audit. Treating a green automated score as full compliance is a common and risky mistake.
Manual testing: where real issues surface #
The heart of a credible audit is manual evaluation by someone who understands accessibility. This includes navigating the entire site with only a keyboard to confirm every function is reachable and operable, focus is visible, and there are no traps. It includes testing with real screen readers — typically NVDA or JAWS on Windows and VoiceOver on Apple — to hear whether content is announced meaningfully, headings and landmarks aid navigation, and interactive widgets expose their roles and states. It includes checking whether alt text actually conveys purpose, whether error messages are clear and announced, whether the page works at high zoom and reflow, and whether content makes sense without color. These are judgments no scanner can make. Manual testing is where the issues that most affect real users — and most often appear in legal complaints — are found. It requires expertise and time, which is why a genuine audit is more involved than running a tool, and it is the standard we apply in every accessibility review.
What a good audit report contains #
The deliverable of an audit is a report that turns findings into an actionable plan. A strong report lists each identified issue with several key details: a plain-language description of the problem, the specific WCAG success criterion it fails and at what level, where it occurs (which pages or components), a severity or priority rating based on how much it blocks users, and clear guidance on how to fix it — ideally with code examples or references. Good reports group issues so that fixing one template resolves many instances, and they distinguish blocking barriers from minor enhancements. They may also note positive findings and provide an overall conformance summary. This structure lets a business or its developers work through remediation efficiently, tackling the highest-impact items first. Without prioritization and specific guidance, a raw list of hundreds of violations is overwhelming. We produce reports designed to hand directly to a development team, and we can carry out the fixes ourselves through /services/web-design or a /services/website-redesign.
Manual, automated, and expert review combined #
The most reliable audits layer three approaches. Automated scanning provides breadth, quickly checking every page for detectable issues and quantifying them. Manual expert testing provides depth, evaluating the criteria that need human judgment and simulating how assistive technology users actually experience the site. Where possible, involving people with disabilities as testers adds authentic insight that even experts can miss, revealing friction that is technically compliant but still frustrating in practice. Each method covers the others' gaps: automation alone misses most real barriers, manual testing alone is slow across large sites, and expert judgment benefits from the coverage automation provides. A serious audit uses automation to sweep broadly, then focuses expert manual effort on key templates, flows, and components — booking forms, checkouts, navigation, and dynamic widgets. This combination is how you get an accurate picture rather than a false sense of security, and it is the methodology behind our accessibility work across /services/web-app-development and /services/client-portals projects.
How often should you audit? #
Accessibility is not a one-time achievement; it degrades as a site changes. New blog posts with missing alt text, uploaded PDFs, swapped images, updated plugins, redesigned sections, and added third-party widgets can all introduce fresh barriers. A site that passed an audit at launch can drift out of compliance within months. Because of this, audits should be periodic, not singular. A common cadence is a full audit annually or before any major redesign, with lighter automated scans run frequently — monthly or after significant content changes — to catch regressions early. High-traffic conversion pages like booking and checkout flows deserve extra attention, since barriers there cost the most in both revenue and legal exposure. Building accessibility checks into your ongoing publishing and maintenance process is far cheaper than repeated full remediations. This is exactly what our /services/care-plans provide: continuous monitoring and periodic manual review so accessibility stays intact as the site evolves, rather than being rediscovered as a problem after a complaint.
Audits and legal risk in the US #
In the United States, website accessibility lawsuits and demand letters under the ADA have become common, targeting businesses of every size, including small local operations. Courts and the Department of Justice generally treat WCAG 2.1 AA as the practical measure of an accessible site, even though the ADA does not name it. An accessibility audit is central to managing this risk. It documents your current state, guides remediation to a defensible standard, and demonstrates a good-faith effort to comply — which matters if a complaint arises. An audit paired with a remediation plan and an accessibility statement shows you are taking the obligation seriously rather than ignoring it. It is far better to discover and fix barriers proactively than to first learn of them through a lawyer's letter. Our /wiki/what-is-ada-website-compliance entry explains the legal landscape in more detail, and pairing an audit with the fixes and ongoing monitoring we provide is the strongest position a business can take.
From audit to remediation #
An audit is the diagnosis; remediation is the cure. Once you have a prioritized report, the work is to fix issues in order of impact — starting with barriers that completely block users, such as unlabeled forms, keyboard traps, and unreachable controls, then addressing serious issues like poor contrast and missing structure, and finally minor enhancements. Efficient remediation often means fixing shared templates and components so that a single change resolves many flagged instances across the site. After fixes, the affected areas should be re-tested to confirm the barriers are truly gone and no new ones were introduced. For older or heavily customized sites, remediation is sometimes best combined with a /services/website-redesign, since rebuilding on a clean, semantic foundation can be faster and more durable than patching a fragile codebase. Once remediated, ongoing monitoring keeps the site conformant. We handle the full cycle — audit, prioritized remediation through /services/web-design, and continuous upkeep via /services/care-plans — so accessibility is achieved and maintained, not just measured once.
FAQ
What is the difference between an accessibility scan and an audit?
A scan is an automated test that quickly flags detectable issues like missing alt text and low contrast, catching only about a third to half of WCAG criteria. An audit is a comprehensive evaluation that adds manual keyboard and screen reader testing, expert judgment, and a prioritized report. A scan is a useful first pass; an audit is the thorough, defensible assessment.
Which standard does an accessibility audit measure against?
Most audits measure against WCAG 2.1 or 2.2 Level AA, the benchmark US courts and the Department of Justice treat as the practical measure of an accessible website. AA balances usability and achievability. Some organizations also reference Section 508 for federal contexts, which incorporates WCAG. AA conformance is the standard target for nearly all local businesses.
Can automated tools alone confirm my site is accessible?
No. Automated tools detect only a portion of WCAG issues — commonly a third to half — because many criteria require human judgment, such as whether alt text is meaningful or focus order is logical. A green automated score does not mean full compliance. Reliable results require combining automated scanning with manual keyboard and screen reader testing by someone with accessibility expertise.
How much does an accessibility audit cost?
It varies with site size and complexity. A small brochure site with a few templates costs far less to audit than a large site with custom applications, PDFs, and third-party widgets. A quick automated scan is free with tools like our /tools/ada-compliance-checker, while a full manual audit with a detailed report is a professional engagement scoped to your specific site.
How often should I audit my website?
Conduct a full audit at least annually and before any major redesign, with lighter automated scans run frequently to catch regressions from new content, plugins, and edits. Sites change constantly, so a one-time audit does not keep you compliant. High-value pages like booking and checkout flows deserve extra, more frequent attention because barriers there carry the greatest cost.
What happens after an audit finds problems?
You move to remediation, fixing issues in priority order — starting with barriers that completely block users, then serious issues, then minor enhancements. Fixing shared templates resolves many instances at once. Affected areas are re-tested to confirm the fixes. For older sites, remediation is sometimes best combined with a redesign, followed by ongoing monitoring to keep the site conformant over time.
Was this helpful?