Skip to content
Arbor

Website accessibility audit checklist

Use this checklist to plan an audit, test whole user journeys and document findings your team can reproduce.

1. Set the scope

  • Record the website or app, build or revision, WCAG version and conformance level, and any exclusions.
  • Pick representative templates and shared components such as navigation, dialogs and forms.
  • Choose tasks that matter to users, such as creating an account or getting from a product page to order confirmation. Include errors and recovery paths.
  • Record the browsers, devices and assistive technology you will use. Arrange authorized access and test accounts for any pages behind a login.

The W3C website accessibility evaluation methodology describes how to select and report a representative sample.

2. Run the checks

  • Keyboard. Use Tab, Shift+Tab, Enter, Space and Escape as appropriate. Watch focus at every step, especially when opening or closing menus and dialogs. Check that a sticky header never fully hides the focused control.
  • Screen reader. Check headings, landmarks, form labels, expanded and collapsed controls, errors and status changes. Listen for the same information a sighted visitor gets from the screen.
  • Zoom, reflow and contrast. Check text at 200% and test at a width of 320 CSS pixels. Make sure ordinary content can be read without scrolling in two directions. For ordinary text, check the WCAG AA minimum contrast ratio of 4.5 to 1, subject to the criterion’s exceptions.
  • Forms. Submit with missing or invalid values. Verify that the error identifies the field, explains what to fix and is discoverable by keyboard and screen reader.
  • Images, video and touch. Check that image alternatives convey the relevant information, captions match the speech and meaningful sounds, and touch controls can be used without precise gestures when WCAG requires an alternative.
  • Automated checks. Scan representative pages and states. Review each finding in context and record the tests that still require manual evidence.

Use the full WCAG 2.2 criteria for a conformance evaluation. The WCAG testing tools guide covers tools for each stage.

3. Write the accessibility audit report

Open with the scope, dates, test environments, results and priority fixes. Give each issue an identifier, the places it occurred, the affected users, the relevant criterion, and clear steps to reproduce it. Group repeated issues by component while preserving the affected page list.

Example finding for a checkout flow

  • Issue A-014. The street address field is highlighted after submission but the page provides no text explaining the error.
  • Steps. Open checkout, leave the street address blank and activate Continue. Inspect the message and listen with NVDA and Firefox.
  • Impact and criterion. A shopper who cannot see the highlighted border may be unable to identify why checkout stopped. This fails WCAG 3.3.1 Error Identification (Level A).
  • Fix and re-test. Show an error message beside the field and associate it with the input. Repeat the same task with keyboard and screen reader and verify that the message explains what to correct.

4. Verify fixes

Reproduce the original task using the same environment. Then test a second page that uses the same component. Record the date, build and result, and link to the new evidence. If the fix changes focus or the order of a flow, test adjacent steps as well.

See how Arbor tests or explore its website accessibility audit services if you need a scoped review and a report.

Need a second set of eyes?

Send a public page or flow to help us understand what you need tested.

Contact Arbor