CtrlK
BlogDocsLog inGet started
Tessl Logo

heading-order

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Maintain logical heading order. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

58

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/heading-order/SKILL.md
SKILL.md
Quality
Evals
Security

Maintain logical heading order

A logical heading structure allows screen reader users to navigate the page content efficiently and helps all users understand the relationship between different sections.

Quick Reference

  • Use heading levels (<h1>-<h6>) in sequential order
  • Do not skip heading levels (e.g., <h1> followed by <h3>)
  • Ensure the document structure is logical and hierarchical

Check

Check the heading structure of the page to ensure that heading levels are not skipped (e.g., check that an

follows an

).

Fix

Adjust the heading levels to ensure a correct hierarchy (e.g., change an

to an

if it follows an

).

Explain

Explain how a consistent heading hierarchy aids navigation for screen reader users who rely on heading lists to understand page layout.

Code Review

Review the rendered markup and interactive states that affect Maintain logical heading order. 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/heading-order

Repository
thedaviddias/Front-End-Checklist
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.