# Accessibility Audit: How a WCAG Website Review Works

Source: https://allyway.ai/glossary/accessibility-audit

An accessibility audit is a structured review of a website or app against an accessibility standard, usually WCAG 2.2 Level AA. It combines automated tests with manual checks by experts and ends in a report that lists each barrier, where it occurs and how to fix it.

An accessibility audit is a structured check of a website against an accessibility standard – in practice almost always [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2) at Level AA. It shows which barriers stop people with disabilities from using your pages, where exactly they are and what to do about them. A good audit is the starting point for fixing issues, writing an accessibility statement and proving progress over time.

## What it means

W3C calls this process evaluation. Its guidance is clear that tools help but "no tool alone can determine if a site meets accessibility standards" – knowledgeable people have to make the final judgment. An accessibility review therefore always mixes three kinds of work:

| Method | What it finds | Limits |
|---|---|---|
| Automated testing | Missing alt text, empty links and buttons, low contrast, missing labels, a missing `lang` attribute | Cannot judge meaning – whether alt text is accurate or a heading makes sense |
| Manual expert review | Keyboard traps, focus order, reading order, unclear error messages | Takes time and skill |
| Testing with users | Real problems with screen readers, magnifiers and voice control | Needs planning and participants |

For a full WCAG audit of a whole website, W3C publishes a methodology called [WCAG-EM](https://www.w3.org/WAI/test-evaluate/conformance/wcag-em/). It has five steps: define the scope of the evaluation, explore the website, select a representative sample, evaluate the selected sample and report the findings. The sample matters – nobody checks 5,000 product pages by hand, but every template (home page, category, product, checkout, forms) must be in it.

The target is a [conformance level](https://allyway.ai/glossary/wcag-conformance-levels). Laws such as the [European Accessibility Act](https://allyway.ai/regulations/eaa) and the German [BFSG](https://allyway.ai/glossary/bfsg) point to [EN 301 549](https://allyway.ai/glossary/en-301-549), which in turn uses WCAG Level AA for web content.

> **Note:** > **An audit is a snapshot**
> The report describes the site on the day it was tested. Every new page, plugin or theme update can add new barriers. Plan regular re-checks or continuous monitoring instead of one audit every few years.

## Examples

A typical audit finding names the criterion, the place and the fix:

```html title="Example"
<!-- Finding: WCAG 4.1.2 Name, Role, Value (Level A)
     Page: /checkout – search icon in the header has no accessible name -->
<button class="search-toggle">
  <svg>…</svg>
</button>

<!-- Recommended fix -->
<button class="search-toggle" aria-label="Search">
  <svg aria-hidden="true" focusable="false">…</svg>
</button>
```

**Do:** Do

Define the scope first (domains, templates, key user journeys), test with tools and by hand, include keyboard and screen reader checks, and write findings with criterion, location, severity and a concrete fix. Re-test after fixes.

**Don't:** Don't

Rely on one automated score, test only the home page, skip forms and checkout, or treat the report as a certificate that stays valid forever.

## How to prepare an accessibility audit



## Questions

Q: What does an accessibility audit include?
A: A defined scope, a sample of pages, automated and manual tests against WCAG, and a report with every barrier, the affected criterion, where it occurs, how severe it is and how to fix it.

Q: How long does an accessibility audit take?
A: It depends on the scope and the number of templates. A small website with a few templates can be reviewed in days; a large shop or web app with many journeys takes weeks.

Q: Is an automated test enough for an accessibility audit?
A: No. W3C states that no tool alone can determine whether a site meets accessibility standards. Automated tests find a large share of the technical errors quickly, but questions of meaning – is this alt text correct, does this error message help – need a person.

Q: How often should a website be audited?
A: After every redesign or relaunch, and in between whenever major features are added. Many teams combine a yearly expert review with ongoing automated checks of every page.

Q: How can I start before booking a full audit?
A: Run a quick automated check to see the biggest problems on your home page. The [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) tests a page against WCAG 2.2 AA in seconds and shows where to begin.
