Skip to content

Make accessibility manageable. Request access

Sign in

Resources

Use the right kind of testing for the question.

Automated accessibility testing applies programmed checks to content. Manual evaluation uses human judgment to examine the experience. They contribute different evidence, and a complete evaluation needs more than an automated scan.

What question are you trying to answer?

Each question, and a useful starting approach.

  • Is a detectable rule failure present in evaluated content?

    Applicable automated check

  • Does the wording convey the intended meaning?

    Human review in context

  • Can someone complete an important task by keyboard?

    Keyboard interaction testing

  • Does an interaction work with a screen reader?

    Evaluation with relevant assistive technology

  • Did a fix address the original barrier?

    Retest the original failure and relevant interactions

The method depends on the issue and the experience being evaluated. Keep the tested pages, states, and limitations with the result.

Give automation a repeatable job.

Use repeated checks to investigate detectable issues across the configured website scope. The results can inform where the team should look next and which work needs ownership.

Give human evaluation a clear scope.

Choose important tasks and relevant variations. Record what the evaluator attempted, what happened, and which barriers need follow-up. Human evaluation may include keyboard and assistive-technology testing as well as review of content and interaction design.

Illustrative scenario.

Example: a form label and an error message.

An automated check identifies a field without a programmatic label. After correcting the association, the team also reviews the visible wording and attempts to recover from an invalid submission. The label check and the error-recovery task answer different questions.

Read the worked remediation example

Where Ility fits.

Ility supports full-site scanning, monitoring, and the issue workflow around remediation. Plan qualified human evaluation alongside those checks and record its outcomes using your team’s supported process.

Questions teams ask

Still have questions?

Tell us about your website and what you need. We'll follow up personally.

Request access

No. It reports the results of the tests performed within their evaluated scope. Human evaluation is needed to assess aspects automation cannot determine.

Plan evaluation based on the changes, user journeys, and risks your team needs to investigate. Repeated automated checks provide useful continuity; the team defines when deeper human evaluation is needed.

Plan the next check around the barrier.

Explore verification, or discuss how your testing and issue workflow could fit with Ility.