Form inputs missing labels
Part of Documentation, UX & Accessibility, which counts for 15% of the overall score. When this check fires it deducts 8 points from that category, once per scan, no matter how many places it turns up.
What it detects
Form inputs with no associated label or aria-label are hard or impossible to use with assistive technology.
Why it matters
A form input with no associated label has no announced name, so a screen-reader user hears "edit text" with no idea what to type. Placeholders do not count: they vanish once the user types and are not reliably read as the field name. Visible labels also help everyone, since they give a bigger click target and stay readable after the field is filled.
How to fix it
Give every non-hidden input an accessible name. Prefer a visible <label for="field-id"> paired with an id on the input (htmlFor in JSX); where a visible label genuinely does not fit, such as a search box with an icon, use aria-label="Search" on the input. Do not rely on placeholder text as the only labeling, and keep the label text short and specific ("Email address", not "Enter value").
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo