Colquhoun.AI
← All guides

Research Guides

Match a Research Control's Name to Its Visible Label

· Colquhoun.shop editorial

A research button can say “Export” on screen while being exposed to assistive technology under a different name. The action may work with a mouse, yet someone trying to activate it by speaking the visible words can encounter a confusing mismatch.

This worksheet reviews the relationship between a visible label and a control's accessible name. It is a manual test for an authorized interface or prototype, not a claim that Colquhoun.shop supplies voice control or has passed a complete accessibility assessment.

1. Record the two names separately

Select controls used in a short research task: search, apply a filter, open a source and export a result. Record the visible wording exactly, then inspect the accessible name exposed by the browser's accessibility tools. Include the page and interface state.

Do not infer the accessible name from appearance alone or from one attribute copied out of the source. Record the computed result available in the tested browser, along with how you inspected it.

2. Compare against the visible words

W3C's Label in Name guidance requires the accessible name of a control with a visible text label to contain that text. Starting the name with the visible label is a recommended practice. The guidance explains how this supports people who use visible wording to operate controls through speech input. W3C: Understanding Label in Name

Keep the comparison scoped to the actual label. A section heading or a long instruction near the control is not automatically part of its visible label. If identification is ambiguous, record that ambiguity rather than declaring a match against whichever nearby phrase is convenient.

3. Trace an override before adding another one

In a fictional research toolbar, the visible button says “Export CSV,” but its accessible name is “Download spreadsheet.” Both phrases sound reasonable in isolation. They nevertheless create two different names for the same control.

W3C notes that ARIA labeling can override a name otherwise supplied by visible text. Its guidance advises care when a visible label already exists. Inspect the naming source before adding another attribute as a quick fix.

The proposed repair should identify the intended wording and preserve the action. Do not turn a CSV export into a vaguely labeled download simply to make a checker stop warning. Verify that the name still describes the file the user receives.

4. Review state changes and repeated controls

Repeat the check after the interface changes. A control might switch from “Show filters” to “Hide filters” visually while retaining an old accessible name. Record both states and the action expected in each.

For repeated controls, distinguish the visible label from extra identifying context. An editor may want the accessible name to identify the relevant source or row, but that context should not erase the words readers can see on the control.

Use safe sample records when activating actions during testing. A label audit does not authorize sending a message, deleting research or submitting a paid request.

5. Keep the label decision reproducible

After an authorized correction, inspect the public interface again and activate the harmless test action. Matching names do not prove that focus behavior, descriptions or the underlying operation are correct.

Where practical, test with the relevant speech-input or screen-reading setup and record its version. If that test was not performed, say so. A computed-name inspection is valuable evidence, but it is not the same as observing every assistive-technology interaction.

The useful result is one recognizable label across the routes people use to reach the action, with a clear record of what was actually verified.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.