Ensure tables have unique accessible names
SkillMediatable-duplicate-name is a skill for AI agents that reviews rendered HTML, interactive components, and design-system patterns related to Ensure tables have unique accessible names. It guides an agent to check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output. The result is web page tables that each have a unique accessible name announced correctly by screen readers.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an AI agent that can load and use skills.
Then ask your AI: use the Ensure tables have unique accessible names skill
What your AI can do with it
- Review rendered HTML tables for duplicate accessible names
- Check native table semantics before deeper inspection
- Inspect keyboard behavior and focus flow on components
- Evaluate accessible names on interactive components
- Assess screen-reader output where relevant
- Review design-system patterns for accessible table naming
Getting started
- Have an AI agent that can load and use skills.
- Add the table-duplicate-name skill to the agent's available skills.
- Ask the agent to review a rendered HTML page, component, or design-system pattern for tables with duplicate accessible names.
- The agent checks native semantics first, then keyboard behavior, focus flow, accessible names, and screen-reader output.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/table-duplicate-name/SKILL.md and read by ahel’s review.
When multiple tables are present, unique names allow users of assistive technology to quickly identify and navigate to the data they need.
Quick Reference
- Each data table must have a unique
<caption>oraria-label - Helps screen reader users distinguish between multiple tables
- Avoid repetitive or generic names like 'Table 1'
Check
Verify that every table has a unique accessible name via caption or ARIA attributes.
Fix
Add a unique <caption> or aria-label to the table.
Explain
Explain why unique table names are necessary for users who rely on screen readers to navigate complex data.
Code Review
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
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- When should this skill be used?
- Use it when reviewing rendered HTML, interactive components, or design-system patterns related to ensuring tables have unique accessible names.
- What does the skill check?
- It checks native semantics first, then inspects keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
- What problem does it solve?
- It helps ensure each table on a web page has a unique accessible name that screen readers announce correctly.
Advanced
- Item type
- skill
- Key
table-duplicate-name- Source
- github.com/thedaviddias/front-end-checklist