Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-16 | ✗→✓ | ▲ Improved | 31% | 0% |
| case-01 | ✓→✓ | = Same ✓ | 48% | 0% |
| case-02 | ✓→✓ | = Same ✓ | -11% | 0% |
| case-03 | ✓→✓ | = Same ✓ | 65% | 0% |
| case-04 | ✓→✓ | = Same ✓ | 5% | 0% |
Properly defined headers allow screen readers to announce the context for each data cell, making complex tables understandable.
<th> for all table headers, not <td>scope="col" or scope="row" to clarify header relationshipscope="col" on a straightforward header row is often the clearest first fixCheck that all data tables use <th> elements for headers with appropriate scope attributes.
Convert header cells to <th> and add the correct scope attribute.
Explain how <th> and scope help assistive technologies communicate the structure of data tables.
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/en/rules/accessibility/table-headers
Other measured skills in the registry, with their headline benchmark lift.