The playbook
Web Accessibility: Metrics and Measurement
Measure web accessibility by defining resolved barriers in critical journeys precisely enough that two people can reproduce the result from the same records. Keep the reporting unit, date basis, and scope visible. Without those definitions, a change in the report may reflect a changed calculation rather than a changed customer outcome.
Put the task in context
A visible field label, a specific error message, and a clearly visible keyboard focus can materially improve a form journey. Check the order of focus and whether controls have understandable names. Automated testing can identify some issues but does not replace trying the task.
Create a metric definition
| Definition field | What it must explain |
|---|---|
| Measure | resolved barriers in critical journeys |
| Unit | What one page or interaction record or completed outcome represents |
| Included records | The scope identified by component and barrier |
| Date basis | The event date or period used to include a record |
| Exclusions | Tests, duplicates, or other records outside the agreed definition |
| Source owner | site owner |
Separate delivery checks from outcome measures
A delivery check asks whether the team completed a specific task, such as check keyboard access focus and meaningful labels. An outcome measure asks what happened for the user or business afterward. Keep both visible. Completing the task is useful evidence of execution, but it does not by itself prove that the broader outcome improved.
Worked arithmetic example
Suppose an illustrative review includes 80 eligible records, and 60 satisfy the explicitly defined completion condition. The completion share is 60 ÷ 80 × 100 = 75%. This is hypothetical arithmetic, not an industry benchmark or a predicted improvement. It describes only the population and condition you defined.
For web accessibility, explain the condition before applying that calculation. If the question is whether the team can test forms errors and complete user journeys, a record counts only when the evidence demonstrates that condition. Do not replace missing outcomes with successful ones just to complete a report.
Compare like with like
Keep the scope, date basis, and exclusions consistent between observations. If barrier changes meaning between periods, note the change and rebuild a comparable view where possible. A rate can also move because the composition of the underlying group changed, even when individual performance did not.
Investigate an unexpected result
- Check whether the underlying component records are complete.
- Look for this known failure: assuming an automated score proves every interaction is accessible.
- Verify that the process still includes: provide text alternatives and readable contrast.
- Reconcile a sample with the original record before changing the operating plan.
Use the report to choose an action
If the evidence supports a correction, combine automated checks with manual keyboard and assistive-technology testing. Record when the change occurred and what should be checked next. Keep uncertainty visible when the sample is small or the observation period is incomplete. The purpose of measurement is a better decision about resolved barriers in critical journeys, not a favorable-looking number.
Use realistic content lengths and assets during review. Short placeholder headings can conceal overflow and hierarchy problems that appear with real service names, prices, or instructions. Check the result after the final content is inserted.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now