Accessibility checking

Rocket Validator looks for accesibility violations on your pages using the axe-core accessibility engine, hosted on our own servers and integrated into our web crawler. You don't need to buy an additional license, everything's already included in your Pro account at Rocket Validator.

WCAG: Best Practice: Headings must not be empty

When at least one heading element (marked by <h1> through <h6>) is present, it is a best practice to ensure it contains content.

Screen readers alert users to the presence of a heading tag. If the heading is empty or the text cannot be accessed, this could either confuse users or even prevent them from accessing information on the page's structure.

If the text inside a heading cannot be accessed by a screen reader, users of this technology will not be able to hear the contents of the heading. Since headings relay the structure of a webpage, it's crucial that users of screen readers are able to access the contents.

Applying heading markup (<h1> through ><h6>) is a quick way to make text stand out, however, using it for anything other than headings will make navigating a web page more confusing for users of assistive technology.

In addition to making the page more accessible, headings have other benefits, since search engines use headings when filtering, ordering, and displaying results. Improving the accessibility of your site can also have the effect of making your page more findable.

In the same way that sighted users can glance at a page and get a sense of its contents, users of screen readers can do the same by navigating through headings. Well written and properly ordered headings can save users, especially those who use screen readers, a lot of time and frustration.

Learn more about this accessibility rule at Deque University >>

Validate accessibility and HTML5 on large sites, starting at $24/week. Start here