Accessibility Testing Methods

Accessibility testing checks how well a website works for people with disabilities. Software checks help, but knowledgeable people must also evaluate the site and involve users with disabilities. Add a manual keyboard check to your next review.

Accessibility evaluation means assessing a website for accessibility problems. W3C guidance recommends evaluating early and throughout development, when problems are easier to address. Evaluation tools are software programs or services that help with this work, but no tool alone can determine whether a site meets accessibility standards. Knowledgeable human evaluation is required. [1]

Build a review plan that combines tools with human judgment and user involvement. Tool results provide information for evaluators to consider; an empty error report does not establish accessibility. The overview offers guidance on choosing tools for your situation and does not prescribe one testing method that must always come first. [1]

Suggested activities for your plan include manual keyboard checks and assistive technology checks. Here, assistive technology means access tools used by people with disabilities. Include people with relevant experience when planning these activities. These are proposed review activities: the supplied overview supports knowledgeable evaluation but does not provide detailed procedures for keyboard or assistive technology checks.

For a hypothetical example, imagine that a tool reports no errors in a checkout, but a participant using a screen reader—an access tool—reports confusing information. Involve that participant in reviewing the experience, record the problem, and evaluate the revised checkout. This example illustrates how user feedback can inform a review; it is not a reported study or evidence that only user testing could find the problem.

Choose activities around the project and the skills available, and involve people with disabilities throughout development. This plan assumes evaluators have relevant knowledge and participants can contribute experience of using the site. Treat evaluation as ongoing work: neither one tool result nor one participant's experience establishes accessibility for everyone. W3C provides planning resources and guidance on combining expertise and involving users. [1]

• Guidance: W3C recommends evaluating accessibility early and throughout development so problems can be identified when they are easier to address. This is official guidance, not a reported experimental finding. [1]
• Guidance: Evaluation tools help assess accessibility, but no tool alone can determine whether a site meets accessibility standards. Knowledgeable human evaluation is required. [1]
• Guidance: The overview recommends involving the right people and skills and links to guidance on including people with disabilities in evaluation throughout project development. [1]
• Guidance: The WCAG-EM Report Tool helps evaluators follow a methodology and generate reports from their input; it does not perform the checking for them. [1]

The supplied overview provides planning guidance, not empirical findings about detection rates or product superiority. It does not prescribe a universal testing order or detailed keyboard and assistive technology procedures. The checkout example and suggested review activities are instructional illustrations. The overview supports no coverage percentage or legal-compliance guarantee, and a clean tool report cannot establish accessibility.