How to fix aria input field name on BigCommerce
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 BigCommerce
- In BigCommerce Admin, go to Storefront → Themes → click Customize on your active theme → click Advanced → Edit Theme Files (opens Stencil theme editor) or download the theme via the Theme Marketplace for local editing.
- Common problem files: templates/components/cart/item-quantity.html (cart quantity inputs), templates/components/search/quick-search.html (search bar).
- In item-quantity.html, locate the <input type="number"> and add aria-label="Quantity for {{name}}" using the available Handlebars context variable for product name.
- In quick-search.html, ensure the search <input> has aria-label="Search our store" or is wrapped in a <label>.
- Upload/save the modified theme files, preview the change, then publish the theme.
- Verify with axe DevTools browser extension on the live storefront.
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 BigCommerce 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