Loading skill
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 Ensure headings contain text. 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-01 | ✗→✓ | ▲ Improved | 12% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -8% | 0% |
| case-15 | ✗→✓ | ▲ Improved | -16% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | 0% | 0% |
| case-04 | ✓→✓ | ＝ Same ✓ | 10% | 0% |
Empty headings create 'ghost' stops in the document outline, confusing users who rely on headings to navigate and understand the page structure.
Find any heading tags (h1 through h6) that are empty or contain only non-perceivable whitespace.
Add descriptive text content to the empty heading or remove the heading tag if it's not needed.
Explain why meaningful heading content is vital for document navigation and accessibility.
Review the rendered markup and interactive states that affect Ensure headings contain text. 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/empty-heading
Other measured skills in the registry, with their headline benchmark lift.