Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure tables have unique accessible names. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
68
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
When multiple tables are present, unique names allow users of assistive technology to quickly identify and navigate to the data they need.
<caption> or aria-labelVerify that every table has a unique accessible name via caption or ARIA attributes.
Add a unique <caption> or aria-label to the table.
Explain why unique table names are necessary for users who rely on screen readers to navigate complex data.
Review the rendered markup and interactive states that affect Ensure tables have unique 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/table-duplicate-name
48405aa
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.