Form control has no recognised associated label
ShipReady found static HTML input, select, or textarea controls with an id but without a recognised label or accessible-name signal.
Why it matters
A clear label helps people understand what information a form control expects; placeholders are not a durable replacement for a label.
How ShipReady detects it
What it inspects
ShipReady examines static, successfully fetched, untruncated HTML input, select, and textarea elements.
What triggers a finding
The rule triggers for eligible controls with an id when no matching label for, aria-label, aria-labelledby, or title is present.
What the evidence shows
The scanner observed eligible controls without one of its recognised labelling signals. It reports a count and a shortened id sample.
Limits of this check
ShipReady excludes non-text input types, controls without ids, aria-hidden controls, and controls with tabindex minus one. Its passive regex cannot reliably recognise a control wrapped by a label, so this finding is medium confidence and is not a complete WCAG or assistive-technology audit.
How to fix it
Add an explicit accessible label
Use a label for whose value matches the control id, or provide an appropriate accessible name where a visible label is not suitable.
How to verify the change
Test the deployed form
Inspect the rendered form and test representative controls with accessibility tooling and assistive technology appropriate to the product.
Expected: Each user-facing form control has an intentional, understandable accessible name.