How to fix aria input field name on Wix

Steps for Wix

1. Open the Wix Editor and click on the form or input element with the accessibility issue.
2. In the element's settings panel, look for an 'Accessibility' section (available on some Wix form and text input widgets) and fill in the 'Accessible Label' or 'aria-label' field.
3. For Wix Velo (custom code): open the Dev Mode panel, click the input element to get its component ID, then in the page code (or site code) use the element's 'accessibility.ariaLabel' property: $w('#myInput').accessibility.ariaLabel = 'Search products';
4. If the input is inside a Wix Form app widget, go to the form editor, click the specific field, and edit the field label — ensure 'Show Label' is toggled on, or use the field settings to add placeholder/label text.
5. Publish the site and verify using the browser axe extension or Chrome Accessibility Tree.

<label for="product-search">Search products</label>
<input id="product-search" type="text" role="searchbox" />

<!-- OR, when a visible label isn't possible: -->
<input type="text" role="searchbox" aria-label="Search products" />

<!-- OR, referencing existing visible text: -->
<h2 id="filter-heading">Filter by price</h2>
<input type="text" role="spinbutton" aria-labelledby="filter-heading" />

What is aria input field name?

Any interactive form field that uses an ARIA role (such as `role="textbox"`, `role="spinbutton"`, `role="searchbox"`, `role="combobox"`, or `role="slider"`) must have an accessible name — a short text label that describes what the field is for. This name can be provided via an HTML `<label>` element, an `aria-label` attribute, or an `aria-labelledby` attribute pointing to visible text on the page. Without it, assistive technologies like screen readers have nothing to announce when a user reaches the field. WCAG Success Criterion 4.1.2 (Name, Role, Value) requires that all user interface components have a name that can be determined programmatically.

Screen reader users — including many people with visual impairments — rely entirely on accessible names to understand what a form field is asking for. An unnamed input field is announced as a blank or generic "edit field," leaving the user completely unable to fill it in correctly, which means lost sales, failed sign-ups, and broken checkout flows on your store. Beyond conversions, failing WCAG 4.1.2 is one of the most commonly cited violations in accessibility lawsuits and regulatory audits (ADA, Section 508, EN 301 549, and the EU Web Accessibility Directive), exposing your business to real legal and financial risk. Fixing it also improves SEO indirectly, since search engines use semantic HTML signals — including proper labeling — to better understand page content and forms.

See the complete Aria input field name guide for every platform and the full background.