Aglet

Verify Accessibility Evidence Before Product Decisions

Verification asks whether the study can support an accessibility claim within its actual scope. Review participant inclusion, research setup, task behavior, and evidence language. A narrow result can still be useful when the boundary is explicit and the next gap has an owner.

Check whether the outcome improved

  1. Set inclusion checks

    List access contexts, participant support, task adaptations, consent needs, and evidence markers required by the question. Add a check that the session setup itself does not create the barrier being attributed to the product.

  2. Review access evidence

    Compare observed task paths, participant explanations, recovery, and successful alternatives. Include different devices or input modes when the decision depends on them. Record absent contexts and accommodations that changed the evidence.

  3. State the safe scope

    Decide whether the evidence supports a design change, another study, or a scoped finding. Record what was not tested and a review owner. Avoid a broad accessibility statement when only one path or assistive technology was observed.

What to carry forward

The verification record should show inclusion checks, setup, access context, task evidence, adaptations, and scope. Use the conclusion only for observed contexts. Keep a follow-up when an untested barrier could affect independent completion or recovery.

Technical background: GOV.UK user research guidance.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow