Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Overview

Create a logical reading order for vision impaired users who rely on using assistive technology such as a screen reader to access online content.

Provide screen reader users with properly nested headings.

Screen reader and other assistive technology users frequently navigate web pages by heading structure.

These users can pull up a list of all the headings on a page to get a quick overview of the type of content that is available.

Headings should primarily be used to describe larger sections of content.

Headings should not be applied to text labels and links that are bolded and do not describe a section of content.

Page Structure and Headings

  • Create a logical reading order by using properly nested headings in your markup, <h1> <h2> <h3> <h4> <h5> <h6>. 

  • Build the structure of the page using semantic markup. Markup that has meaning to browsers and screen readers. A web page should be able to stand on its own without the help of a style sheet.

  • Sighted users often scroll the page quickly and look for headings to get an idea of the structure and content of the page. Screen reader and other assistive technology users also have the ability to navigate web pages by heading structure, assuming true headings are used (as opposed to text that is styled to be big and/or bold). This means that the user can view a list of all of the headings on the page, or can read or jump by headings, or even navigate directly to top level headings (<h1>), next level headings (<h2>), third level headings (<h3>), and so on.

  • There should only be one <h1> heading per page and should be applied to the page title to indicate to the user that this is where the content area begins. 

  • Headings should be structured in a hierarchical manner. 

Proper Nesting of Headings 

<h1>Page Title</h1>
      <h2>Heading Two</h2>
            <h3>Heading Three</h3>
            <h3>Heading Three</h3>
            <h3>Heading Three</h3>
                  <h4>Heading Four</h4>
                  <h4>Heading Four</h4>
      <h2>Heading Two</h2>
            <h3>Heading Three</h3>
            <h3>Heading Three</h3>
            <h3>Heading Three</h3>
                  <h4>Heading Four</h4>
                  <h4>Heading Four</h4>
      <h2>Heading Two</h2>
            <h3>Heading Three</h3>
            <h3>Heading Three</h3>
            <h3>Heading Three</h3>
                  <h4>Heading Four</h4>
                  <h4>Heading Four</h4>                                                            

Provide Descriptive Headings and Labels

General Guidelines

Help users understand what information is contained in Web pages and how that information is organized by providing descriptive headings.

When headings are clear and descriptive, users can find the information they seek more easily, and they can understand the relationships between different parts of the content more easily.

Descriptive labels help users identify specific components within the content.

Labels and headings do not need to be lengthy. A word, or even a single character, may suffice if it provides an appropriate cue to finding and navigating content.

Screen Reader Guidelines

Screen reader users frequently navigate web pages by heading structure. These users can pull up a list of all the headings on a page to get a quick overview of the type of content that is available.

This requires headings to be descriptive enough so that screen reader users can quickly get an overview of the type of content that is available on the page.

Lists

  • HTML lists - <ul>, <ol>, and <dl> - also convey a hierarchical content structure.

  • Lists should be used to display actual list items. They should not be used for layout purposes.

WCAG Related References

1.3.1 Info and Relationships (Level A)

  • No labels