2. Use Headings to Create Structures
Headings in content allow readers to organize chunks of content and to navigate the content. A sighted user has the ability to discern headings based on attributes such as: size, spatial relationships, color, positioning, case, and punctuation to determine which text is a heading and what text relates to that heading. We must offer that same level of functionality to the non-sighted person who uses a screen reader. A non-sighted person can pull up a list of headings via their screen reader to navigate a document like an interactive table of contents. Manually formatting heading text does not offer a programmatic equivalent to the non-sighted person using a screen reader. This denies them the ability to programmatically scan the content in a way similar to a sighted person who can rely on size, spatial relationships, color, positioning, case, and punctuation to determine which text is a heading and which text relates to that heading. It is also important to provide semantic understanding to headings and to maintain an outline level hierarchy of the headings in a piece of content.
- Use the heading styles provided in a Drupal template
- Do not override text styles with manual formatting to simulate headings
- Do not skip headings (i.e., do not jump from h2 to h4, instead move from h2 to h3 and then to h4)
- Only use only one h1 per page