Bad code Bad code
<input type="text" placeholder="First name">
Issues and how to fix them Issues and how to fix them
- Every form input element needs a label. When screen reader users access a form field, the label is announced with the field type (e.g. first name, edit text). If it’s missing, users might not know what they’re supposed to fill in (e.g. edit text).
- Some screen readers fall back to
placeholderas the label, but it’s not recommended to rely on it.
- By default, placeholder text is displayed in a light grey color with low contrast. It might not be readable for people with low vision or under certain conditions, like strong sunlight.
- It’s possible to increase contrast by using the
::placeholderpseudo element, but if contrast is too high, users may mistake a placeholder for data that was automatically filled in.
- Using and displaying a
<label>increases the target size of the form field which can be of great help, especially on touch devices.
placeholderfunctions as the only label, the label disappears when the user types. This strains their short-term memory, especially on complex or rarely used forms.
- Users cannot check what they’ve filled in before submitting a form, because they only see values and no labels.
- If browsers auto-fill fields, users have to cut-and-paste auto-filled values to check if browsers filled in fields correctly.
- Placeholder text is cut off if it goes beyond the size of the field.
- Translation tools like Google Translate might not translate attribute values.
- Labels work best when they’re placed above the corresponding text field, not in the field.
Check out the resources section at the bottom of this page for more.
Good code Good code
<label for="firstname">First name</label>
<input type="text" id="firstname">