Aglet

Investigate notification badge meaning from count to destination

An investigation should show what the badge represents and whether the shell communicates that meaning to visual and assistive technology users. Replay zero and nonzero states, compare item and group counts, and inspect the destination. Keep numeric correctness separate from semantic clarity.

Build a useful investigation brief

  1. Build the meaning table

    List badge value, count source, unread and grouped records, icon label, navigation text, zero behavior, destination, and filter. Include one unrelated metric for comparison. Record what a person could infer before activation.

  2. Trace activation

    Open the indicator with one and several unread records, then with none. Compare destination heading, filters, list contents, status message, and return path. Record whether a count remains visible when its destination is filtered or empty.

  3. Write the semantics brief

    State first mismatch, affected surfaces, and competing explanations such as count definition, label, or destination. Recommend one bounded copy or count experiment with a pass condition. Do not rely on color or icon shape as the sole meaning.

What to carry forward

The investigation is complete when count, accessible name, zero state, and destination form a reproducible semantic contract, or the first unknown is explicit. Stop with one bounded experiment. Keep visual and text-equivalent communication aligned in the brief.

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