Access for All

Accessibility Audit Checklist

Quick 10-Minute Accessibility Check

Use this checklist to carry out a basic accessibility audit. Tick each item as you review your website, document, app or digital service.

  • Can you use the whole page with only a keyboard?

  • Is the keyboard focus clearly visible?

  • Do all images have suitable alt text?

  • Is text readable with sufficient colour contrast?

  • Are videos captioned?

  • Are forms labelled properly?

  • Can the page be zoomed to 200%?

  • Does the page have a logical heading structure?

  • Does the site work with a screen reader?

  • Have you tested with a real user if possible?

Accessibility Checklist

Use this checklist to carry out a basic accessibility audit. Tick each item as you review your website, document, app or digital service.

How to Use This Checklist

For the best results, combine:

  • Automated testing tools (for example WAVE, axe or Lighthouse)

  • Manual keyboard-only testing

  • Screen reader testing

  • Real user testing with disabled users where possible

Suggested testing tools:

  • WAVE

  • axe DevTools

  • Lighthouse

  • WebAIM Contrast Checker

  • NVDA or JAWS screen readers

  • VoiceOver (Mac/iPhone)

1. Perceivable

  • Information and interface elements can be seen or heard

  • Images and Non-Text Content

  • Every meaningful image has clear, descriptive alt text.

  • Decorative images have empty alt text (alt="").

  • Icons and buttons with images have accessible labels.

  • Charts, graphs and infographics include a text alternative or summary.

  • CAPTCHAs have an accessible alternative.

Multimedia

  • Videos include accurate captions.

  • Audio-only content includes a transcript.

  • Video content includes a transcript or audio description where needed.

  • Media does not autoplay, or users can pause and stop it.

Colour and Contrast

  • Normal text has a contrast ratio of at least 4.5:1.

  • Large text has a contrast ratio of at least 3:1.

  • Buttons, form fields and other interface elements have a contrast ratio of at least 3:1.

  • Information is not communicated by colour alone.

  • Links are identifiable without relying only on colour (for example underlined links).

Text, Layout and Zoom

  • Text can be resized to 200% without loss of content or functionality.

  • The page works properly when zoomed to 400%.

  • Content reflows correctly on mobile devices and small screens.

  • Users can adjust text spacing without breaking the layout.

  • Page orientation is not restricted to only portrait or landscape unless essential.

2. Operable

Users can navigate and interact with the interface

Keyboard Accessibility

  • All links, buttons, menus and form controls can be used with a keyboard only.

  • Users can move through the page in a logical order using Tab.

  • No keyboard trap prevents users from moving away from an element.

  • Dropdowns, pop-ups and modal windows can be opened and closed by keyboard.

  • Drag-and-drop actions have an alternative method.

Focus and Navigation

  • A visible focus indicator appears on every interactive element.

  • The focus indicator is not hidden or obscured.

  • Focus order matches the visual order of the page.

  • A ‘Skip to main content’ link is available.

  • Repeated navigation can be bypassed.

  • Page titles clearly describe the page.

Links and Buttons

  • Link text makes sense on its own.

  • Buttons clearly describe what they do.

  • There are no vague links such as ‘Click here’ or ‘Read more’ without context.

  • Touch targets and buttons are large enough to select easily.

Timing and Motion

  • Users can pause, stop or extend time limits.

  • Content does not flash more than 3 times per second.

  • Animations can be reduced or turned off.

  • Motion is not required to complete a task.

3. Understandable

Content and interaction are clear and predictable

Language and Readability

  • The page language is set correctly in the HTML.

  • Any change in language within the content is identified.

  • Content uses plain English and avoids unnecessary jargon.

  • Instructions are clear and easy to follow.

Structure

  • Pages have one clear H1 heading.

  • Headings follow a logical order (H1, H2, H3 and so on).

  • Lists are marked up correctly.

  • Tables are used only for data, not layout.

  • Data tables include headings and are easy to understand.

Forms

  • Every form field has a visible label.

  • Required fields are clearly identified.

  • Instructions are provided before the user starts typing.

  • Error messages explain what is wrong and how to fix it.

  • Errors are announced to screen reader users.

  • Users can review and correct important information before submitting.

  • Form fields use the correct autocomplete purpose where possible.

Predictability

  • Navigation is consistent across pages.

  • Components behave consistently.

  • Links do not open new windows unexpectedly.

  • Changing a form field does not trigger an unexpected action.

4. Robust

Content works with assistive technology and different devices

Code and Compatibility

  • HTML is valid and semantic.

  • Landmarks are used correctly (header, nav, main, footer).

  • ARIA is only used where needed and is implemented correctly.

  • Custom controls expose names, roles and states to assistive technology.

  • Status messages are announced to screen readers.

Screen Reader Testing

  • The site has been tested with NVDA, JAWS or VoiceOver.

  • All page content is announced in the correct order.

  • Form fields, buttons and links are announced clearly.

  • Dynamic content updates are announced correctly.

Cross-Device Testing

  • The site works on desktop, tablet and mobile.

  • The site works in more than one browser.

  • Accessibility features remain available in responsive layouts.