Form Labels Check
How VitalSite checks that every form field has an accessible label so screen-reader users can complete your forms — and how to fix unlabeled inputs.
A form field with no label is a mystery to a screen-reader user — they hear "edit text" with no idea what to type. VitalSite checks that every input, select and textarea has a programmatically associated label, using axe-core and WCAG criteria 1.3.1 (Info and Relationships), 3.3.2 (Labels or Instructions) and 4.1.2 (Name, Role, Value).
What VitalSite checks
- Every field has a label. Each
<input>,<select>and<textarea>must have an associated<label>, or an accessible name viaaria-label/aria-labelledby. - Placeholder is not a label. Placeholder text disappears when the user types and is not announced reliably — it does not count.
- Labels are correctly associated, so clicking the label focuses the field and screen readers announce it.
Why it matters
Forms are where conversions happen — signups, checkouts, contact. An unlabeled form quietly excludes assistive-technology users from your most important actions, and it is a frequent ADA complaint target. Proper labels also make forms easier for everyone (a bigger click target, clearer intent).
How to fix it
Associate a real <label> with each field using for / id:
<label for="email">Email address</label>
<input id="email" type="email" name="email">If a visible label is not possible, give the field an accessible name with aria-label. Do not rely on placeholder text alone.
Verify the fix
Re-scan your domain. The Form Labels check should show every field with an accessible name. On Pro, VitalSite lists each unlabeled field with its page and element.
Run a free full-domain scan to see whether this affects your site — every page, with an exact fix guide. Pro and Agency plans add PDF export and monitoring.
See if this affects your site
Run a free full-domain scan — this check runs on every page, with an exact fix guide.