Aglet

Verify notification badge meaning across zero and unread states

Verification should prove that the badge communicates unread notification state and leads to the records a person expects. Test zero and nonzero cases, grouped or filtered lists, and accessible names. Keep unrelated counts outside the badge claim. A count without a clear destination remains a weak signal.

Check whether the outcome improved

  1. Check zero and unread

    Inspect no-unread, one-unread, and several-unread states. Confirm badge, icon label, navigation text, destination heading, and list content agree. Record whether a zero indicator disappears or changes to explicit status by design.

  2. Check grouped context

    Review grouped or filtered notifications and compare count with destination. Ensure a person can tell whether the number counts items or groups. Test opening and returning so the indicator does not imply a different list.

  3. Review text equivalence

    Inspect accessible name, status message, narrow layout, and users who do not see visual badges. State tested count definitions and omitted platform behavior. Leave a partial pass if one destination or filter remains unobserved. Check that the destination exposes the same unread definition.

What to carry forward

Verification passes when badge meaning, accessible text, zero behavior, and destination agree across tested states. If grouping or platform behavior is partial, document it. A visually obvious number is not a passing semantic contract when its destination surprises.

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