Fix guide · Buttons with no text

How to fix “Buttons must have discernible text”

By · Updated

A button on the page has no name a screen reader can say, usually because it shows only an icon. Put words in the button, or give it an aria-label that says what it does.

axe rule
button-name (this page also covers input-button-name)
WCAG
4.1.2 Name, Role, Value (Level A)
Lighthouse
Google Lighthouse and PageSpeed Insights report it as “Buttons do not have an accessible name”

What it means

A button needs a name for the same reason a link does. Menu buttons with three lines, close buttons with an X, search buttons with a magnifying glass and slider arrows are the usual cases. A screen reader announces just "button" and the visitor has to guess.

The WebAIM Million found empty buttons on 30.6% of home pages in 2026.

Who it affects

People who use a screen reader, and voice control users, who need a name to say out loud.

How to find it

  1. Run the free checker and look at each button it lists. The code usually shows the icon class, like a menu or close icon.
  2. Open your mobile menu, pop ups and image sliders. Their buttons are often icon only.

How to fix it

  1. Add visible words if the design allows. "Menu" beside the three lines helps everyone.
  2. Otherwise add an aria-label that says what the button does: "Open menu", "Close", "Search", "Next photo".
  3. Hide the icon itself from screen readers with aria-hidden="true" so it isn't read twice.
  4. For an input button (input type="button" or "submit"), give it a value attribute.

A mobile menu button

Before · fails
<button class="menu-toggle">
  <i class="icon-bars"></i>
</button>
After · fixed
<button class="menu-toggle" aria-label="Open menu">
  <i class="icon-bars" aria-hidden="true"></i>
</button>

An input with no value

Before · fails
<input type="submit" class="search-go">
After · fixed
<input type="submit" class="search-go" value="Search">

In your website builder

Where each platform’s own help pages cover it, as of November 2026. Menus move, so follow the link if a step doesn’t match what you see.

Wix
Select the button, open Settings and fill in Accessible name. Wix help
Webflow
Select the button and add an aria-label custom attribute in the Element settings panel. Webflow help

What a scanner can and can’t tell you

Fixing this clears one automated check. It doesn’t mean the page is accessible, and it doesn’t settle any legal question. Automated tests catch only part of the problems. W3C puts it plainly: evaluation tools “can not determine accessibility, they can only assist in doing so.” The rest takes a person working through the site with a keyboard and a screen reader.

Source: W3C WAI, Selecting Web Accessibility Evaluation Tools. Not legal advice.

Sources

All checked November 8, 2026. The rule wording is axe-core 4.14.0’s own.

Related fixes

Every fix guide →

Check a page for free

Scan any page of your site against WCAG 2.1 AA in about 30 seconds. You get the problems automated testing finds, in plain words, with a link to a fix guide for the common ones.

Run the free checkno sign up · one page at a time

Rather have someone fix it for you? Tell me about your site.