• Success Criterion 4.1.2
  • Conformance level A
  • W3C reference F86

Multi-Part Field Where Each Box Has No Individual Name

4.1.2 — Name, Role, Value

Scenario

Setting

A ticket marketplace's seat-selection map

What’s wrong

Each box of a multi-part field (e.g., 3 phone-number boxes) has no individual name — screen readers announce three anonymous 'edit' fields.

Example

A ticket marketplace's seat-selection map shows the problem clearly: each box of a multi-part field (e.g., 3 phone-number boxes) has no individual name — screen readers announce three anonymous 'edit' fields.

Why it matters

Screen-reader and voice-control users who can operate only what the accessibility tree exposes. On a ticket marketplace's seat-selection map, this barrier means they are excluded from part of the experience.

How to test

Inspect a multi-part field (e.g., a 3-box phone number): check whether each box has its own accessible name, not just a single label for the whole group.

How to fix

Name every part of a multi-part field (visible group label + per-part accessible names).

Outcome

Corrected, a ticket marketplace's seat-selection map now lets a visitor complete the task without extra help.

Who is affected

Screen-reader and voice-control users who can operate only what the accessibility tree exposes.

Learn more

Related scenarios