Web Accessibility Audit

Design Systems & Engineering • UX & Product Architecture

A web accessibility audit is a documented evaluation of a website or web app against a defined accessibility standard and scope. It identifies barriers, records how they were found, and gives teams evidence they can use to prioritize fixes and verify changes.

How do you run a web accessibility audit?

  1. Define the scope and target. Record the site or release, WCAG version and level or other applicable standard, and the browsers and assistive technologies used for testing.
  2. Sample representative content and complete tasks. Include common templates, shared components, different states, and critical journeys such as checkout. If a sampled page is part of a process, include the steps needed to complete that process.
  3. Combine automated and manual tests. Use scans for issues they can identify. Test keyboard operation, focus order, zoom and reflow, labels, errors, and announcements by hand. Include people with disabilities in usability evaluation to understand how barriers affect real tasks.
  4. Report and retest. Record the affected page or state, environment, steps to reproduce, expected behavior, actual result, user impact, and applicable criterion. Retest the fix across other instances of a shared component.

Example: A keyboard trap during checkout

Evidence Example finding
Location and test Checkout, payment-help dialog. Open it by keyboard and try to close it with the available controls.
Actual result and impact Focus stays inside the dialog. The visible close icon only responds to pointer input, so a keyboard user cannot return to payment.
Criterion and fix WCAG 2.1.2 No Keyboard Trap (Level A). Make the close control keyboard-operable and verify that focus returns to the trigger when the dialog closes.

The report should identify what the sample covers and any areas that remain untested. A short check of one page can uncover barriers. A conformance evaluation requires a broader review of the defined scope.

Sources