Placeholders are a poor home for format rules

What it is

Rules such as “YYYY-MM-DD,” “11-digit mobile,” or “at least 8 characters with a number” must remain available for checking while someone types. Putting them only in the placeholder is format-in-placeholder failure: once typing starts, the rule leaves the slot, and the rest of the string is assembled from memory. The issue is where rule text survives, not whether the placeholder can act as a field name, and not whether the grey is dark enough.

Why it happens

A format is a constraint, not an identity. Writers need to check hyphens, spaces, and decimal marks during input. If the rule exists only in the empty slot, that check dies after the first character and errors wait until submit. Dates, phone numbers, and money especially need an in-flight check: remembering separator order only in the third group usually wastes the whole string. An example inside the placeholder is also easy to take as a filled or default value, so people skip the field and submit the hint text itself. Format guidance needs copy that outlives the empty state; a placeholder offers the opposite lifetime.

Studying it

Compare format-only-in-placeholder, a persistent note under the slot, and an input mask. Record format-error rate, pre-submit edits, and whether the placeholder string is submitted as a value. Factors: complexity (plain digits versus punctuated dates), paste allowed or not. Outcomes: legality of first submit, delete-to-reread counts. Interrupting and then resuming best exposes “the rule is no longer in view.” Do not credit a mask’s success to the placeholder; a mask is a different mechanism.

Where it stops holding

A very short, universally known format (a four-digit code) shows little failure even when the hint vanishes. Localization changes the rule itself—the same date field wants different separators by region, and a hardcoded placeholder will reject correct input. Password rules are long and multiple; they will not fit, and forcing them in yields a truncated half-sentence. If a screen reader treats the placeholder as the accessible name, the user hears a format instead of a field identity, two messages fighting for one channel.

Applying it

• Put format rules in persistent copy outside the slot, visible throughout typing; do not make the placeholder carry a must-obey rule.
• If you show an example, make it obviously unreal, and never let the example be the only source of the rule.
• For dates, phones, and money, keep separators and digit counts checkable while the person is still writing, not only after submit.
• Verify by stopping people halfway, covering the vanished inner text, and asking what format this cell requires. If they cannot answer, the rule still lives only in the placeholder.

Related

• Within the group: E2.04.1 A placeholder vanishes once typing starts, so it cannot serve as a label · E2.04.2 Placeholder contrast usually sits below a readable threshold
• Adjacent: E2.06 Format hints and examples · E2.07 Input masks
• Search terms: format-in-placeholder failure · format hint · persistent instruction