Aglet

Triage Accessibility in Product Discovery

Accessibility is part of the problem space from the first research question. Triage whether the study includes people who use assistive technology, need accommodations, or have lower digital confidence. Record barriers as evidence gaps, not as participant defects or afterthoughts.

Establish what is happening

  1. Name access contexts

    List the tasks, devices, assistive technologies, language needs, motor, sensory, cognitive, and digital skill contexts relevant to the outcome. Identify who is missing and which barriers a standard session could hide.

  2. Review study access

    Inspect recruitment, consent, materials, scheduling, prototype interaction, and note-taking for access barriers. Record adaptations and whether they preserve the question. Separate inability to use the study setup from inability to use the product.

  3. Bound the evidence gap

    State which findings include disabled or assisted paths and which do not. Identify a barrier requiring another study and the decision it could change. Keep claims scoped to the access contexts actually observed.

What to carry forward

The triage output is an accessibility evidence map with relevant contexts, study barriers, adaptations, and open questions. Stop when the team can see whose experience is missing. Keep findings provisional when access arrangements prevented a fair task or excluded an important context needed for the decision.

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