Accessibility features
ArcGIS StoryMaps has many capabilities that allow authors to create content that is accessible to a broad audience.
Many features do not require input from the author, such as keyboard navigation and the acceptable text color contrast in the standard themes. However, authors can make changes to content created with ArcGIS StoryMaps that make it more or less accessible. For example, authors must provide alternative text for media and select colors that ensure sufficient contrast when designing a theme or changing the color of text. It is ultimately the author's responsibility to incorporate accessibility into the design and configuration of finished products.
Built-in features
While it is the author's responsibility to integrate accessibility practices into their design, listed below are some built-in accessibility features that readers can expect in ArcGIS StoryMaps content.
Keyboard navigation
ArcGIS StoryMaps supports standard keyboard navigation with a visible focus state. Standard keyboard navigation is used by keyboard, voice recognition software, and switch devices.
Note:
In ArcGIS StoryMaps content, the first tab stop is a Skip to content button that allows readers to skip past the interactive elements in the header to immediately interact with the primary content area of the page (typically the cover).
Keyboard shortcuts
For quick actions to format text, work with content in the builders, and activate presentation mode, ArcGIS StoryMaps includes keyboard shortcuts.
ArcGIS StoryMaps also inherits map interaction keyboard shortcuts through its use of ArcGIS web maps and web scenes.
Screen readers
ArcGIS StoryMaps supports screen readers by communicating component and landmark roles, labels, and state changes to interactive elements.
Themes
All standard themes included with ArcGIS StoryMaps are designed to meet color contrast requirements and work with operating system high-contrast modes.
Authoring features
ArcGIS StoryMaps provides tools for authors to make accessible content; however, the choices an author makes will determine how accessible stories are for the audience. Authors must ensure the content is perceivable and understandable as it relates to WCAG guidelines.
Some accessibility choices authors make are part of the theme, and other choices are made when creating content, such as a story or briefing.
Theme design
The following sections describe accessible theme design capabilities.
Font choices
Authors who choose to use custom themes can choose fonts within the theme builder and from the Google Fonts library. The font choices can affect a story’s accessibility. Some Google fonts—particularly display fonts—have character embellishments or tight spacing between characters that make them more difficult to read. The initial list of suggested fonts in the theme builder has been curated to contain generally accessible fonts. Font sizes for paragraph text can be adjusted within the builder.
For more information, see Format, style, and links.
Color choices
Whenever you choose a color in one of the ArcGIS StoryMaps builders, the contrast checker indicates whether your selected color has enough contrast against its background to meet WCAG AA accessibility guidelines. Generally, this means a contrast ratio of 3:1 for regular and larger text sizes and 4.5:1 for smaller text.
Adhere to the contrast checker's recommendations when choosing colors for the following:
Theme elements such as fonts, background areas, and accent elements (see Create a theme)
Text formatting options within a story, briefing, frame, or collection
Chart and infographic elements
The calculated contrast ratios are available if you choose to adhere to different guidelines. View this information by expanding the contrast checker section of the picker.
Content design
The following sections describe accessible content design capabilities.
Semantic structure
When creating a story, you can include headings to separate a narrative into sections. You can use up to three levels of headings. It's recommended that you use headings in the expected order; for example, don't use a heading 2 before you've used a heading 1.
Choosing to use story navigation within the story Design panel creates navigation links that allow readers to jump to specific headings within a story.
Alternative text
Alternative text is descriptive information about visual media that is announced by screen readers. It is required for media to provide support for search engines and readers using assistive technologies, and it is shown to readers if the media can’t be loaded.
For recommendations on writing alternative text, see Accessibility guidance > Alternative text for media.
Tip:
The ArcGIS StoryMaps assistant can help you save time by utilizing AI to analyze media and generate suggested alternative text for it.
To learn how to add alternative text—including how to use the ArcGIS StoryMaps assistant to generate alternative text suggestions—refer to the relevant section for each type of media: images, videos, maps, swipes, ArcGIS apps, and embeds.
Transcripts and closed captions
When uploading audio or video media, you can add a transcript and closed captions to improve accessibility. See Add and configure audio and Add and configure video.
When embedding video or audio from third-party web services, add transcripts and closed captions using the native platform's tools.
Accessible media
Avoid sharing key information inside media where a screen reader will not pick up text, such as in images with words, videos with elaborate diagrams, or a screenshot of a chart or complex infographic.
Creating charts and infographics in ArcGIS StoryMaps improves accessibility of this type of content compared to using screenshots or exported images of products generated elsewhere. Text information within media can be added to alternative text or a transcript to make it available for screen readers.