Avoid triggering actions before a tap is completed

What to change

Ask the supplier to use predictable activation behaviour and an appropriate way to cancel accidental pointer actions.

A worked example

Illustrative example

A visitor touches Send enquiry accidentally, slides away and releases outside the control. The unsent form remains available for deliberate submission.

How to check the result

Accept when ordinary actions support the expected cancellation gesture and consequential operations do not occur merely from an incidental touch.

A mistake to avoid

Disabling every touch interaction to prevent mistakes would also block intended use; the aim is a predictable activation boundary.

Your action checklist

Use these checks to prepare a discussion with your team or supplier. Tick a check when you have recorded the decision or evidence, rather than when a feature has simply been promised.

Decisions to recordIn a test environment, touch a control and move away before lifting your finger. Observe whether the action still occurs despite leaving its target.Repeat with ordinary links, secondary controls and the final form action. Ask the supplier to explain any control that intentionally responds before release.Use a mouse to press, move away and release as a comparison. Confirm behaviour remains understandable and does not generate duplicate activations.

Evidence, open questions and decisionsNext action and responsible role

Entries stay in this page and are not submitted to Kay & Co. Download your notes before leaving; the page does not save them.