Skip to content
Get packs

ARIA Command Name Checker

Reviews interactive HTML so buttons and links have clear accessible names for screen readers.

Source Download skill
Repository
thedaviddias/Front-End-Checklist
Stars
74,632
Licence
MIT
Files
2 files

What it does

When installed, the agent reviews web page markup and interactive components to check that buttons, links, and menu items have a label that screen reader users can hear. It checks native HTML semantics first, then looks for missing names and suggests fixes using text content, aria-label, or aria-labelledby. The skill is a set of written review instructions; it does not itself run tests on a site.

Great for

  • Front-end developers reviewing components for accessibility
  • Designers or QA reviewers checking a design system for unlabeled controls
  • Teams preparing an accessibility audit of a web interface

Skip it if

  • People who need a fully automated accessibility scan, since this relies on the agent reading markup rather than running a testing tool
  • Non-web projects with no rendered HTML, where the guidance does not apply

Try asking

  • “Review this login page HTML and tell me which buttons or links lack an accessible name.”
  • “Check my icon-only toolbar buttons for aria-label issues and suggest fixes.”
  • “Audit this dropdown menu component for menuitem elements without labels.”
Step-by-step guide: how to use ARIA Command Name CheckerInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 2 original files, the MIT licence and an attribution note.

    aria-command-name.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip aria-command-name.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip aria-command-name.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Paste the rendered HTML or component code, not just the source template, so the agent sees the final output.
  • Ask the agent to also verify fixes with browser accessibility tools or a screen reader, since the skill only reviews markup.
  • Combine with keyboard and focus checks for a fuller accessibility review.

What's inside

  • references/rule.md
  • SKILL.md

Redistributed unmodified from thedaviddias/Front-End-Checklist under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.