Check that custom shortcuts do not hijack typing

What to change

Ask the supplier to identify custom shortcuts and provide an appropriate way to avoid accidental activation where the interaction requires it.

A worked example

Illustrative example

Pressing a letter while writing an enquiry inserts that letter. It does not open a search panel or move to another section of the page.

How to check the result

Accept when custom shortcuts do not interfere with text entry and users have a practical route to avoid conflicts in supported interactions.

A mistake to avoid

Documenting a shortcut in help does not make accidental activation harmless or ensure visitors can discover how to turn it off.

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 recordObtain the shortcut list and try each key while focus is in text fields, search boxes and editable message areas. Record any unexpected action.Test normal reading with a screen reader and any supported speech input workflow. Ask the supplier to explain conflicts and the available adjustment or disabling control.Disable or reconfigure the shortcuts if that option exists, then repeat. The normal visible controls should still provide every essential function.

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.