When should you use Form fields are labelled?
form-labels-associatedfunctionalrequired
A screen reader announces an unlabelled field as just "edit text", so the visitor cannot tell what to type and abandons the form; every input, select and toggle must carry a programmatic label.
When should you use this check?
Run this on every page with a form. An unlabelled field is announced as "edit text" and nothing more, so a screen-reader user cannot tell an email box from a phone box. It is one of the defects most often cited in accessibility complaints, and one of the easiest to fix once found.
When should you not?
It proves each field has a programmatic name; it does not judge whether the name is clear. A label reading "Field 1" passes. Hidden fields and buttons whose type gives them a name are out of scope.
What does it inspect?
inputs with no label at all; selects with no name; toggles with no label
What does a failure mean?
A failure names the field and the rule it broke: no label, no name on a select, a button input with no value, or a custom ARIA field with no name. A field named only by its placeholder is listed for review rather than failed: the accessible-name rules accept a placeholder, but its words disappear as soon as the visitor types. Fields the engine could not decide are listed for review too.
What are the Standard defaults — and why?
There is no threshold. WCAG 1.3.1, 3.3.2 and 4.1.2 require every form control to have a programmatic name; a label element, aria-label, aria-labelledby or a title all satisfy it.
How does an agent call it?
{ "type": "url", "validations": ["form-labels-associated"] }Who governs the Standard?
SchemaFirst.org publishes community-governed standards for digital QA. ArbiterQA is a supporter and commercial licensee of those standards; citation does not mean SchemaFirst operates ArbiterQA.
Author ArbiterQA · Reviewed by ArbiterQA · 2026-10-01
Related
Run this check on your own assets
1,000 credits a month on the free plan. No card.