• Success Criterion 2.4.6
  • Conformance level AA

Form Label Like ‘Field 1’ That Doesn’t Describe Its Purpose

2.4.6 — Headings and Labels

Scenario

Setting

An e-book reader's library page

What’s wrong

Labels that don't describe the field's purpose: "Field 1", bare "*", "Enter value".

Example 

<label for="f1">Field 1</label>
<input id="f1" placeholder="e.g. Tolkien">
<label for="f2">*</label>
<input id="f2">
<label for="f3">Enter value</label>
<input id="f3" type="date">

Why it matters

A user filling out the book request form can't tell that Field 1 wants an author name and the asterisk field wants an ISBN.

How to test

Read field labels like 'Field 1' or a bare '*' out of context: if they don't describe what to enter, they fail.

How to fix

A label should name the data the field collects, not a placeholder position like Field 1.

<label for="f1">Author name</label>
<input id="f1" placeholder="e.g. Tolkien">
<label for="f2">ISBN</label>
<input id="f2">
<label for="f3">Requested by date</label>
<input id="f3" type="date">

Outcome

A reader fills in Author name and ISBN correctly on the first attempt.

Who is affected

Screen reader and cognitive-disability users depend on labels to know what to type, and generic ones leave them guessing.

Learn more

Related scenarios