This Wiki page is edited by participants of the WCAG Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Edits to Add 2.4.10 to H69

Jump to: navigation, search

  1. REDIRECT Target page name



Add 2.4.10 Section Headings to the applicability section for this technique.


The description as it stands is very well suited to 2.4.10, arguably more so than for 2.4.1 which is already associated with this technique.

The full description as it currently stands is below, changes are marked with "@@":

The objective of this technique is to use section headings to convey the structure of the content. Heading markup can be used:

  • to indicate start of main content
  • to mark up section headings within the main content area
  • to demarcate different navigational sections like top or main navigation, left or secondary navigation and footer navigation
  • to mark up images of text that are used as headings (@@ delete this one as it is off-topic here)
  • @@to allow users the ability to navigate a page by sections or skip repeated blocks of information

Headings are designed to convey logical hierarchy. Skipping levels in the sequence of headings may create the impression that the structure of the document has not been properly thought through or that specific headings have been chosen for their visual rendering rather than their meaning. Authors are encouraged to nest headings hierarchically. When headings are nested hierarchically, the most important information is given the highest logical level, and subsections are given subsequent logical levels.(i.e., h2 is a subsection of h1). @@Providing this type of structure will help users understand the overall organization of the content more easily.

Since headings indicate the start of important sections of content, it is possible for users with assistive technology to jump directly to the appropriate heading and begin reading the content. This significantly speeds interaction for users who would otherwise access the content slowly. Headings create chunks of information that can be found easily by people with disabilities, such as a blind person using a screen reader, or a person with a cognitive disability who uses assistive technology that delineates groups of information, or someone with a communication disability or illiteracy, who uses a screen reader to assist them in their reading.

Note: All of our techniques assume that people needing special user agents (including AT or special plug-ins) will get and be using that type user agent (eg screen reader, or plug-in that allows keyboard navigation of properly marked up content, etc).


Currently the procedure reads: For all content which is divided into separate sections,

  1. Check that each section starts with a heading.

Change to:

  1. Check that the content is divided into separate sections
  2. Check that each section on the page starts with a heading
  • For 2.4.1 check #2 is true.
  • For 2.4.10 checks #1 and #2 are true.