Aglet

Verify zero-query discovery across first-use contexts

Verification should show that a person understands the search scope and can start with or without guidance. Test first-use and returning states, then inspect examples, history, focus, and the ability to replace or dismiss a cue without losing the blank query.

Check whether the outcome improved

  1. Check first use

    Open the blank state without history and confirm scope, label, focus, examples, and first action are understandable. Choose an example and type a literal query. Record whether the result context follows the entry point.

  2. Check returning context

    Repeat with available history or category entry. Confirm recent terms are relevant to the person’s own context, can be replaced, and do not appear where history is unavailable. Keep static guidance understandable without personalization.

  3. Review the empty fallback

    Clear the query, use browser back, and inspect a narrow layout. Verify the person can start again and that no option claims unsupported popularity. Limit the closure to the contexts tested and preserve an omitted history branch.

What to carry forward

Verification passes when blank and guided states explain scope, support a first useful action, and preserve user control across contexts. If history or personalization is not tested, state that boundary. A populated zero-query view is not a pass if its options cannot be understood.

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