Aglet

Prioritize notification read-state clarity with reversible cues

Read-state work matters when opening a notification removes it from attention before the task is understood or leaves a person unsure whether it was acknowledged. Compare state transition, visual cue, badge, and recovery. A reversible mark action may be safer than changing automatic behavior broadly.

Decide where the work belongs

  1. Name the missed-work risk

    Describe what disappears from the unread queue and whether the person has completed the underlying task. Compare focus, open, dismiss, and explicit mark actions. Keep visual styling separate from a state mutation that affects navigation.

  2. Compare transition choices

    Set view-to-read, explicit mark, task completion, temporary highlight, undo, and unchanged state beside one another. Consider keyboard and screen readers. Prefer a rule that preserves agency and makes the next state predictable.

  3. Choose a bounded move

    Record action, state, surface, owner, and revisit evidence. Decide whether to fix transition, add undo, clarify copy, or adjust badge mapping. Preserve the current path and one explicit control for comparison. Tie the queue choice to one named transition boundary.

What to carry forward

Prioritize read-state changes where unread work disappears before acknowledgment or state cues are contradictory. The decision should name transition and recovery. If state changes are intentional and clear, queue the specific badge or history issue instead.

Technical background: W3C 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