Research Guides
Identify Research Controls Without Relying on Their Position
A research tutorial tells the reader to select “the round button on the right.” The instruction works for its author's screenshot, but it can become ambiguous when controls move, the page is read without sight or a different layout puts another button in that position.
This worksheet checks how help text identifies a control. It complements, rather than replaces, a review of the control's own label. The examples are fictional and do not describe an implemented Colquhoun.shop workflow.
1. Identify the control by more than appearance
W3C's Sensory Characteristics guidance says instructions should not rely solely on features such as shape, color, size, visual position, orientation or sound. It permits those cues as additional help when the information is also available another way. W3C: Understanding Sensory Characteristics
Do not respond by deleting every visual clue. Instead, make sure the instruction has an identifying reference that remains meaningful without that clue. A control's actual label is often a useful starting point.
2. Collect instructions from the whole task
Review onboarding text, help panels, error messages and documentation that accompany one bounded activity. Search for phrases such as “on the right,” “the circle” or “when you hear the sound,” then inspect each occurrence in context.
A text search produces candidates, not automatic failures. Some phrases describe content clearly in its reading order, while others leave the intended action uncertain. Keep the full sentence and the interface state with each observation.
3. Rewrite a fictional export instruction
Suppose a tutorial says, “Press the blue circle to save your source list.” The interface has a control visibly labeled “Export sources.” A clearer instruction is, “Select Export sources to save your source list.” If the visual cue genuinely helps, it can remain as supplementary information rather than the only identifier.
Verify the action as well as the wording. If selecting that control opens a format chooser instead of immediately saving a file, describe that next step accurately. Better identification should not preserve a misleading account of what the control does.
If two controls share the same label, add a meaningful section reference or ask the interface owner to resolve the ambiguity. Replacing one vague description with a duplicated name does not necessarily help the reader find the right action.
4. Recheck after the layout changes
Use the same instructions in the supported layouts available to your review. Record whether the intended control is still identifiable when a toolbar collapses or a help panel moves. Do not claim an untested layout works simply because the sentence sounds clearer.
Also check renamed controls. Documentation can lag behind an interface release, leaving a precise but obsolete label. Assign an owner to the instruction so it is reviewed when the relevant task changes.
5. Copy this instruction-reference card
- Task: the activity and step being explained.
- Instruction: exact original sentence and its location.
- Target: intended control and current label.
- Dependency: sensory cue that the sentence relies on.
- Revision: proposed identifying reference and expected next action.
- Checks: interface states and layouts actually reviewed.
- Ownership: person responsible for keeping the wording current.
Ask a reviewer who did not write the instruction to identify the intended control. Record any extra explanation they need. For a safe test, stop before purchases, sharing or other consequential actions unless those actions are separately authorized.
The acceptance criterion is that the instruction identifies the intended step without depending only on a sensory cue. Report the specific task reviewed, not a blanket accessibility claim about the entire site.