Build a useful investigation brief
Inspect the control contract
Record accessible name, role, state, form association, focus behavior, and surrounding instructions. Compare the control with the expected action and note whether the rendered structure matches the visible label.
Trace state transitions
Follow initial load, validation error, loading, disabled, success, and return states. Identify whether focus, visibility, or instructions change at a transition and whether the action remains associated with its form.
Compare layout boundaries
Review narrow width, zoom, reduced motion, and keyboard navigation where relevant. Check clipping, overlap, off-screen focus, sticky regions, and duplicate controls; preserve screenshots or semantic output as evidence.
What to carry forward
The brief should identify the first semantic, state, or layout boundary that blocks the action, affected modes, and reliable alternatives. Conclude a rendering defect, interaction-state defect, copy problem, or unresolved cause with confidence. Trace semantic markup, label association, focus management, disabled or hidden state, contrast, and event handling at the exact point where the action becomes unavailable.
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