Glossary · Accessibility term
Form label
A form label is the visible text naming a field, tied to that field in code so software can tell which words belong to which box. The visible half and the coded half are two different things and WCAG names them separately, which is worth knowing because a field can have one without the other. Placeholder text is the usual way that happens. It looks like a label, and it does get used as a last-resort name when nothing better exists, so a placeholder-only field is not silent. It is worse than silent in a different way. The prompt vanishes the moment somebody types, so anybody interrupted mid-form has lost the question they were answering, and placeholder grey is usually the palest text on the page. Four separate rules touch this. One asks that a label or instruction exists at all. One asks that the control carries a name software can read. One asks that the connection between them sits in the code. And one asks that the label describes the field.
In practice
In HTML the connection is a label element whose for attribute matches the input's id, or a label with the input nested inside it, and either way the payoff is testable in one click. Click the label text. If focus jumps into the box, they are connected, because forwarding that click is specified behaviour rather than a browser quirk. Read a silent click carefully, though. It rules out a real label element and it does not rule out a name, because aria-labelledby names a control correctly and forwards no clicks at all. So the click tells you which mechanism you have, and only the accessibility tree tells you whether there is a name.
The requirement covers every field, not only the required ones. The rule's own word is requires, and it is used there to mean accepts, which is a misreading common enough that W3C corrects it in the guidance. An optional field with no label fails on exactly the same terms as a required one.
Labels do not have to be the label element and they do not have to be words. A legend inside a fieldset labels a group. That is the answer for anything split across boxes, such as a phone number, a date or a card expiry, where no single field carries the meaning alone. An image can label a field too, which is what the magnifying glass on a search box is doing, as long as the audience reads it the way you meant.
More help is not automatically better. W3C's own warning is that too much information or instruction can be as harmful as too little. A field wrapped in three lines of hint text is slower for everybody. It is much slower for somebody hearing all of it read out before they can start typing.
Why it matters
Missing form labels turned up on 51% of the top million home pages in February 2026, third behind low contrast text and missing alt text. A third of all form inputs on those pages carried no name software could read, by any mechanism. What that measures is the coded half, so some of those boxes do have words beside them and no way for a screen reader to tell which box the words belong to. It is also the failure that sits closest to your money, because the boxes are in checkout and contact forms. And it is the one an auditor cites hardest, since the criterion that fails for a nameless control is Level A.
The two-second test
Click the words next to a box. If the cursor lands in the box, a label element is connecting them and you are done. If it does not, open the accessibility tab in your browser's developer tools and read the field's name. A name there means something else supplied it, usually aria-labelledby. Nothing there means the field is announced by whatever the browser could scrape together, which on a good day is the placeholder and on a bad one is silence.
Where this shows up on the site
Related terms
- Accessible nameThe accessible name is what assistive technology announces an element as, the words a screen reader speaks when it lands on a button or a link.
- Error identificationError identification is the Level A rule that when your form rejects something, the page names the field that failed and says in text what went wrong.
- Semantic HTMLSemantic HTML means using HTML elements for what they mean rather than for how they look.
- UnderstandableUnderstandable is the third of WCAG's four principles, and it splits in two the way its own sentence does.
- AutocompleteAutocomplete is an HTML attribute naming what a form field collects.
Knowing the word is the easy part.
Find out where your own site stands. The free scan checks 10 pages in a real browser against all 90 supported automated rules, separates 27 best-practice checks from its WCAG findings, and names the rule behind every result.