Buttons Without Accessible Names

What This Means

One or more <button> elements (or elements with role="button") in the page have no accessible name — no visible text content, no aria-label attribute, and no aria-labelledby reference. The button's purpose is undescribed.

Why It Matters for SEO

Screen reader users hear a button announced as just "button" with no indication of what it does. This is a WCAG 2.1 failure (Success Criterion 4.1.2). For search engines, buttons without accessible names provide no textual signal about the interactive action they trigger — crawlers cannot understand the button's function or associated link target.

What the Platform Checks

The platform inspects all <button> elements and elements with button roles, checking for visible text content, aria-label, aria-labelledby, or title attributes. Fires when none of these provides an accessible name.

How to Fix It

• Add visible text inside the button: <button>Submit</button>.
• For icon-only buttons: add an aria-label describing the action: <button aria-label="Close dialog">✕</button>.
• For buttons with a referenced label: use aria-labelledby="element-id".
• Every button must have a human-readable name that describes what it does when activated.