Form label checker
Finds inputs without labels, placeholders used as the only label, and fields that don't say what they collect.
What this check looks for
The audit runs this check with every other check, on the page as the browser renders it.
- Inputs with no label
- Fields without a label element, aria-label or aria-labelledby, so they have no name.
- Placeholder as the only label
- Hint text that disappears as soon as someone starts typing.
- Missing autocomplete
- Name, email and address fields without the autocomplete values browsers use to fill them.
- Unlabelled groups
- Radio buttons and checkboxes without a fieldset and legend that say what the group is.
What a failure looks like
A reminder sign-up field uses placeholder text instead of a label. Screen readers may announce it only as "edit text".
<!-- Broken: the placeholder is the only label -->
<input type="email" placeholder="Email address"><!-- Fixed: a visible label tied to the field -->
<label for="reminder-email">Email address</label>
<input type="email" id="reminder-email" name="email" autocomplete="email">How it shows in AccessGuard
Each finding names the WCAG criterion, explains the problem in plain words and shows the element that fails, so a developer can find it on the page.
WCAG criteria
Findings from this check name one of these criteria. How much of each the audit can decide on its own:
| Criterion | Level | Automation |
|---|---|---|
| 3.3.2 Labels or Instructions | A | Partly automated |
| 1.3.1 Info and Relationships Headings, lists, tables, labels and landmarks in the markup are checked. Structure shown only visually needs a person. | A | Partly automated |
| 1.3.5 Identify Input Purpose | AA | Partly automated |
| 4.1.2 Name, Role, Value Missing names, invalid roles and broken ARIA are found automatically. Whether custom widgets behave correctly needs a person. | A | Partly automated |
What still needs a person
No automated tool can confirm these. AccessGuard marks related findings as Review, so nobody mistakes them for a pass.
- Whether error messages say what went wrong and how to fix it.
- Whether instructions and required fields are clear before someone submits.
- Multi-step forms, checkouts and log-ins used from start to finish.
Questions
Is placeholder text a label?
No. It disappears when someone types, often has low contrast and is not reliably announced. Use a visible label and keep placeholders for examples.
Can a label be hidden visually?
A visually hidden label gives the field a name for screen readers, which passes 4.1.2. Most people still benefit from a visible label, and WCAG 3.3.2 asks for labels or instructions people can see.
Why does autocomplete matter for accessibility?
WCAG 1.3.5 asks fields that collect personal information to identify their purpose. Browsers then fill them in, which helps people with motor and memory impairments.
Related checks and guides
- ARIA checker
Finds invalid roles and attributes, controls with no accessible name and ARIA that hides content people need.
- Keyboard and focus checker
Finds controls people can't reach by keyboard, focus styles that were removed, and focused elements hidden behind sticky headers.
- Color contrast checker
Measures text and control colors on the rendered page against the WCAG 2.2 AA ratios, and flags links that differ from text by color alone.
- Accessible Forms: WCAG Inputs, Labels, and Errors
Guide
- 7 Form Accessibility Mistakes (and WCAG Fixes)
Guide
Check a client page for form labels issues
The free audit runs this check and every other one. Results in about a minute.