Button Name Checker
Paste your page HTML and find empty, icon-only and title-only controls — unnamed buttons fail WCAG 4.1.2.
What this tool gives you
Check button names
Paste your page HTML. Analysis runs locally in your browser — nothing is sent anywhere.
Empty and icon-only buttons fail WCAG 4.1.2. Name them with visible text or aria-label, and set type so they do not submit forms by accident.
What this checker looks for
A control without a name is announced as "button" — users cannot tell Close from Submit.
Empty buttons
No text, aria-label, labelledby, alt or value.
Icon-only
SVG or icon font with no accessible name.
Title-only
title= is a tooltip, not a name — AT often skips it.
Missing type
<button> defaults to submit and will post the nearest form.
role="button"
Custom widgets need the same name as a real button.
0–100 score
Track unnamed controls across templates and CMS partials.
How to name every button
Visible text first. aria-label only when the control is an icon.
Prefer visible text
Put the action in the button. Sighted and AT users then hear the same name.
Label icons
Icon-only controls get aria-label="Close" (or the real action), not title=.
Set type
type="button" unless the control should submit. The HTML default is submit.
Why answer engines care about named controls
Named buttons are a cheap-to-parse signal that interactive UI was designed, not dumped.
| Signal | What engines infer | Why it helps |
|---|---|---|
| Named buttons | Every control has an action. | Usable UI lowers abandonment on AI-referred visits. |
| Labeled icons | Icon fonts were designed, not forgotten. | Consistent conventions make parsing predictable. |
| Explicit type | Forms will not submit from chrome buttons. | Trustworthy interactive pages get quoted more often. |
| WCAG 4.1.2 pass | Name, Role, Value is met. | Citable, accessible pages survive answer-engine filters. |
| No title-only | Names work without a mouse. | Keyboard and touch users hear the same copy. |
Related GEO pages
Named buttons pair with form labels and focus outlines so keyboard users can act.
Button name FAQs
Why do empty buttons fail accessibility?
WCAG 4.1.2 (Name, Role, Value) requires every control to expose a name. An empty <button> is announced as "button" with no action. Users cannot tell Close from Submit or Menu.
How should icon-only buttons be named?
Keep the icon for sighted users and add aria-label with the action ("Close", "Search", "Open menu"). Image-only buttons can use alt on the <img>. Do not rely on title= — it is a mouse tooltip and often ignored by assistive tech.
Why set type on every button?
The HTML default for <button> is type="submit". An unlabeled icon button inside a form will post the form when activated. Set type="button" unless the control is meant to submit.