Accessible foundations - Headings
Headings are an good part of making content accessible. They break down content into well identified parts, easier to digest. They also provide important shortcuts for assistive technology users. In the 2019 WebAIM Screen Reader User Survey, 68.8% of the respondents said they use headings to find their way through the pages. Indeed, screen readers (for example) provide a list of all the page headings and ways to jump between them, allowing users to quickly get to a section they'd be interested in.
For that to happen, though, making some text larger and/or bolder is irrelevant. Only sighted users will interpret that as a heading. Machines need semantic markup to tell with certainty that a particular piece of text is a heading.
This is the role of the
<h6> tags in HTML, each number representing the level of the heading.
<h2> start subsections of the previous
<h3> of the previous
<h2>... Creating a clear outline with these elements, with coherent levels (no skipping, for example), helps users skim through the page.
It's technically possible to have more than one
<h1> on a page. However, having only one, usually announcing the topic of the page, gives a clear point of entry. On this page, the title of the article, for example.
This doesn't mean it needs to be the first heading. Sections of the header, can be introduced with an
<h2>, for example. This doesn't mean it needs to be the boldest/largest piece of text on the screen either. Here, it's more of a design concern, but it can be particularly useful for more app-like designs.
Managing heading levels
Past that main
<h1>, there's no avoiding managing the level of each heading to ensure a correct hierarchy. You might have encountered HTML5's proposal of using sectioning elements and only
<h1>s to compute the heading's hierarchy. Unfortunately, this never got implemented by browsers.
<h3>... are still very much needed.
This becomes a concern when some content gets to come from different sources, or rendered at different heading levels (on separate pages). On this article, for example, the
<h1> comes from metadata in the file's front-matter.
title: Accessible foundations - Headings
The rest of the headings comes from the compiled Markdown. The catch is to start the headings in the Markdown at the second level.
## Second level heading
Second level heading
I tend to prefer this last one, actually ;)
Easy enough for one person, especially when it's the one building the site. It doesn't really scale when we're talking of multiple people adding content to a CMS, for example.
No magic solution to offer here ,though (happy to learn of one if you have it). Maybe automatically shifting heading levels to the right depth can help a bit. Limiting options and adding validations in the CMS could also be worth exploring. For example, not providing anything in the menus to insert a
<h1> if already generated elsewhere, or display an educational error message if the heading hierarchy looks off.
Checking the heading hierarchy
Hunting each heading in the middle of all the markup doesn't feel like much fun. Fortunately, there's other ways to checks that headings are ordered properly.
I like the headingsMap extension for Firefox (also available for Chrome) to quickly give a glance at the list of headings. It'll highlight headings which are out of place in the hierarchy, as well. This is also something that the Axe extension will do (among other accessibility checks).
And there's always the option to look at the lists detected by screen-readers. Both Mac, Windows 10 and Ubuntu come with one built in, and NVDA can be freely installed on Windows.
In complement of headings, there are other ways to help navigation inside a page for assistive technologie users. Definitely enough to fill the next article, which will deal with ARIA landmarks.