Form Inputs Missing Labels

What This Means

One or more form input elements (<input>, <select>, <textarea>) do not have an associated label. A label is considered associated if it uses for="input-id" matching the input's id, if the input is wrapped inside a <label> element, or if the input has an aria-label or aria-labelledby attribute.

Why It Matters for SEO

Screen reader users cannot identify the purpose of an unlabeled input field. When focus moves to the input, the screen reader announces nothing useful — just "edit text" with no context. This is a WCAG 2.1 failure (Success Criterion 1.3.1 and 4.1.2).

For SEO, labeled form fields are better understood by search engines that try to parse form context. Contact forms, search forms, and subscription forms with proper labels are more interpretable.

What the Platform Checks

The platform checks each form input for a properly associated label via: <label for="...">, parent <label> wrapper, aria-label, or aria-labelledby. Fires when an input has none of these.

How to Fix It

• Add a <label for="input-id"> element preceding each input, with the for attribute matching the input's id:
• Or wrap the input inside a <label> element.
• For hidden labels (visual design constraints): use aria-label="Field description" on the input itself.
• Never use placeholder text as a substitute for a label — placeholders disappear when the user starts typing.