Headers or titles in ArcGIS StoryMaps are read out with the wrong header labels (h1, h2, h3...) when using a screen reader, violating WCAG guidelines of logical heading order.
ArcGIS StoryMaps
漏洞 ID 编号
BUG-000178183
已提交
July 24, 2025
上次修改时间
August 7, 2025
适用范围
ArcGIS StoryMaps
找到的版本
June 2025
操作系统
Windows OS
操作系统版本
11.0 64 bit
状态
As Designed
经开发团队审核,已确定此行为符合设计。 有关详细信息,请参阅“其他信息”部分。
附加信息
ArcGIS StoryMap builders are designed for a broad audience, many of whom may not be familiar with basic accessibility concepts. For this reason, an intentional re-mapping exists between the “headings” created in the builder and the semantic HTML headings coded into the resulting web page for screen reader use.
From the author’s perspective, it would seem inconsistent if the first heading level in the body of the story were called “Heading 2.” However, from a screen reader perspective, the first heading level in the body after the title (which must be an
) must be
. For this reason, the “Heading 1” displayed in the builder corresponds to
in the HTML code.
The screen reader reads the intended heading hierarchy correctly because the headings are coded with the appropriate HTML elements to ensure sequential usage. Authors are advised to use the headings provided in the body of the story in a straightforward, sequential order starting with Heading 1, followed by Heading 2 and Heading 3 as needed.
A future update is planned to enhance ArcGIS StoryMaps documentation with details on how headings function with screen readers, in order to address any confusion that may arise for authors who are highly familiar with accessibility guidelines.