Give every field a label
A placeholder is not a replacement for a label. A visible label remains available before, during and after input and provides a usable name for assistive technologies.
- Use <label for> with a matching field id.
- Keep visible labels for important information.
- Add separate help text when the expected format needs explanation.
Explain constraints before errors happen
Required fields, formats and limits should be clear before submission. Users should not discover the rules only after a failed attempt.
- Clearly identify required fields.
- Use appropriate HTML types such as email, tel, url or date.
- Use autocomplete for common personal data when it helps.
Make errors easy to fix
After validation, each message should explain the problem and remain associated with the relevant field. A summary can complement local messages on longer forms.
- Place a specific message near the invalid field.
- Keep previously entered values whenever possible.
- Move focus to an error summary when several fields require attention.
Practical checklist
- Every important field has a visible label.
- Constraints are explained before submission.
- The complete journey works with a keyboard.
- Errors are specific and linked to the correct field.
- Focus remains visible and logical.
Continue with related resources
Conclusion
An accessible form is usually easier for everyone. The same improvements reduce mistakes, build confidence and can support conversion.