Decide where the work belongs
Name the blocked action
Describe whether a person cannot reach a suggestion, cannot dismiss it, or submits text they did not choose. Compare keyboard, touch, and screen reader paths. Keep a visual-only inconsistency separate from an action that changes the result set.
Compare repair sizes
Set focus management, active option semantics, explicit labels, acceptance behavior, and dismissal rules beside one another. Consider whether a change fixes one key without breaking pointer selection. Prefer a small contract that preserves editable text and user control.
Choose the queue move
Set owner, input methods in scope, and a revisit trigger such as a failed keyboard journey. Preserve the key trace and expected value. Decide whether the next step is markup, interaction logic, copy, or a focused accessibility review.
What to carry forward
Prioritize the smallest change that prevents an unintended query or makes the full selection path usable. The decision should name input methods, consequence, and pass condition. If the contract itself is unsettled, queue the interaction decision before a broad implementation change.
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