Keep the lesson for the next incident
Keep the event boundary
Record prefix, key sequence, popup state, active option, committed value, and result query. Note which state a person could see or hear. This keeps the lesson tied to a real interaction rather than a preference about keyboard style.
Compare later paths
Review different prefix lengths, no-match states, narrow layouts, and a second input method after the change. Look for the same divergence under another suggestion count. Preserve a working control so the lesson does not imply every list behaves alike.
Add one interaction check
Require a keyboard acceptance, Escape dismissal, continued typing, and result-state assertion in future reviews. Assign ownership and revisit date. Define the observation that would show the check prevented a silent commit or an inaccessible focus transition.
What to carry forward
The learning record should connect one keyboard failure to a repeatable event-state check. Stop when another reviewer can apply it to a new autocomplete list and inspect the submitted value. Carry forward uncertainty where assistive-technology coverage remains incomplete.
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