Skip to content
Design Academy My progress

Template

Accessibility audit checklist

A manual review based on common WCAG 2.2 requirements, to use alongside automated tools.

Accessibility audit checklist

Page / flow: Date: Auditor: Tools used: (automated checker, screen reader, browser zoom)

This checklist covers frequent issues; it is not a full WCAG conformance review. Automated tools find only part of the problems. Passing them does not make a design accessible.

Perceivable

  • Body text contrast at least 4.5:1; large text at least 3:1 (WCAG 1.4.3)
  • Icons, input borders and focus indicators at least 3:1 against adjacent colours (1.4.11)
  • Information is never conveyed by colour alone (1.4.1)
  • Meaningful images have alt text; decorative images are hidden from assistive tech (1.1.1)
  • Video has captions; audio has transcripts (1.2)
  • Content works at 200% zoom and reflows at 320 CSS pixels wide without horizontal scrolling (1.4.4, 1.4.10)
  • Text spacing can be increased without loss of content (1.4.12)

Operable

  • Everything works with a keyboard alone (2.1.1)
  • No keyboard traps (2.1.2)
  • Focus order follows a logical reading order (2.4.3)
  • Focus is always visible (2.4.7) and not hidden behind sticky elements (2.4.11)
  • A skip link or landmarks allow skipping repeated navigation (2.4.1)
  • Pages have descriptive titles (2.4.2)
  • Link text makes sense out of context (2.4.4)
  • Targets are at least 24 by 24 CSS pixels or adequately spaced (2.5.8)
  • Anything done by dragging also works with a single pointer (2.5.7)
  • Motion can be paused or is reduced when the user prefers reduced motion

Understandable

  • Page language is set (3.1.1)
  • Form fields have visible labels and instructions (3.3.2)
  • Errors are identified in text and explain how to fix them (3.3.1, 3.3.3)
  • Navigation is consistent across pages (3.2.3)
  • Users are not asked to re-enter information already provided in the same process (3.3.7)

Robust

  • Headings form a logical outline (h1, then h2, then h3)
  • Buttons are buttons and links are links
  • Custom controls have accessible names, roles and states (4.1.2)
  • Status messages are announced without moving focus (4.1.3)

Screen reader spot check

  • The main task can be completed with a screen reader (VoiceOver, NVDA or TalkBack)

Issues found

#IssueWhereWCAG criterionSeverityRecommendation
1
View the Markdown source
# Accessibility audit checklist

**Page / flow:**
**Date:**
**Auditor:**
**Tools used:** (automated checker, screen reader, browser zoom)

> This checklist covers frequent issues; it is not a full WCAG conformance review. Automated tools find only part of the problems. Passing them does not make a design accessible.

## Perceivable
- [ ] Body text contrast at least 4.5:1; large text at least 3:1 (WCAG 1.4.3)
- [ ] Icons, input borders and focus indicators at least 3:1 against adjacent colours (1.4.11)
- [ ] Information is never conveyed by colour alone (1.4.1)
- [ ] Meaningful images have alt text; decorative images are hidden from assistive tech (1.1.1)
- [ ] Video has captions; audio has transcripts (1.2)
- [ ] Content works at 200% zoom and reflows at 320 CSS pixels wide without horizontal scrolling (1.4.4, 1.4.10)
- [ ] Text spacing can be increased without loss of content (1.4.12)

## Operable
- [ ] Everything works with a keyboard alone (2.1.1)
- [ ] No keyboard traps (2.1.2)
- [ ] Focus order follows a logical reading order (2.4.3)
- [ ] Focus is always visible (2.4.7) and not hidden behind sticky elements (2.4.11)
- [ ] A skip link or landmarks allow skipping repeated navigation (2.4.1)
- [ ] Pages have descriptive titles (2.4.2)
- [ ] Link text makes sense out of context (2.4.4)
- [ ] Targets are at least 24 by 24 CSS pixels or adequately spaced (2.5.8)
- [ ] Anything done by dragging also works with a single pointer (2.5.7)
- [ ] Motion can be paused or is reduced when the user prefers reduced motion

## Understandable
- [ ] Page language is set (3.1.1)
- [ ] Form fields have visible labels and instructions (3.3.2)
- [ ] Errors are identified in text and explain how to fix them (3.3.1, 3.3.3)
- [ ] Navigation is consistent across pages (3.2.3)
- [ ] Users are not asked to re-enter information already provided in the same process (3.3.7)

## Robust
- [ ] Headings form a logical outline (h1, then h2, then h3)
- [ ] Buttons are buttons and links are links
- [ ] Custom controls have accessible names, roles and states (4.1.2)
- [ ] Status messages are announced without moving focus (4.1.3)

## Screen reader spot check
- [ ] The main task can be completed with a screen reader (VoiceOver, NVDA or TalkBack)

## Issues found
| # | Issue | Where | WCAG criterion | Severity | Recommendation |
|---|---|---|---|---|---|
| 1 | | | | | |

All templates