Fix · Serious · cited in audits
How to fix: empty buttons / icon-only buttons
Screen reader announces "button" with no purpose. Buttons need a programmatic name.
- WCAG references
- 4.1.2
- Severity
- Serious
What it looks like in the wild
Screen reader announces "button" with no purpose.
The screen-reader user, keyboard user, or low-vision user encountering this issue does not get an error message. The page just stops working for them. Which is why this kind of bug rarely shows up in your error tracker; it shows up in support tickets, lawsuits, and abandoned conversions.
Why it fails WCAG
Buttons need a programmatic name.
Map this back to 4.1.2 when you log the bug. Auditors and procurement teams expect that mapping; "broken" is not enough context.
The wrong pattern (avoid)
HTML
<button><svg>...</svg></button>The right pattern (copy this)
HTML
<button aria-label="Open notifications">
<svg aria-hidden="true">...</svg>
</button>Notes from real audits
aria-hidden on the SVG prevents double announcement.
Related fixes
Find every accessibility issue on your site in 60 seconds.
Free public scan. No card. AI-generated fixes for every issue we find.