- Level
- A
- Since
- WCAG 2.0
- Entries
- 3 / 193
3.3.2 Labels or Instructions
Every place where a person has to enter something needs a visible label or an instruction that says what is expected.
/ What it requires
Wherever content asks for input, people need to know what to enter before they start. That means a visible label for each field, a question for each group of checkboxes or radio buttons, and an instruction where the input has to follow a pattern, such as a date format or a required field. It helps everyone, and it is decisive for people with cognitive or learning disabilities, for people who magnify the screen and see one field at a time, and for anyone using a screen reader.
The criterion asks that labels or instructions are present. It does not say they must be linked to the field in code, which falls under 1.3.1 and 4.1.2, nor that they must be well worded, which is 2.4.6. It names no exceptions. A placeholder that disappears on the first keystroke leaves the field without a label at the moment people check their entry, which is why auditors do not accept it as the only label.
/ How pages fail it
- A field has only a placeholder such as "Email", which vanishes as soon as typing starts.
- Required fields are marked with an asterisk, and nothing on the page says what the asterisk means.
- A date or phone field expects a fixed format and does not show it.
- A group of radio buttons offers "Yes" and "No" with no visible question above them.
- The instruction for a field is printed below the submit button, after the point where it was needed.
/ How to check it yourself
- Look at each field while the form is empty. Visible text should say what belongs in it.
- Type something into every field and check that its label is still on screen.
- Find the required fields and check that the marking is explained before the first field, or written out as a word in each label.
- Check fields with a fixed format, such as dates, phone numbers and passwords, for a visible hint about what is accepted.
- For every group of checkboxes and radio buttons, look for the question or heading the options belong to.
/ How to fix it
- Give each field a visible label element and connect it through the for attribute to the id of the input.
- Wrap related checkboxes or radio buttons in a fieldset element and write the question in its legend.
- State the expected format in the label or in a hint under the field, and link the hint to the input with aria-describedby.
- Mark required fields with the word "required" in the label, or explain the asterisk above the form. Add the required attribute or aria-required="true" to the input as well.
- Use the placeholder attribute only for an example value, never as the only name of the field.
/ What our scanner checks
One check is filed here, required-not-announced. Where the accessible name of a visible field holds an asterisk or the words "(required)" or "(wymagane)", and the field has neither the required attribute nor aria-required="true", it reports the field. It does not test for a visible label or a format hint. Fields with no label are reported under 1.3.1 and 4.1.2.
/ Who fails it, in our own measurements
| Body | Sector | Instances | Score |
|---|---|---|---|
| Bundesministerium des Innern | government · DE | 1 | 10 |
| Gdynia | city · PL | 1 | 7 |
| Muzeum Narodowe w Warszawie | culture · PL | 1 | 11 |
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
Is a placeholder enough as a form label?
No. A placeholder disappears when the person starts typing, so the field has no label while they fill it in or check it afterwards. Placeholder text is also often too pale to read comfortably. Use a visible label element that stays in place, and keep the placeholder, if you want one, for an example of a valid value.
How should required fields be marked for accessibility?
Visibly and in the code. On screen, write "required" in the label, or use an asterisk and explain it before the first field. In the markup, add the required attribute to the input, or aria-required="true" on a custom control, so that a screen reader announces the field as required. An asterisk with no explanation and no attribute leaves sighted and blind users guessing.
What is the difference between 3.3.2 and 1.3.1 for form labels?
3.3.2 asks whether a label or an instruction exists for the person to read. 1.3.1 Info and Relationships asks whether that label is tied to its field in the code, so that software can report the two together. A form can pass one and fail the other: visible text beside a field with no for attribute meets 3.3.2 and breaks 1.3.1.
