Category: Testing and Evaluation

Accessibility Audit

Also known as: Accessibility Assessment, Accessibility Compliance Testing, Digital Accessibility Audit

Simply put

An accessibility audit is an evaluation of how well a website, mobile app, or other digital product works for people with disabilities. It typically combines automated tools with hands-on review by accessibility specialists, including testing with assistive technologies such as screen readers. The goal is to identify barriers that may prevent people with disabilities from using the digital product.

Formal definition

An accessibility audit is a structured evaluation of a digital asset's accessibility, generally combining automated testing with manual review conducted by accessibility experts using assistive technologies. Audits are commonly benchmarked against recognized technical standards such as the Web Content Accessibility Guidelines (WCAG), most often at Level AA, though the specific version and conformance target should be defined for each engagement. Because automated tools detect only a portion of potential issues, thorough audits incorporate manual and assistive-technology testing to assess real-world usability. An audit reports conformance findings but does not by itself guarantee full accessibility, usability for all users, or legal compliance; jurisdictional requirements evolve through regulation and case law, and organizations should consult qualified legal counsel for compliance determinations.

Why it matters

An accessibility audit is one of the primary ways organizations understand whether their digital products actually work for people with disabilities, rather than assuming they do. Because automated tools detect only a portion of potential accessibility issues, an audit that combines automated testing with manual review and assistive-technology testing provides a far more realistic picture of the barriers users may encounter. This matters because barriers such as unlabeled controls, poor keyboard support, or content that a screen reader cannot interpret can effectively exclude people with disabilities from using a service at all.

Audits are also valuable as a planning and prioritization tool. Findings are commonly benchmarked against recognized technical standards such as the Web Content Accessibility Guidelines (WCAG), most often at Level AA, which gives organizations a structured framework for identifying, categorizing, and remediating issues. Establishing a clear scope, target WCAG version, and conformance level for each engagement helps teams set expectations and measure progress over time.

It is important to understand what an audit does not do. An audit reports conformance findings at a point in time; it does not by itself guarantee full accessibility, usability for every user, or legal compliance. Jurisdictional requirements evolve through regulation and case law, and the applicable authority may differ depending on whether an organization is a federal agency, a state or local government entity, or a place of public accommodation. Organizations should treat audit results as technical guidance and consult qualified legal counsel for compliance determinations.

Who it's relevant to

Accessibility Engineers and Developers

Engineers and developers rely on audit findings to locate and remediate specific barriers, from missing labels to keyboard traps. A detailed audit that maps issues to WCAG success criteria helps teams understand the technical cause of each finding and validate fixes through follow-up testing, including manual and assistive-technology checks.

UX and Product Designers

Designers use audit results to understand how design decisions affect people who use assistive technologies. Findings related to focus order, contrast, form controls, and content structure can inform design patterns and help prevent recurring barriers in future work.

Compliance Officers and Business Leaders

Compliance officers and leaders use audits to gauge how well digital products align with a chosen standard such as WCAG Level AA and to prioritize remediation. Audit findings support planning and risk assessment, but they do not by themselves establish legal compliance, and organizations should pair them with guidance from qualified counsel.

Legal Counsel

Legal counsel may review audit findings when assessing an organization's accessibility posture, keeping in mind that the applicable legal authority varies by context, that requirements evolve through regulation and case law, and that a conformance report is technical evidence rather than a determination of legal compliance.

Procurement and Vendor Management Teams

Teams evaluating third-party digital products or services can use accessibility audits to assess how accessible a vendor's product is before or during procurement. Defining the audit scope, target WCAG version, and conformance level in advance helps set clear, comparable expectations across vendors.

Inside Accessibility Audit

Automated Testing

The use of software tools to scan digital content for detectable accessibility issues, such as missing alternative text, insufficient color contrast, or improper markup. Automated testing detects only a portion of potential issues and cannot fully evaluate context, meaning, or user experience.

Manual Testing

Human evaluation of content against accessibility standards, including keyboard navigation, logical reading order, focus management, and other criteria that automated tools generally cannot assess reliably.

Assistive Technology Testing

Evaluation using tools such as screen readers, screen magnifiers, and voice control software to assess how people who use assistive technology actually experience the content. This step is required to identify barriers that automated and manual checks may miss.

WCAG Benchmarking

Measuring content against the Web Content Accessibility Guidelines (WCAG), published by the W3C through the Web Accessibility Initiative. Audits commonly reference conformance level AA, and should specify which WCAG version (2.0, 2.1, or 2.2) is used, since success criteria differ across versions.

Scope Definition

A clear statement of which pages, screens, components, documents, or user flows are covered by the audit, and which are out of scope. Scope determines the completeness and interpretation of the findings.

Findings and Remediation Report

Documentation of identified issues, often prioritized by severity or impact, with references to the relevant success criteria and suggested remediation approaches. This report supports planning but does not by itself confirm legal compliance.

Common questions

Answers to the questions practitioners most commonly ask about Accessibility Audit.

Does passing an accessibility audit mean my website is legally compliant?

No. An accessibility audit assesses conformance against a technical standard such as WCAG, but conformance is not the same as legal compliance. Meeting WCAG success criteria does not guarantee immunity from legal claims, and legal requirements are shaped by statutes, regulations, agency guidance, and evolving case law that vary by jurisdiction and context. An audit can be strong supporting evidence of a good-faith accessibility effort, but it is not a substitute for advice from qualified legal counsel. This entry is not legal advice.

Can an automated tool perform a complete accessibility audit on its own?

No. Automated testing detects only a portion of accessibility issues, generally those that can be evaluated programmatically. Many barriers, such as whether alt text is meaningful, whether focus order is logical, or whether content is usable with a screen reader or keyboard, require manual evaluation and testing with assistive technologies. A thorough audit combines automated scanning with manual expert review and assistive technology testing rather than relying on any single tool.

Which standard and conformance level should an accessibility audit be measured against?

Audits are commonly measured against the Web Content Accessibility Guidelines (WCAG) published by the W3C, most often at the AA conformance level, which is the level most frequently cited as a target. You should confirm the specific WCAG version (for example 2.0, 2.1, or 2.2) and level before the audit begins, since success criteria differ across versions and some criteria were added in later releases. The appropriate benchmark may also depend on the applicable authority for your context, such as Section 508 for covered federal contexts or the relevant Title of the ADA.

What should the scope of an accessibility audit include?

Scope should be defined before the audit and typically identifies the target standard and conformance level, the representative pages, templates, and user flows to be evaluated, the browsers and assistive technologies to be tested, and whether components such as documents, PDFs, mobile apps, or third-party embedded content are included. Because auditing every page is often impractical, a representative sample is commonly selected, and any areas left out of scope should be documented so gaps are understood.

How often should an accessibility audit be performed?

Because digital content changes frequently and standards and legal expectations evolve, accessibility is generally treated as an ongoing process rather than a one-time event. Organizations often schedule periodic audits and also evaluate accessibility when significant changes are made, such as redesigns, new features, or new content types. Ongoing monitoring, testing during development, and remediation tracking are commonly used to maintain accessibility between full audits.

What is typically included in the deliverables from an accessibility audit?

Audit deliverables commonly include a report of identified issues mapped to specific WCAG success criteria, an indication of severity or user impact, the methods used (automated, manual, and assistive technology testing), and remediation guidance describing how issues can be addressed. Clear documentation of scope, methodology, and any limitations helps stakeholders prioritize fixes and understand what was and was not evaluated.

Common misconceptions

An accessibility audit can be completed entirely with automated tools.

Automated testing detects only a portion of accessibility issues. A meaningful audit generally requires manual testing and assistive technology testing to evaluate context, usability, and barriers that software cannot reliably identify.

Passing an audit guarantees legal compliance and protection from claims.

Meeting WCAG success criteria or passing audit checks does not guarantee an accessible experience for all users, nor immunity from legal claims. Requirements evolve through regulation and case law, and organizations should consult qualified legal counsel. This guidance is not legal advice.

An audit against WCAG is the same as satisfying a specific legal requirement under the ADA.

The ADA is a US civil rights law and does not itself contain detailed web technical specifications. Courts and settlements have often referenced WCAG as a benchmark rather than a codified rule. Applicable authority may differ, for example Title II of the ADA for state and local government, Title III for places of public accommodation, and Section 508 for federal contexts.

Best practices

Define and document the audit scope clearly, specifying which pages, flows, components, and documents are covered and which are excluded.

Combine automated, manual, and assistive technology testing rather than relying on automated tools alone, since automated checks detect only a portion of issues.

State the WCAG version (2.0, 2.1, or 2.2) and conformance level being evaluated, noting that level AA is the most commonly cited target.

Prioritize findings by user impact and severity, and reference the specific success criteria involved to support remediation planning.

Treat conformance as distinct from usability and from legal compliance, and involve people who use assistive technology where feasible to validate real-world experience.

Consult qualified legal counsel and monitor current agency rulemaking and case law for the applicable jurisdiction, as audit results are not legal advice.