Forms and controls
button-name
WCAG 4.1.2 Name, Role, Value Level A
Who this affects
This button has no text, so a screen reader announces "button" with no indication of what it does.
How to fix it
Put text inside the button. If it is icon-only, add an aria-label describing the action, such as "Close dialog".
How much work is it?
Usually a content edit. That is a rough guide for planning, not an estimate for your codebase. A single content edit repeated across a template is a template change.
What a person still has to check
Passing this rule does not mean 4.1.2 passes. Automation checks part of the criterion, and the rest is a judgement:
Use a screen reader on each custom control and confirm its name, role, and state are announced.
Read 4.1.2 Name, Role, Value in plain language
Where this check comes from
This is an axe-core rule. We run axe in a real browser on every page we scan. Deque’s reference for button-name
Find out whether your site does this
A scan checks this rule on every page it visits, and shows you the code and a screenshot of each place it fires.