How to Evaluate a Website Accessibility Audit Provider

Choose an accessibility audit provider by the clarity of the testing scope and the usefulness of the findings. A claim to be the best provider or a single automated score does not establish that people can use your website.

Agree on the scope

Identify the pages, templates and user journeys to be tested. Include navigation, forms, authentication where relevant, error states and important documents. Confirm which accessibility standard and conformance level the engagement will evaluate. These should be written into the scope rather than inferred from a general promise of compliance.

Ask about manual evaluation

Automated tools can identify some issues, but they cannot determine whether every interaction works for people with different access needs. Ask how the team evaluates keyboard use, focus behavior, labels, instructions, content order and assistive-technology interactions. Confirm the devices and browsers included in testing and the limitations of the sample.

The W3C evaluation tools overview explains why tools support, rather than replace, accessibility evaluation. Use the WCAG overview to understand the standards referenced in a proposal.

Request actionable findings

A useful issue includes the affected location, steps to reproduce it, the observed behavior, the impact on the user and a suggested repair. Ask for representative sample findings before purchasing an audit. Developers should be able to reproduce the problem without guessing which page or state the reviewer saw.

Separate audit, remediation and retesting

Confirm whether the price covers evaluation only, implementation support or code changes. After a repair, retest the affected journey and check that the change did not introduce another barrier. Content authors may also need guidance so future headings, links, images and documents remain usable.

Questions for your proposal

• Which pages and interaction states are included?
• Which manual methods and assistive technologies will be used?
• How will findings be prioritized and explained?
• Who implements repairs, and what does retesting include?
• Which parts of the website remain outside the evaluated scope?

An audit describes an evaluated scope at a point in time; it is not a blanket guarantee about every future change or legal obligation. For a scoped discussion, see our accessibility and WCAG services or contact the team.