Skip to content

thedaviddias/Front-End-Checklist / skills/table-duplicate-name

table-duplicate-name

Verified

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.

FileKindSize
SKILL.mdskill md1.7 KB
references/rule.mdmarkdown2.2 KB

references/rule.md

View on GitHub
# Ensure tables have unique accessible names

> Checks that data tables have unique accessible names

**Priority:** medium · **Difficulty:** intermediate · **Time:** 10 min

---
Accessible names for tables provide context for users of assistive technologies, especially when a page contains multiple tables.

## Code Example

```html
<!-- ✅ GOOD: Using <caption> -->
<table>
  <caption>Monthly Sales Data (2023)</caption>
  <thead>...</thead>
  <tbody>...</tbody>
</table>

<!-- ✅ GOOD: Using aria-label -->
<table aria-label="Employee Directory">
  <thead>...</thead>
  <tbody>...</tbody>
</table>
```

## Why It Matters

- **Navigation**: Screen reader users can pull up a list of tables; unique names help them choose the right one.
- **Context**: Explains what the data represents before the user starts diving into rows and columns.
- **Clarity**: Prevents confusion when similar-looking tables are used for different purposes.
- **Compliance**: Supports WCAG requirements for providing names for structural elements.

## Exceptions

- Simple data tables can sometimes fail more from missing header relationships than from missing enhancements such as captions or mobile wrappers, so prioritize the strongest semantic issue.
- Do not convert layout structures into data-table markup just to satisfy a rule; the correct fix may be to remove table semantics entirely.
- When several table-accessibility issues overlap, resolve the header-cell relationship first because downstream announcements depend on it.

## Standards

- Align the implementation with W3C WAI: WCAG Overview and verify the rendered experience, not only the source code.
- Align the implementation with MDN: Accessibility and verify the rendered experience, not only the source code.

## Verification

### Automated Checks

- Inspect the browser accessibility tree or accessibility pane for the relevant element, role, or accessible name.
- Run an automated accessibility checker such as axe or Lighthouse where applicable.

### Manual Checks

- Test the affected UI with keyboard-only navigation and confirm the rule holds in the rendered experience.
- Re-test one representative user flow with a screen reader if this rule affects a key interaction.
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 322kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall