Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →thedaviddias/button-name
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for buttons. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Passed 21 of 22 test cases with the skill, and 19 of 22 without it.
2 fixed19 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our automated accessibility audit flagged several interactive elements in our main navigation bar, specifically an icon search element and a quick-action trigger. Please analyze this HTML snippet and refactor it so assistive technologies can properly announce all interactive elements.
| Checked | Without skill | With skill |
|---|---|---|
| The response explains why buttons trigger actions while links handle page navigation. | Missed | Passed |
| The response explains how to verify the accessibility fix using browser accessibility tooling. | Missed | Passed |
The instructions your model reads when the skill loads.
Buttons without accessible names are announced as 'button' by screen readers, leaving users unable to determine what action will be triggered.
Scan for buttons that lack descriptive text or accessible labels.
Add an accessible name to the button using text content, an aria-label, or an aria-labelledby reference. If the element navigates to another URL, replace the button with a link instead of keeping button semantics.
Explain why accessible names are critical for screen reader users to identify and interact with buttons, and why buttons should trigger actions while links should handle navigation.
Review the rendered markup and interactive states that affect Provide accessible names for buttons. Flag exact elements, roles, labels, focus behavior, or keyboard interactions that violate the rule, and note how to verify the fix with browser accessibility tooling or assistive tech.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/accessibility/button-name
test cases passed, vs 19 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.