What is an unlabelled form field?
Rubric check: unlabelled form field (check id a11y_label)
An unlabelled form field is an input, such as an email box or a search box, with no label, aria-label or placeholder. Screen-reader users hear "edit text" and can't tell what to type, so they may give up on the form.
Why it matters for SEO
Search engines don't rank pages on form labels. The cost is to the people who use the form: sign-ups, enquiries and orders you lose because some visitors can't complete it. Accessibility rules in many countries also expect labelled form fields.
Does this matter for ChatGPT and AI Overviews?
Browser agents that fill in forms for people, such as booking or shopping agents, often read the page's accessibility labels, as screen readers do. A field with a clear label is easier for them to fill in correctly. This check shares a capped allowance with Rubric's other accessibility checks.
How Rubric scores it
MinorMinor checks cost a quarter to a half of a standard check when they fail.
Why this tier: Unlabelled fields make forms hard or impossible to use with a screen reader.
It is judged on every page Rubric scores.
Every Rubric score starts at 100. When this check fails, it takes up to 6 points off. Even one failing page costs at least 3 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.
This is one of 5 accessibility checks. Together they can take off at most 18 points, so a site isn't marked down many times for one kind of problem.
All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 109 of 300 sites where Rubric could judge it (36%). That is 106 of 287 judged sites in Rubric's 313-site test set and 3 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)
Real sites: people checked 42 of its findings by hand and 6 were wrong (14%). Last checked 14 Nov 2026.
Latest review round: 0 of 89 findings judged were still wrong after the last fix.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Open the form in your form plugin (WPForms, Gravity Forms, Contact Form 7 or similar).
- Give every field a label. If the design hides labels, use the plugin's "screen reader only" or "hidden label" option rather than deleting the label.
- In Contact Form 7, wrap each field in a label:
<label>Your email [email* your-email]</label>.
Shopify
- Check the newsletter, contact and search forms in Online Store > Themes > Customize. Most themes label these fields already.
- If a section or app adds a field with no label, edit the section's Liquid file to add a
<label for="...">(it can be visually hidden), or ask the app developer.
Webflow
- In the Designer, select each form field and check it has a Field Label element above it.
- Select the label and set For to the field's ID in the element settings.
- If the design has no visible label, keep the label and hide it visually with a screen-reader-only class rather than removing it.
Custom code
Link a label to each field with for and id:
<label for="email">Email address</label>
<input id="email" type="email" name="email">For a search box with no visible label, use aria-label="Search".