Name repeated table actions with their row context

What to change

Ask for row actions to carry enough context to distinguish their targets while keeping the interface concise.

A worked example

Illustrative example

A View action is identified as View reception contact request, using the row's appropriate public or test identifier so it can be distinguished from neighbouring actions.

How to check the result

Accept when each repeated action has an unambiguous target and opening one never affects a different row.

A mistake to avoid

Appending only the visual row number becomes unreliable when sorting, filtering or pagination changes the row's position.

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 recordOpen the control or link list with a screen reader and compare repeated row actions. Check whether each one identifies the relevant record or item.Activate a middle row's action using the keyboard, then return. Ask the supplier to demonstrate a useful return position in the same table.Inspect rows with similar names and narrow-screen versions. The identifying context should remain sufficient and should not become an excessively long spoken label.

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.