Articulate Storyline and Section 508 Accessibility

Article Last Updated Sep 11, 2017

This article applies to:

It’s our goal to help all learners interact as fully as possible with the e-learning courses you create in Articulate Storyline.

View the Storyline VPAT

The following table outlines the many ways we’ve optimized Storyline to meet the requirements of Section 508 accessibility of the Rehabilitation Act of 1973.

Section 508 Accessibility Requirement

Storyline Support

Keyboard Support

You can execute most Storyline functions using a keyboard. Exceptions include drag-and-drop and hotspot interactions.

Content Focus

Storyline displays a yellow box around the shape that’s currently in focus and reports it to assistive technology.

Flicker Reduction

Storyline doesn't use flashing or blinking text, objects, or other elements with a frequency greater than 2 Hz and lower than 55 Hz. (Video imported by course authors should also conform to this standard.)

Non-Visual Operation and Information Retrieval

Storyline supports the JAWS screen reader.

Large Text

Storyline supports the JAWS screen reader and makes it easy for course authors to create large text versions of slides.

Text Equivalents

Author controlled. Storyline provides text equivalents (alt text) for every non-text element.

Learners must use supported screen readers and browsers for Storyline 360, Storyline 3, or Storyline 2.

Assistive Technology—Ready UI

Storyline reports an object’s type, state, and description to the accessibility interface.

Assistive Technology—Ready Forms

When forms are used, Storyline provides the type, description, and state information for field elements. (Note: Course authors must include clear written directions for completing the form.)

Assistive Technology—Ready Scripts

All content elements in Storyline include functional text that can be read by assistive technology.

Course author’s role in Section 508 Accessibility compliance

As you build a course in Storyline, you’ll make design decisions that impact Section 508 accessibility compliance. The following table outlines how you can create courses that are more accessible to people with disabilities.

Section 508 Accessibility Requirement

Author-Controlled Compliance

Image Consistency

When you use images to identify controls, status indicators, or other programmatic elements, assign a consistent meaning to those images throughout your course.

Animation (Alternative)

When you convey information in an animation, provide an alternate, non-animated slide for the content.

Keyboard

If you include drag-and-drop or hotspot interactions, provide alternate, keyboard-controlled interactions.

Color Coding (Alternative)

Don’t use color coding as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Multimedia (Alternative Synchronization)

When using multimedia, provide text captions that are synchronized with audio and video. Easily create closed captions in Storyline 360 and Storyline 3 with the built-in editor.

In Storyline 1 and Storyline 2, we recommend using a variable and triggers to display a caption text box synchronized with the media. Learn more.

Text-Only (Alternative)

Make a text-only version of the course available to learners.

Skip Links

Give learners a way to skip repetitive navigation links.

Open/Closed Captions

Provide open or closed captions for all informational video, multimedia, and audio. Easily create closed captions in Storyline 360 and Storyline 3 with the built-in editor.

In Storyline 1 and Storyline 2, we recommend using a variable and triggers to display a caption text box synchronized with the media. Learn more.

Audio Descriptions

Provide audio descriptions for all content.

User-Selectable Audio and Text Descriptions

Make all display of alternate text and audio descriptions user-selectable.

Support for Hearing Impaired

Add notes or captions to slides containing audio and video.

Learn more about Section 508 accessibility requirements.