meaningful-button
Mobile validation
If a button lacks clear, descriptive text, users might not know what will happen when they activate it. This uncertainty can discourage or prevent someone from using the button.
Try It Yourself
Using a screen reader
New to screen reader testing, or need a refresher?
Review this article first: Practical guides for using screen readers
- Turn on VoiceOver on iOS, or TalkBack on Android.
- Swipe left or right to move to the button, and listen to the description. Expected results: The description is clear and descriptive. Actual results: The description is vague or repeated, so you cannot tell what the button does.
FAQ
How does this issue relate to 2.4.6 Headings and Labels
This issue relates to WCAG success criterion 2.4.6 because the text on a button acts as its label. The criterion expects labels to describe purpose. Clear, descriptive button text tells users what will happen before they activate it.
If a button’s text is missing or vague, people may not understand the result of activating it, and assistive technology may not announce a useful purpose. This creates an accessibility barrier and may not meet WCAG success criterion 2.4.6.
How does this issue relate to 3.3.2 Labels or Instructions
This issue aligns with 3.3.2 because clear, descriptive button text acts as a label or instruction that sets expectations before you activate the control. It tells users what will happen, which reduces confusion and supports informed action.
When a button lacks meaningful text, people may hesitate or avoid using it. Clear text helps people with disabilities and assistive technology users understand the purpose of the button and decide whether to proceed.
Why is this issue marked as Moderate?
This issue is marked as Moderate because unclear or missing button text makes the outcome unpredictable. Some people will not know what will happen when they activate the button, which can block use of that control. The impact is typically limited to the affected button rather than the entire experience.
Clear, descriptive button text supports people who use assistive technology and reduces errors for everyone. While the scope may be narrow, you should address it promptly to maintain a reliable, understandable interface.
Standards and Regulations
| Standard | Success Criterion | Reference |
|---|---|---|
| WCAG 2.2 | 2.4.6 Headings and Labels (AA) | Headings and labels describe topic or purpose. |
| WCAG 2.2 | 3.3.2 Labels or Instructions (A) | Labels or instructions are provided when content requires user input. |
| EN 301 549 | 11.2.4.6 Headings and Labels | Same as the WCAG text. |
| EN 301 549 | 11.3.3.2 Labels or Instructions | Same as the WCAG text. |