Direct answer
A website accessibility audit combines automated testing with knowledgeable human evaluation.
A website accessibility audit combines automated testing with knowledgeable human evaluation. Inspect semantic structure, keyboard operation, focus, names and labels, alternatives, contrast, zoom and reflow, forms and errors, motion, media, and complete user tasks. Document the page and state tested, evidence, relevant requirement, user impact, and reproducible remediation, not only a tool score.
An automated score is not WCAG certification or legal advice. Conformance evaluation requires the applicable standard, defined scope, and knowledgeable human review.
Audit checklist
Inspect each layer and record the evidence behind the result.
| Area | What to verify | Why it matters |
|---|---|---|
| Structure | Page language, title, landmarks, headings, lists, tables, and reading order convey meaning. | Assistive technologies depend on programmatic relationships. |
| Operation | Every control works by keyboard with visible focus, logical order, and no trap. | Mouse-independent operation is essential for many users. |
| Names and alternatives | Controls have accurate accessible names; meaningful images and media have appropriate alternatives. | A control or image without meaning cannot be used reliably. |
| Perception | Text contrast, non-text contrast, zoom, reflow, spacing, motion, flashing, and media support varied perception. | Visual polish can conceal barriers under magnification or alternate settings. |
| Tasks and recovery | Forms, errors, authentication, status messages, timeouts, and complete journeys are understandable and recoverable. | Individual compliant elements can still combine into an unusable workflow. |
Scope
Audit representative experiences, not just convenient URLs.
Select pages by template, component, content type, state, and user task. Include errors, empty states, dialogs, authentication, forms, media, documents, and responsive layouts when they exist.
Record browser, operating system, viewport, zoom, screen reader, input method, authentication state, date, and code version. Reproducible context makes a finding actionable.
Layered testing
Let automation find deterministic defects and people evaluate meaning and use.
Automated checks efficiently identify some missing names, invalid semantic relationships, contrast failures, and structural issues. Review the evidence because dynamic state and hidden content can produce false positives or incomplete results.
Manual testing evaluates whether focus moves sensibly, instructions make sense, alternatives serve the same purpose, error recovery works, and complete tasks remain possible. Include users with disabilities in research and testing when the scope and resources allow.
Remediation
Fix the system that produced the barrier and verify the human outcome.
Trace repeated defects to shared components, content rules, tokens, or authoring systems. A component-level fix can remove barriers across many routes, but its larger blast radius requires regression testing.
Retest the original evidence and the complete task with the same tools and settings. A changed automated score is useful evidence, but the user outcome is the acceptance criterion.
Common mistakes
Avoid conclusions that the available evidence cannot support.
01
Equating a score with conformance
A number cannot establish complete WCAG conformance or replace qualified evaluation.
02
Testing only the happy state
Errors, validation, timeouts, disabled controls, dialogs, and recovery often contain the most serious barriers.
03
Patching instances instead of components
The same inaccessible pattern returns when its shared source remains unchanged.
Audit workflow
How to run a website accessibility audit
Step 1
Define representative scope
Choose templates, components, content types, states, devices, assistive technologies, and complete tasks that represent the experience.
Step 2
Run automated checks
Collect deterministic issues such as missing names, invalid relationships, contrast failures, and semantic defects, then remove false positives.
Step 3
Evaluate manually
Test keyboard and focus, screen-reader reading and operation, zoom and reflow, content clarity, media, errors, and complete tasks.
Step 4
Report, fix, and retest
Prioritize blocking and repeated component defects, specify acceptance evidence, and retest with the same method after deployment.
Collect current evidence for the public page before creating remediation work.
FAQ
Website accessibility audit checklist FAQ
Can an automated checker certify WCAG compliance?
No. W3C explains that tools assist evaluation but knowledgeable human evaluation is required to determine accessibility and conformance.
What should I test with a keyboard?
Reach and operate every interactive element, confirm a visible logical focus order, test dialogs and menus, avoid traps, and verify skip or landmark navigation.
Which pages belong in an accessibility audit?
Include representative templates and critical tasks, plus unique components, forms, authentication, errors, media, documents, and states that automated crawls may miss.
How should accessibility findings be prioritized?
Start with barriers that block task completion, affect many users or repeated components, create safety or legal exposure, or have no workable alternative.
Primary references
Standards and platform documentation used for this guide.
Technical summary
Website accessibility audit checklist in five statements
- A website accessibility audit requires automated and manual evaluation.
- Keyboard, focus, screen-reader, zoom, reflow, content, form, error, motion, media, and task testing expose different barriers.
- Automated tools can find many programmatically detectable defects but cannot determine complete accessibility on their own.
- Each finding should record scope, environment, evidence, user impact, relevant requirement, reproduction steps, and verification criteria.
- Fix reusable components before isolated instances when the same defect appears across pages.
