How to fix button name on Webflow

Steps for Webflow

1. In the Webflow Designer, select the button element on the canvas that is missing a label.
2. In the right-hand Settings panel (the gear icon), find the 'Accessibility' section. In the 'Aria Label' field, type a clear, descriptive name for the button (e.g. 'Close dialog' or 'Open search').
3. For Navbar components (hamburger menu button), click the Navbar element, then open its Settings → find the Menu Button and set its Aria Label in the same Accessibility section.
4. For CMS-driven buttons where the label should be dynamic (e.g. 'Add [product name] to cart'), bind the Aria Label field to a CMS field using Webflow's dynamic binding (click the purple database icon next to the Aria Label input and connect it to the appropriate CMS field).
5. For e-commerce Add to Cart buttons, select the button inside the Product element, open Settings → Accessibility, and set the Aria Label or bind it dynamically.
6. Publish the site and test with a screen reader or the axe DevTools browser extension to confirm no button-name violations remain.

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.