Make Enter follow the intended form action

What to change

Agree the expected Enter behaviour for single-line fields, multiline messages and the final submission stage.

A worked example

Illustrative example

In contact details, Enter advances through validation to review. In the enquiry message box, Enter creates a paragraph without sending anything.

How to check the result

Accept when keyboard submission follows the same deliberate journey as the visible primary controls and cannot bypass required review.

A mistake to avoid

A blanket rule that disables Enter everywhere may prevent accidental submission but also makes ordinary keyboard interaction unnecessarily difficult.

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 recordOn each step, press Enter from an ordinary text field. Check that the action matches the intended next step and applies the same validation.Press Enter inside a multiline message. It should add a new line where that is the expected editing behaviour, without prematurely sending the request.Ask the supplier to test screens containing Back, Change and Continue controls together. Confirm no secondary action becomes the unintended default.

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.