Accessibility & Standards
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:
min
19.11.2026

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.
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
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
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
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.
For more on implementation, see Accessible forms – which decisions really matter.
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