Aglet

Triage an inaccessible primary action in a workflow

An inaccessible primary action turns an available workflow into a dead end for part of the audience. Start with the user’s intended task and record where progress stops across pointer, keyboard, zoom, or assistive interaction without assuming the cause.

Establish what is happening

  1. Name the task path

    Record page, state, role, expected action, and the control label users were given. Preserve the sequence from entry to failure and note whether the action is visible, enabled, discoverable, and associated with the right content.

  2. Compare interaction modes

    Check the same path with pointer, keyboard, enlarged text, and an available assistive technology or semantic inspection. Record the first difference, such as focus order, hidden control, clipped label, or unclear state.

  3. Bound the blocked outcome

    Describe whether users can complete the task another way, lose entered work, or remain stuck. Separate a discoverability problem from an action that cannot be activated at all.

What to carry forward

Triage should state the task, entry point, blocked interaction mode, first stopping point, and user consequence. Escalate when the primary path has no dependable alternative; otherwise capture a scoped usability gap for prioritization. Describe the task a user cannot complete and the interaction mode involved, then capture focus order, accessible name, visible state, and any error or recovery message.

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