Aglet

Verify a repaired primary action across user paths

Verification should replay the task that failed and check the action from entry through completion. Confirm semantics and visible behavior together, including validation recovery and narrow layouts where the original issue appeared.

Check whether the outcome improved

  1. Replay the blocked mode

    Use the same role, page state, interaction mode, viewport, zoom, and action sequence from triage. Record whether focus, name, enabled state, and form association now support the intended task.

  2. Check recovery states

    Trigger validation, loading, disabled, success, and return states that can change action availability. Confirm users receive a clear next step and do not lose entered information while recovering.

  3. Compare the ordinary path

    Complete the task with the default pointer or touch path and inspect the resulting state. Apply the evidence rule and keep verification qualified if any original interaction mode remains untested.

What to carry forward

Verification should say accessible across reviewed modes, partially covered, still blocked, or inconclusive. Close only when the primary task completes from the original entry state and the repaired control remains usable through recovery states. Complete the task with keyboard-only navigation, enlarged text or zoom, and an assistive technology check where available; confirm focus and errors remain understandable after submission.

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