Decide where the work belongs
Rank task consequence
Describe whether the blocked action prevents saving, continuing, recovering, reviewing, or only discovering an optional feature. Give higher priority to work that strands entered information or a required workflow.
Rank affected modes
Record which pointer, keyboard, zoom, viewport, or assistive paths fail and whether the failure is consistent. Do not infer population size from one report; preserve reachability evidence and unknowns.
Assess alternatives
Check whether an equivalent visible, semantic, and documented path works for the same user state. A workaround that requires a different role or hidden URL is weaker than a usable primary action.
What to carry forward
The queue decision should name the blocked task, affected modes, consequence, owner, and review point. Keep priority high when no equivalent path works or entered work is at risk; lower it only with evidence of a dependable alternative. Prioritize a blocked primary action in a repeated or consequential workflow, especially when keyboard, zoom, or assistive technology users lack the same completion path.
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