table-headers
/table-headers
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Define proper table headers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
- Author
- thedaviddias ↗
- Repository
- front-end-checklist ↗
- Licence
- MIT
- Last repository change
- 06.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Define proper table headers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
Original author description
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Define proper table headers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
How it works
- Quick Reference
- Check
- Fix
- Explain
- Code Review
SKILL.md preview
--- name: table-headers description: "Use when reviewing rendered HTML, interactive components, or design-system patterns related to Define proper table headers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant." metadata: category: accessibility priority: medium difficulty: intermediate estimatedTime: "10" source: frontendchecklist.io url: https://frontendchecklist.io/rules/accessibility/table-headers --- # Define proper table headers Properly defined headers allow screen readers to announce the context for each data cell, making complex tables understandable. ## Quick Reference - Use `<th>` for all table headers, not `<td>` - Apply `scope="col"` or `scope="row"` to clarify header relationship - Ensure every data cell is associated with at least one header - In simple tables, prefer fixing header associations before escalating to caption-level recommendations - Missing `scope="col"` on a straightforward header row is often the clearest first fix ## Check Check that all data tables use `<th>` elements for headers with appropriate scope attributes. ## Fix Convert header cells to `<th>` and add the correct `scope` attribute. ## Explain Explain how `<th>` and `scope` help assistive technologies communicate the structure of data tables. ## Code Review Review the rendered markup and interactive states that affect Define proper table headers. 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/table-headers
Files in this package (2)
- SKILL.md 2 KB
- references/rule.md 2 KB
Versions
The database has no other skills named table-headers.
Database snapshot: 13.11.2026 · package version 769cf99ce08d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100table-duplicate-name
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. - 100th-has-data-cells
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Ensure table headers associate with data cells. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.