How do I install the Button Name skill?

Run npx skillmds@latest add thedaviddias/button-name in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Button Name safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Button Name?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Button Name free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Button Name?

thedaviddias (@thedaviddias) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Button Name by thedaviddias — Agent Skill

Name: Button Name
Author: 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.

thedaviddias 3cb4fc4 2 files · 4.9 KB Updated Sep 17, 2026

File contents

Provide accessible names for buttons

Buttons without accessible names are announced as 'button' by screen readers, leaving users unable to determine what action will be triggered.

Quick Reference

Ensure every has a discernible, descriptive label
Use inner text, aria-label, or aria-labelledby for identification
Use buttons for actions and state changes, not page navigation
Avoid empty buttons or those containing only non-text icons

Check

Scan for buttons that lack descriptive text or accessible labels.

Fix

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

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.

Code Review

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/en/rules/accessibility/button-name

Frequently asked questions