Skip to content
Back to skills

Aria Labels

ASecurity

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for all interactive elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

  • 74,358 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 5, 2026
developmentgofrontend

Works with

  • cli

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add thedaviddias/Front-End-Checklist --skill aria-labels --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Aria Labels?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Aria Labels
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedaviddias-aria-labels/badge)](https://www.skillsdirectory.com/skills/thedaviddias-aria-labels)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: aria-labels
description: "Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide accessible names for all interactive elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant."
metadata:
  category: accessibility
  priority: high
  difficulty: intermediate
  estimatedTime: "10"
  source: frontendchecklist.io
  url: https://frontendchecklist.io/rules/accessibility/aria-labels
---

# Provide accessible names for all interactive elements

Interactive elements are the core of web navigation; without names, they become 'mystery meat' that users cannot confidently interact with.

## Quick Reference

- Buttons, links, and other controls must have a discernable name
- Names should be concise and describe the action or destination
- Avoid generic names like 'Click Here' or 'More'

## Check

Audit all interactive elements (buttons, links, widgets) for missing or unhelpful accessible names.

## Fix

Add descriptive text content or `aria-label` attributes to all interactive elements.

## Explain

Explain how clear labels on interactive elements improve accessibility and general usability.

## Code Review

Review the rendered markup and interactive states that affect Provide accessible names for all interactive elements. 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/aria-labels

Files in this skill

  • SKILL.md1.7 KB
  • references/rule.md2.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…