Matan · WCAG · Operable
Form labels
WCAG 1.3.1 and 3.3.2: every input needs a label so the accessible name is clear.
Pass condition in our engine: Visible inputs have an accessible name.
1. Problem description
Placeholder is not a label. Unlabelled search boxes and email fields fail both accessibility and autofill. Hidden, submit and button types are ignored.
2. Most common causes
- Material-style floating labels not associated with the input.
- Custom selects without aria-label.
3. How to fix it
- Use <label for>
- or wrap the control, or aria-label / aria-labelledby.
Test this check
We fetch only this URL (plus robots.txt / llms.txt at the domain root when the check needs them). We do not crawl the rest of the site like a full report.
Scoring rules for the full site crawl are documented in methodology. Want every category at once? Generate a free report.
Get your free SEO & GEO report
Enter your URL and receive a full audit with scoring and recommendations. No sign-up required.