Aglet

Verify autocomplete suggestions across prefixes and devices

Verification should show that suggestions support the typed search rather than replacing it unexpectedly. Test short and specific prefixes, accept and edit options, and inspect narrow rendering. Confirm that a useful recent or category suggestion remains understandable and dismissible. The result should make both acceptance and dismissal easy to recognize.

Check whether the outcome improved

  1. Check prefix relevance

    Type representative prefixes and compare the list with the accepted query or product result. Confirm suggestion labels identify product, category, or recent-search behavior. Record no-list and one-list states so the empty transition is intentional.

  2. Check acceptance and editing

    Select with pointer or keyboard, continue typing, press Escape, and submit the literal prefix. Verify the chosen suggestion is committed only when intended and that a person can remove or replace it without losing their text.

  3. Review narrow behavior

    Inspect the list at a narrow width and with zoom or assistive technology semantics where available. Ensure the popup does not obscure the field or clip the meaning. Limit the closure record to tested prefixes, sources, and device paths.

What to carry forward

Verification passes when suggestions follow the typed intent, selection is intentional, and non-query suggestions are clearly labeled and dismissible. If one source or device path is untested, keep it outside the claim. A visually attractive list is not evidence of useful autocomplete.

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