Section Headings:
Understanding SC 2.4.10
2.4.10 Section Headings: Section headings are used to organize the content. (Level AAA)
Note: "Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content.
Note: This Success Criterion covers sections within writing, not user interface components. User Interface components are covered under Name, Role, ValueFor all user interface components, the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically determined and programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. This Success Criterion is primarily for Web authors who develop or script their own user interface controls. For example, standard HTML controls already meet this Success Criterion when used according to specification..
Intent of this Success Criterion
The intent of this Success Criterion is to provide headings for sections of a Web page, when the page is organized into sections. For instance, long documents are often divided into a variety of chapters, chapters have subtopics and subtopics are divided into various sections, sections into paragraphs, etc. When such sections exist, they need to have headings that introduce them. This clearly indicates the organization of the content, facilitates navigation within the content, and provides mental "handles" that aid in comprehension of the content. Other page elements may complement headings to improve presentation (e.g., horizontal rules and boxes), but visual presentation is not sufficient to identify document sections.
Specific Benefits of Success Criterion 2.4.9:
People who are blind will know when they have moved from one section of a Web page to another and will know the purpose of each section.
People with some learning disabilities will be able to use the headings to understand the overall organization of the page content more easily.
People who navigate content by keyboard will be able to jump the focus from heading to heading, enabling them to find quickly content of interest.
In pages where content in part of the page updates, headings can be used to quickly access updated content.
Examples of Success Criterion 2.4.10
A menu contains different sections for different courses. Each section has a heading: Appetizers, Salad, Soup, Entree, Dessert.
A Web application contains a settings page that is divided into groups of related settings. Each section contains a heading describing the class of settings.
Techniques and Failures for Success Criterion 2.4.10 - Section Headings
Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. The techniques listed only satisfy the Success Criterion if all of the WCAG 2.0 conformance requirements have been met.
Sufficient Techniques
Additional Techniques (Advisory) for 2.4.9
Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.
Using the 'live' property to mark live regions (future link) (ARIA)
Providing mechanisms to navigate to different sections of the content of a Web page (future link)
Failures for SC 2.4.9
The following are common mistakes that are considered failures of Success Criterion 2.4.9 by the WCAG Working Group.
(No failures currently documented)