Aglet

Verify notification read state across open and mark actions

Verification should prove that the read state changes only at the defined action and that list, badge, and history agree afterward. Test passive viewing and explicit marking, then inspect keyboard, grouped, and return paths. Keep task completion outside the claim unless directly tested.

Check whether the outcome improved

  1. Check passive viewing

    Focus and open an unread item, then return without marking it. Confirm the defined state, visual cue, badge, and history. Record whether the product intentionally treats opening as read and how that choice is explained.

  2. Check explicit marking

    Mark an item read and unread or use undo where available. Confirm list, badge, grouped summary, and another surface update within the contract. Test a child notification so group state does not conceal an unread item.

  3. Review direct and keyboard paths

    Inspect direct link, keyboard focus, narrow layout, status message, and history. State tested surfaces and omitted sync cases. Leave a partial pass when cross-device update or task completion cannot be observed.

What to carry forward

Verification passes when defined actions produce consistent read state, recovery is understandable, and badges and history agree. If opening, grouping, or sync behavior is partial, document it. A changed row style is not a pass if the underlying unread record remains.

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