Aglet

Verify notification badge counts against unread records

Verification should prove that the badge communicates the same unread meaning as the inbox and updates after the defined transition. Test item and group views, read actions, filtering, and another surface. Keep platform badge presentation separate from the in-app count contract.

Check whether the outcome improved

  1. Check the unread baseline

    Open a list with known unread records and compare badge, group totals, and visible rows. Record the count definition and filter. Include zero unread so the empty indicator is intentional.

  2. Check a read transition

    Open or explicitly mark one item read according to the contract, then refresh another tab or device. Confirm badge, list, group, and status update within the defined boundary. Record any expected delay.

  3. Review filters and copy

    Inspect filtered list, direct link, narrow layout, accessible name, and status message. State tested grouping and sync paths. Leave a partial pass when cross-device or platform badge behavior is outside observation. Record the exact transition that made the count agree.

What to carry forward

Verification passes when badge, unread records, grouping, and defined transitions agree across tested surfaces. If sync or platform presentation is partial, document it. A count that matches only after a manual refresh is not a pass unless refresh is the contract.

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