An empty field displays “Email”, but the hint disappears as soon as someone types. This can make the field harder to identify and does not replace a proper label. Inputs need understandable names that remain accessible during entry.
A simple example associates a visible label with an input:
<label for="contact-email">Email address</label>
<input id="contact-email" name="email" type="email"
autocomplete="email">
Use a unique id. Duplicate identifiers can undermine an otherwise correct association. Add explanatory examples separately where needed rather than using them as the only name.
Continue testing after entry
Partially complete the form. Can someone still identify what each field requests? Click or tap the label and check that the intended input receives focus, then navigate through the fields with a keyboard.
Inspect accessible names in the accessibility tree. An added aria-label can override visible wording; do not automatically apply one to every correctly labelled field.
Clearly identify optional information. This helps people decide which data is necessary. Technical association does not establish understandable wording: “Reference” can be correctly labelled but remain ambiguous.
Ask someone unfamiliar with the form whether they understand the required information without hints. Record which fields cause questions.