Maintain logical heading order
SkillMediaHeading-order is a skill for AI agents that reviews rendered HTML to check whether headings follow a logical sequence. It flags skipped heading levels, such as an h2 appearing after an h1, and suggests fixes during code review. A clear heading hierarchy helps screen reader users move through page content.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an AI agent that can load and use skills.
Then ask your AI: use the Maintain logical heading order skill
What your AI can do with it
- Reviews rendered HTML to confirm heading levels h1 through h6 follow a logical sequence
- Flags skipped heading levels, such as an h2 coming after an h1 rather than jumping past it
- Reports violations during code review and suggests fixes
- Explains why a clear heading hierarchy helps screen reader users navigate content
- Checks native semantics first, then keyboard behavior, focus flow, accessible names, and s
Getting started
- Have an AI agent that can load and use skills.
- Add the heading-order skill to the agent's available skills.
- Ask the agent to review a rendered HTML page, interactive component, or design-system pattern for heading order.
- Review the flagged violations and suggested fixes in the agent's output.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/heading-order/SKILL.md and read by ahel’s review.
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
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- When should this skill be used?
- Use it when reviewing rendered HTML, interactive components, or design-system patterns related to maintaining logical heading order.
- What does it check?
- It checks that heading levels h1 through h6 follow a logical sequence without skips, and inspects native semantics first, then keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
- Why does heading order matter?
- A clear heading hierarchy helps screen reader users move through page content.
- Does it fix the issues automatically?
- It flags violations and suggests fixes, explaining why they matter; it does not apply changes on its own.
Advanced
- Item type
- skill
- Key
heading-order- Source
- github.com/thedaviddias/front-end-checklist