WCAG 4.1.2 · Level A

Buttons must have discernible text

Some buttons have no accessible name, so screen reader users hear only 'button'.

What this rule checks

Ensure buttons have discernible text.

Why it matters

WCAG 4.1.2 requires every control to have a name. Unnamed buttons often include quantity steppers, close buttons and slider arrows.

How to fix it

  1. Find the buttons that have no name, usually buttons that show only an icon.
  2. Add visible text, visually hidden text, or an aria-label that says what the button does (for example aria-label="Close" or aria-label="Increase quantity").

How to check the fix

  • Re-scan the affected pages.
  • Check the buttons with a screen reader.

How FixReports finds it

Our scan runs the axe-core rule button-name in a real Chrome browser on every page it tests, and reports each failing element with its page, its markup and, where it applies, a screenshot.

An automated test confirms that this specific problem is present. It can't tell whether the rest of the page is accessible: some barriers only show up when a person checks the page.

Scan your website today

Find it. Fix it. Verify it.

What kind of website is this?

Your answer picks the right checks, like the shopping journey for online stores. We still check the site's own evidence and show both.

What kind of website is this?

Free scan. No credit card required.