Protocol

Check that a field keeps the name you gave it

A label can remain on screen yet name the wrong field, or no field at all. Check both what people see and what software exposes.

About 3 min read

Before you use it

Use when
  • A form looks clean until its placeholder disappears.

Keep this limit in mind

  • Some controls have context-specific labelling patterns. A technical label association alone does not make confusing wording clear.

Current editorial reading

Keep the purpose visible

Fill an ordinary text field, then return to it. Can you still tell what it asks for? Keep a clear label outside the placeholder; put format help beside it. For example, a Project code field should still say Project code after someone enters PX-42.

Check the connection

For an HTML text field, one standard route is a label element whose for value matches the field’s unique id. Inspect that connection and click the label to check which field receives focus. This is one supported pattern, not a requirement to use it for every kind of control.

Inspect the name the field actually exposes

In the browser’s accessibility inspector, read the field’s computed Name, not just its nearby text. An aria-label or aria-labelledby can override the ordinary label. Compare the name with the intended field purpose, then repeat with a filled value and an error. Record the browser and assistive technology when checking how the field is presented in use.

Take it with you

Keep one short record: visible label, linked control and computed name. A correct link or successful click alone does not establish a usable name. Some controls can rely on clear surrounding context; a hidden name cannot replace visible instructions that the user still needs.

Sources and evidence (4)

What we checked

Supports

WAI describes explicit HTML label association through matching for and id values.

Tutorial updated 2024-05-13; selected passages inspected 2026-10-06. The explicit link is one route. Context can sometimes support a visually hidden label; that does not make hidden-only labeling a general recommendation.

Labeling Controls · Associating labels explicitly; Associating labels implicitly; Hiding label text

Supports

For applicable HTML controls, H44 describes matching label for and control id values, a unique id and activation through the associated label.

Technique updated 2026-01-12; selected passages inspected 2026-10-06. This is a sufficient technique within its stated scope, not a requirement that every control use an external label or a whole-interface conformance test.

H44: Using label elements to associate text labels with form controls · Description; elements that use explicitly associated labels; Tests

Supports

Placeholder text is not an appropriate replacement for a field label; ARIA naming can override native label associations.

Understanding page updated 2026-04-05; selected passages inspected 2026-10-06. This is the inspected locator for the placeholder warning; the Labeling Controls tutorial was not found to contain the placeholder discussion attributed to it in the historical base item. That historical record remains unchanged.

Understanding Success Criterion 2.5.3: Label in Name · Identifying label text for components; Accessible Name and Description Computation specification

Limits

Visible field identity, programmatic naming and visible instructions address related but distinct needs.

The filled-field example, inspector sequence and record are editorial application of the guidance, not observed user results. A placeholder may still be the visible text evaluated for Label in Name when no other label exists; that does not make placeholder-only design good labeling. No assistive-technology test was performed for this draft.

Understanding Success Criterion 2.5.3: Label in Name · Identifying label text for components; Accessible Name and Description Computation specification

Provides context

Chrome DevTools exposes computed accessibility properties, while markup inspection does not establish successful assistive-technology navigation.

Official tool documentation updated 2026-05-28; selected passages inspected 2026-10-06. Supports the feasibility and limits of the inspector step. Other browsers may expose equivalent information through different tools; no browser or assistive-technology runtime test was performed.

Accessibility features reference — Chrome DevTools · Overview of accessibility features in Chrome DevTools; The Accessibility tab; View an element’s computed accessibility properties

Editorial sources (4)

Editorial version 1.0.0 · Evidence checked 2026-10-06

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingCheck that a field keeps the name you gave it

Original edition evidence and sources

These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.

Supports

WAI guidance describes associating labels with form controls and warns against relying on placeholder text as a replacement for labels.

A programmatic label and a usable visible instruction solve related but distinct needs.

Labeling Controls · Associating labels and placeholder discussion.

All sources (1)
Original edition, downloads and provenance

The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.

Version 0.1.0

No review details are supplied for this edition.

Read the original edition and overlay as JSON · Release details