Aglet

Investigate autocomplete keyboard selection with an event trace

An investigation should show where keyboard selection diverges from the intended query. Recreate the same prefix, inspect focus and active-option state after each event, and compare the value submitted with the value announced. Keep a pointer path as a control rather than treating it as equivalent.

Build a useful investigation brief

  1. Build the event table

    For one prefix, record input value, popup visibility, active option, focus, aria state, and result query after every key. Include Down, Up, Enter, Escape, Tab, and continued typing. Note what happens when the list closes between keystrokes.

  2. Vary one interaction

    Hold the markup and prefix fixed while changing one key sequence or selection method. Compare automatic highlight with manual selection and dismissal. Record whether a value change is visible, announced, and reversible; a hidden mutation is a separate finding from lost focus.

  3. Write the interaction brief

    State the first divergent event, affected input method, and competing explanations such as focus ownership or commit logic. Link the event trace and propose one bounded experiment. Do not infer assistive-technology behavior from color alone when semantic state is available.

What to carry forward

The investigation is complete when the first divergent event and resulting query are reproducible, with semantic and visual evidence aligned. Stop with one bounded interaction experiment or an explicit support gap. Keep a successful pointer or literal-submit path as a control for later verification.

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