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
The standard keys used for navigation are Tab, Shift+Tab, Enter, Escape, and the arrow keys. They are used as follows in ArcGIS StoryMaps:
Tab moves focus forward between interactive elements, such as links and buttons
Shift+Tab moves focus in the opposite direction
Enter activates or selects the current element
Arrow keys may scroll the screen, navigate to the next item or slide, or otherwise move between elements
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.
See also Screen readers for additional keyboard navigation options.
Focus state
When navigating ArcGIS StoryMaps content using a keyboard, the keyboard focus state indicates the currently active area on the page. Typically, the focus is shown as a border that highlights the area. This allows the reader to see which area they can interact with using the keyboard.
Screen readers
ArcGIS StoryMaps content is designed to be compatible with screen readers. For example, visible and alternative text is read aloud, and buttons are named and identified. The information read by screen readers may vary depending on the operating system, browser, screen reader software, and individual configuration settings. ArcGIS StoryMaps is tested with VoiceOver on Safari (macOS) and NVDA on Firefox (Windows). Mobile devices also support screen readers, including VoiceOver on iOS devices.
Navigation landmarks can be used to jump between sections of a page. For example, the navigation bar in a story is designated as a landmark.
Color contrast in standard themes
It is important to use a theme that has been designed to account for color contrast requirements. The themes provided with ArcGIS StoryMaps all meet WCAG AA contrast requirements.
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 they relate 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 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 customize a color in one of the ArcGIS StoryMaps builders, you will see a contrast checker that indicates whether your selected color has enough contrast against its background to meet accessibility guidelines.
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
Content design
Choosing to use story navigation within the story Design panel creates navigation links that allow readers jump to specific headings within a story.
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.
Alternative text
Alternative text is descriptive information about visual media that is announced by screen readers. Add alternative text to all nondecorative images and media content.
The ArcGIS StoryMaps assistant can help you save time by generating alternative text for images. See ArcGIS StoryMaps assistant.
For more information, see Using Alternative Text for Equitable Storytelling on the ArcGIS Blog.
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.
Transcripts and closed captions
When uploading audio or video media, you can add a transcript and closed captions to improve accessibility. See Add media.
When embedding video or audio from third-party web services, add transcripts and closed captions using the native platform's tools.