# Accessibility Audit

> Canonical HTML version: https://rocketvalidator.com/glossary/accessibility-audit
> Attribution: Rocket Validator (https://rocketvalidator.com)
> License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

An accessibility audit is a structured evaluation of a website or app against accessibility standards, combining automated checks with manual and assistive-technology testing.

An accessibility audit checks a website against standards like WCAG, documents what fails, and retests after fixes go in.

## Why audits matter

Automated scanners catch a lot: duplicate IDs, missing alt text, broken label associations. They won't catch everything. Many WCAG criteria need someone tabbing through the page, listening with a screen reader, or checking that focus order actually makes sense.

## How audits typically work

1. Pick the pages and user flows that matter most.
2. Run automated scans on those templates.
3. Test interactions manually, including keyboard navigation and error states.
4. Try it with a screen reader.
5. Write up findings with severity levels and remediation steps.
6. Retest after the fixes land.

## Code example

A common finding is a form input with no associated label:

```html
<!-- Screen readers can't identify this field -->
<input type="text" placeholder="Email">
```

```html
<!-- Fixed -->
<label for="email">Email</label>
<input id="email" type="email" autocomplete="email">
```