杏吧原创

Skip to Content

Always give a page a proper hierarchy

Accessibility

Page hierarchy is created by using a set of nesting subheadings. These create a way a page can be read by a screen reader, or by a user who scans the page visually. It allows people to understand the importance and types of information on a page.

Reason

Best practice

The way to organize information using subheaders can easily seen in this example:

Heading 1 Places to eat [The Page as a whole]

Heading 1 for a page is always the page title and there can only be one instance of this.

If you were using a screen reader and wanted to eat off-campus you would skip from the first Heading 2 section to the second (“Off-campus”) and skip through its subheadings until you heard the name of the restaurant you want to eat at. You could then access all the information listed there.

On a page accessed visually there is an immediately visible cue: the subheadings are different sizes – the lower down the hierarchy, the smaller the subheading.

Example of less accessible practices

There are a few different ways in which use of hierarchy can make life more difficult for people to success information.

Skipping a level would look like:

Heading 1 Places to eat

The hierarchy being in the incorrect order would look like this, for example:

Heading 1 Places to eat

Instantly, the user will be confused by what they see or hear.

See also:

Pro tip

You can view the structure of the page in cuTheme. When editing a page or post, click on the Document view icon in the top left. It is a black square with three white lines on it. Next click on the Outline tab. You will see something that looks like this:

The outline displays a list of all the section sub-headings on the page, indented if they are sub-sections of a heading.

Additional benefits

What WCAG says

WCAG outlines the use of headings in . (They refer to headings as “h1” to “h6”.)

(Be sure to .)

From WCAG:

“Heading markup will allow assistive technologies to present the heading status of text to a user. A screen reader can recognize the code and announce the text as a heading with its level, beep or provide some other auditory indicator… if a document can be broken up into sections with headings, it facilitates both understanding and navigation.”