How to fix button name on BigCommerce

Steps for BigCommerce

1. In BigCommerce Admin, go to Storefront → My Themes → click Customize on your active theme → then Advanced → Edit Theme Files (opens the Stencil theme editor / WebDAV access).
2. Locate the Handlebars template files containing offending buttons. Common locations: templates/components/common/header.html (nav/cart/search icons), templates/components/products/add-to-cart.html (product buttons), templates/components/carousel/ (slider arrows).
3. Add aria-label attributes to icon-only <button> elements in these templates.
4. If you use Page Builder widgets, edit the widget's HTML in Storefront → Page Builder, select the element containing the button, switch to HTML/Custom Code view, and add the aria-label there.
5. Commit and push changes via Stencil CLI (stencil push) or save via the Theme Editor, then test with a screen reader.
6. Re-run an accessibility scan (e.g. axe DevTools browser extension) to confirm the button-name violations are resolved.

What is button name?

Every button on a webpage must have an "accessible name" — a short piece of text that describes what the button does. This name is what screen readers announce aloud when a blind or low-vision user navigates to that button. An accessible name can come from visible text inside the button (e.g. "Add to Cart"), an `aria-label` attribute, or a linked text element. When a button has no accessible name — for example it contains only an icon or an image with no alt text — screen readers may announce it as simply "button," leaving users with no idea what it does. WCAG Success Criterion 4.1.2 (Name, Role, Value) requires all interactive controls to have a programmatically determinable name.

Screen reader users — a significant and growing segment of online shoppers — cannot use your store if they cannot identify your buttons. A "Search," "Add to Cart," or "Checkout" button with no accessible name is effectively invisible to them, directly costing you sales and customers. Beyond conversions, accessibility failures like this create real legal exposure: lawsuits under the ADA (US), the European Accessibility Act (EU), and equivalent laws worldwide increasingly target e-commerce stores. Google also uses accessibility signals as a proxy for page quality, so fixing these issues can contribute positively to your organic search rankings and Core Web Vitals scores. Fixing unnamed buttons is one of the highest-impact, lowest-effort accessibility improvements you can make.

See the complete Button name guide for every platform and the full background.