CtrlK
BlogDocsLog inGet started
Tessl Logo

label-content-name-mismatch

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

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/label-content-name-mismatch/SKILL.md
SKILL.md
Quality
Evals
Security

Align visible labels with accessible names

When the visible label doesn't match the accessible name, voice control users may find it impossible to interact with the element by speaking its name.

Quick Reference

  • Visible text should be part of the accessible name (ARIA label)
  • Ensure speech-to-text users can trigger controls by their visible name
  • Maintain consistency between what is seen and what is read by tech

Check

Compare the visible text of buttons and links with their 'aria-label' or 'aria-labelledby' attributes to ensure the visible text is included in the accessible name.

Fix

Update the ARIA attribute to include the exact string of the visible label text at the beginning of the accessible name.

Explain

Explain how a mismatch between visible labels and accessible names breaks the experience for users of voice recognition software.

Code Review

Review the rendered markup and interactive states that affect Align visible labels with accessible names. 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/label-content-name-mismatch

Repository
thedaviddias/Front-End-Checklist
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.