Accessibility & Standards

Accessibility testing: When do you need a scan, a WCAG audit or inclusive user testing?

A scan finds issues that tools can detect. A WCAG audit checks agreed criteria. Inclusive user testing shows how people complete real tasks. An example form helps you choose.

Reading Time:

x

min

|

19.11.2026

Let's Talk

* Pflichtfelder

Thank you very much

... that you've reached out to UseTree.
Our team will be like this
with you as soon as possible
get in touch.

Write another message
Yikes! Something went wrong. Try again.
""

Author

Redaktion

Contributors

Sources

Subscribe newsletter

Vielen Dank für die Anmeldung zu unserem Newsletter!
Oops! Something went wrong while submitting the form.

An automated scan is useful for getting an initial overview and running recurring checks. A WCAG audit shows which agreed criteria a digital product meets and where action is needed. Inclusive user testing shows whether people with disabilities can understand and complete specific tasks independently. Which method you need depends on the decision you want to make.

‍

What does each testing method reveal?

Automated scan

A scan checks rules that software can evaluate. Depending on the tool and the page state being tested, it can detect issues such as form fields without a programmatically determinable label or certain colour contrast problems. It produces a list of findings that your team can review and check again after making changes.

Checking whether a label is clear, keyboard focus moves in a logical order or an error message helps someone complete a form requires human judgement. A scan with no findings therefore does not establish WCAG conformance. W3C guide to evaluation tools

WCAG audit

An audit assesses accessibility against agreed criteria, such as WCAG 2.2 at Level AA. Agree in advance which pages, components, states and complete user journeys the audit covers. The audit combines automated and manual checks, for example with a keyboard, a screen reader or a magnified view. The report documents the criteria, where issues occur, their impact and prioritised recommendations. Its findings apply to the documented scope. How UseTree carries out a WCAG audit

Inclusive user testing

People with disabilities work through realistic tasks, using their usual assistive tools where possible. You observe where participants pause, take a detour or abandon a task. This can show whether they understand a hint and what helps them continue after an error. The findings describe what happened in the situations you observed. To assess WCAG conformance, you also need to check against the criteria. W3C guide to involving users · How UseTree runs inclusive user tests

‍

One form, three different findings

Imagine you want to find out whether people can book an appointment online. In this fictional example, the three methods look at the same process from different perspectives.

  1. The scan flags a field with no programmatically associated label. Your team can fix the issue and check the change in the next scan.
  2. In the audit, manual keyboard testing shows that the calendar opens, but you need a mouse to select a date. The report documents the blocked step and the relevant WCAG criterion.
  3. In inclusive user testing, the screen reader correctly announces “Invalid date”. Participants still do not know which format the form expects and try several entries. A clear example beside the field could help them correct the error.

For more on implementation, see Accessible forms – which decisions really matter.

‍

Which method fits your next step?

  • You want to catch new technical issues early. Run scans when things change and add manual checks for critical user journeys.
  • You need a documented assessment before a relaunch or to plan improvements. Agree the criteria and scope of a WCAG audit. Retest significant fixes once they are in place.
  • You want to know whether people can complete an important task in practice. Plan inclusive user testing around specific tasks. Check first whether any known blockers would prevent participants from completing them and should be fixed beforehand.

For an important user journey, you can combine all three methods. Scans help you monitor changes, an audit reveals technical and design gaps, and user testing shows where people encounter barriers in practice. Digital accessibility at UseTree

Author

Mitwirkende

Quellen

Newsletter abonnieren

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.