How to fix aria input field name on Webflow
Add a descriptive accessible name (aria-label, aria-labelledby, or a visible <label>) to every ARIA input field so assistive technologies can identify it.
Steps for Webflow
- Open the Webflow Designer and click the input or form element that is flagged.
- In the right-hand Settings panel (the gear icon), scroll to the 'Accessibility' section. Fill in the 'Custom Attribute' fields: Name = aria-label, Value = your descriptive label text (e.g. 'Email address').
- Alternatively, if a visible label exists, ensure the label's 'For' attribute matches the input's 'ID' — set both in the Settings panel to create a proper label association without needing aria-label.
- For Webflow's native Form Block fields, click the label element inside the form and ensure it is not set to 'Display: None' in the Style panel — hiding labels visually removes them for sighted users but assistive tech may still read them; use the visually-hidden CSS technique instead if you need to hide labels.
- Publish and verify with axe DevTools.
What is aria input field name?
An "ARIA input field name" is the text label that screen readers and other assistive technologies announce when a user focuses on a form field — a text box, search bar, date picker, quantity field, or any other input that uses an ARIA role like `textbox`, `spinbutton`, `searchbox`, `slider`, or `combobox`. When that label is missing or empty, the field has no accessible name. WCAG Success Criterion 4.1.2 (Name, Role, Value) requires every user-interface component to have a name that programs can determine. A field without a label is essentially invisible to assistive technology users.
Screen reader users — including many customers with visual impairments — cannot understand what to type into an unlabeled field, which means they cannot complete your checkout, search for products, or fill in any other form on your site. This directly costs you sales and excludes a significant portion of your potential customers. Legally, WCAG 2.1 AA compliance (which includes SC 4.1.2) is referenced in accessibility laws and regulations in the US (ADA), EU (EAA), UK (PSBAR), and elsewhere — stores with unlabeled form fields are at real legal risk. Search engines also use accessible markup signals as part of overall quality assessment, so fixing this contributes to long-term SEO health.
See the complete Aria input field name guide for every platform and the full background.
Not sure if your Webflow store has this?
Run a free SEOLZ scan — we’ll find aria input field name and every other issue across your whole site.
Scan my site free