Few patterns are as visually appealing and as functionally poor as a form that uses placeholder text instead of labels. It photographs beautifully in a design mockup and degrades the moment anyone actually uses it.
What the attribute is for
The placeholder attribute displays a short hint inside an empty field, which vanishes as soon as the field has content.
<label for="phone">Telephone</label> <input type="tel" id="phone" name="phone" placeholder="07700 900123"> The specification describes it as a short hint about the expected value, explicitly noting it is not a substitute for a label. That is the intended use: an example of the format, alongside a real label.
The text disappears when you need it
The core problem is that the hint vanishes exactly when the user is working. Someone who is interrupted, who returns to check their answer, or who is simply reviewing a completed form has no way to see what a field was asking for without deleting their answer.
This affects everyone occasionally and affects some people constantly. Anyone with a memory or attention difficulty, anyone completing a long form, anyone working in a second language, and anyone being interrupted is worse off.
The contrast trap
Placeholder text is rendered in a light grey by default, and that default often falls below accessibility contrast requirements. It is genuinely hard to read for anyone with reduced vision or on a screen in bright light.
The obvious fix creates a new problem. Darkening the text until it meets contrast requirements makes an empty field look filled in, so people skip it and then cannot work out why the form will not submit. There is no value that solves both problems at once, which is a strong indication that the pattern is wrong rather than that the styling needs tuning.
Assistive technology support varies
Some screen readers announce a placeholder as a fallback when no label is present, and some do not. Voice control software matches spoken commands against visible labels, which a placeholder does not reliably provide.
Relying on inconsistent behaviour to convey essential information means the form works for some users and not others, with no way to know which.
Translation and autofill
Automatic translation tools handle labels reliably and are less consistent with placeholders, so a translated page may show an untranslated hint. Browser autofill also fills fields based on labels and autocomplete tokens, and a form without labels gives it less to work with.
Floating labels
The common compromise starts the label inside the field and animates it above once the user types. This preserves the visual economy while keeping the label present.
It is better than placeholder-only and not free of problems. The floated label is typically very small, which can push it below readable size. The animation adds motion that should respect a reduced motion preference. And the field must be genuinely a label element rather than a styled placeholder, which some implementations get wrong.
If the design can accommodate a plain label above the field, that remains the most robust option.
When a placeholder helps
There are legitimate uses. An example demonstrating an expected format is useful, particularly for fields where the format is not obvious, such as a reference number or a date.
The rule is that the placeholder must add information the label does not carry. Repeating the label as a placeholder is pure duplication, and it may cause some screen readers to announce the same words twice.
Search fields are the common exception
A search box with a placeholder and no visible label is so familiar that it rarely confuses anyone, and the surrounding icon and button usually make its purpose obvious. Even here, a real label hidden visually should be present in the markup, so the field has a proper accessible name rather than depending on placeholder support.
That combination gives you the clean appearance the design wants and the correct announcement, which is the pattern worth copying wherever space is genuinely tight.
Format hints belong outside the field
Where the requirement is more than a brief example, put it in visible text near the field and associate it with an aria-describedby attribute pointing at its id. This text is announced after the label, stays visible while the user types, and can be as long as it needs to be.
Password requirements are the obvious case. Nobody can satisfy a complex rule from a placeholder that disappears at the first keystroke, and hiding the rules until an error appears is a needlessly frustrating way to run a registration form.