Bogue
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.
| Numéro d’ID de bogue | BUG-000178183 |
|---|---|
| Envoi | July 24, 2025 |
| Dernière modification | August 7, 2025 |
| S’applique à | ArcGIS StoryMaps |
| Version trouvée | June 2025 |
| Système d’exploitation | Windows OS |
| Version du système d’exploitation | 11.0 64 bit |
| Statut | As Designed |
Informations supplémentaires
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.
Étapes pour reproduire
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.
Étapes pour reproduire
ID de bogue: BUG-000178183
Logiciel:
- ArcGIS StoryMaps
Recevoir une notification lorsque le statut d’un bogue change
En savoir plus sur ce sujet
Rechercher des informations associées
Rechercher une formation sur ce sujet
Explorer des pistes et donner un avis
Obtenir de l’aide auprès des experts ArcGIS
Télécharger l’application Esri Support