How to Structure Headings for Better Accessibility
Proper heading structure improves navigation for screen readers and keyboard users. Headings should be meaningful, follow a logical order, and help people understand content at a glance. Use this checklist to ensure headings are implemented correctly.
10-Point Headings Accessibility Checklist
Number One: Use headings to define page structure
Headings should outline the page’s main topics. Do not use bold text as a replacement for proper headings.
Number Two: Follow a logical heading order
Use <h1> for the main title, followed by <h2>, <h3>, etc. Never skip heading levels (e.g., jumping from <h2> to <h4>).
Number Three: Each page has a single <h1>
The <h1> should describe the page’s main topic. Do not use multiple <h1> elements unless it is a multi-section document.
Number Four: Headings provide clear meaning
Ensure each heading describes the section content. Avoid vague headings like "Click Here" or "More Info."
Number Five: Do not use headings for styling
Headings should not be used just for bold or large text. Use CSS for visual styling instead of choosing a heading level based on appearance.
Number Six: Avoid empty heading tags
Every heading must contain meaningful text. Do not leave <h2></h2> or similar tags empty.
Number Seven: Headings improve screen reader navigation
Test heading structure with a screen reader to ensure proper hierarchy. People using assistive technology should be able to navigate by headings alone.
Number Eight: Headings are used consistently across the site
Maintain a predictable structure across all pages. Keep heading usage consistent in similar sections.
Number Nine: Use headings to break up long content
Long paragraphs should be divided into smaller, scannable sections with headings. This improves readability for all people, including those with cognitive disabilities.
Number Ten: Test headings with a document outline tool
Use browser extensions or developer tools to check the heading structure. Ensure headings create a clear and logical content outline.
Support my work in accessibility
Creating accessible content takes time, care, and deep testing — and I love every minute of it. From writing blog posts to doing live audits and building checklists, everything I create is designed to make the digital world more inclusive.If something here helped you — whether it saved you time, taught you something new, or gave you insight into accessibility — consider supporting my work.
You can buy me a coffee to help keep this platform going strong:
Buy Me a Coffee
Every coffee goes toward:
- Creating new articles with accessibility tips, tools, and testing methods
- Covering hosting, software, and assistive tech costs
- Supporting free education for designers, developers, and testers
- Making a meaningful difference for people living with disabilities
Thanks for being part of this mission to build a more accessible web — one page at a time.