Keep visible button wording aligned with its spoken name

What to change

Ask the supplier to keep visible text within the accessible name, adding context only where it helps distinguish the action.

A worked example

Illustrative example

A visible Search button is announced as Search services. The visible word remains part of its name while the extra context distinguishes its purpose.

How to check the result

Accept when visual, spoken and voice-command identification agree on the control and its action across interface variants.

A mistake to avoid

Adding a long hidden marketing sentence to a short button can obscure its purpose and make voice interaction less predictable.

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 recordSelect controls with visible labels and compare them with their announced names. Include responsive versions that replace words with icons.Use the visible wording in a speech command where testing support is available. Record controls that cannot be selected reliably by what the visitor can see.Ask the supplier to inspect repeated controls with added context. Their labels should remain concise and describe the same action rather than a different destination.

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.