This document provides information about the Acquia Web Governance accessibility check:
Is the heading descriptive enough?
What
A heading on a webpage must clearly describe the topic or purpose of the content that immediately follows it.
Why
Headings guide users through the content of a webpage. When a heading does not clearly describe the topic or purpose of the content that follows, users may become disoriented, particularly those who rely on assistive technologies like screen readers. For example, a vague or non-descriptive heading might cause a user to skip over important sections, believing they are irrelevant. Similarly, users who navigate quickly through headings to locate specific information may waste valuable time or miss key details if the headings are unclear. Clear and descriptive headings ensure that all users, regardless of their abilities, can efficiently locate and understand the information they need for a more seamless and inclusive browsing experience.
Who
This check affects users who have
Visual impairments: Who rely on screen readers to navigate a webpage. If the headings are unclear or non-descriptive, they may miss vital sections or struggle to understand the structure of the content.
Cognitive impairments: Who benefit from clear and descriptive headings to quickly understand the purpose of a section. This reduces confusion and improves focus.
User story
Bridgit is a blind mother to a five-year-old girl and an 11-year-old boy:
"As part of my job, I need to complete regular online training, like learning new customer service techniques. I usually do this in the evening after my kids have gone to bed. But navigating these platforms can be a nightmare! The headings are so vague, things like 'Module 1' or 'Topic A,' and they give me no clue what each section is about. I end up wasting so much time opening and listening to each section just to figure out if it is relevant. It is incredibly frustrating and eats into the little time I have left for myself after a long day balancing work and family life."
Examples
This section provides some examples of the issue.
Example: Blog page with non-descriptive headings
A blog section on a website displays a list of posts where the headings only indicate dates instead of a description of the content of each blog post. Only the date is marked as a heading, and this makes it non-descriptive. Screen reader users, who navigate through the page and understand the content by retrieving a list of headings, cannot get a quick overview of the page content or efficiently navigate to the desired article. Even though each article has a specific name, the screen reader only announces the date.
Example: Blog page with descriptive headings
A blog section on a website displays a list of posts where the headings clearly describe the content of each blog post. Even if users only see and navigate through a list of headings on the page, it is easy to get an overview of the content and navigate to the desired article.
Provide descriptive headings so that users who rely on screen readers can navigate the page efficiently.
How
This section provides information about how to review the issue.
How to review it
The Acquia Web Governance platform highlights all text snippets marked as headings for review. Assess the headings to determine if each heading accurately describes the content that immediately follows it. If the heading text gives users a clear understanding of the content it is meant to describe, mark this issue as "reviewed."
This document provides information about the Acquia Web Governance accessibility check:
Is the heading descriptive enough?
What
A heading on a webpage must clearly describe the topic or purpose of the content that immediately follows it.
Why
Headings guide users through the content of a webpage. When a heading does not clearly describe the topic or purpose of the content that follows, users may become disoriented, particularly those who rely on assistive technologies like screen readers. For example, a vague or non-descriptive heading might cause a user to skip over important sections, believing they are irrelevant. Similarly, users who navigate quickly through headings to locate specific information may waste valuable time or miss key details if the headings are unclear. Clear and descriptive headings ensure that all users, regardless of their abilities, can efficiently locate and understand the information they need for a more seamless and inclusive browsing experience.
Who
This check affects users who have
Visual impairments: Who rely on screen readers to navigate a webpage. If the headings are unclear or non-descriptive, they may miss vital sections or struggle to understand the structure of the content.
Cognitive impairments: Who benefit from clear and descriptive headings to quickly understand the purpose of a section. This reduces confusion and improves focus.
User story
Bridgit is a blind mother to a five-year-old girl and an 11-year-old boy:
"As part of my job, I need to complete regular online training, like learning new customer service techniques. I usually do this in the evening after my kids have gone to bed. But navigating these platforms can be a nightmare! The headings are so vague, things like 'Module 1' or 'Topic A,' and they give me no clue what each section is about. I end up wasting so much time opening and listening to each section just to figure out if it is relevant. It is incredibly frustrating and eats into the little time I have left for myself after a long day balancing work and family life."
Examples
This section provides some examples of the issue.
Example: Blog page with non-descriptive headings
A blog section on a website displays a list of posts where the headings only indicate dates instead of a description of the content of each blog post. Only the date is marked as a heading, and this makes it non-descriptive. Screen reader users, who navigate through the page and understand the content by retrieving a list of headings, cannot get a quick overview of the page content or efficiently navigate to the desired article. Even though each article has a specific name, the screen reader only announces the date.
Example: Blog page with descriptive headings
A blog section on a website displays a list of posts where the headings clearly describe the content of each blog post. Even if users only see and navigate through a list of headings on the page, it is easy to get an overview of the content and navigate to the desired article.
Provide descriptive headings so that users who rely on screen readers can navigate the page efficiently.
How
This section provides information about how to review the issue.
How to review it
The Acquia Web Governance platform highlights all text snippets marked as headings for review. Assess the headings to determine if each heading accurately describes the content that immediately follows it. If the heading text gives users a clear understanding of the content it is meant to describe, mark this issue as "reviewed."
Web Governance