Articulate Storyline and Web Content Accessibility Guidelines (WCAG)

Article Last Updated Jun 22, 2017

This article applies to:

We want all learners to be able to fully interact with courses you create in Articulate Storyline.

The following table outlines how we’ve optimized Storyline 2 and later to meet WCAG 2.0 requirements, Levels A and AA.

The design decisions you make while building courses in Storyline also impact WCAG compliance. We’ve noted those cases in the table below and have provided guidance on how to make WCAG-compliant authoring decisions where appropriate.

WCAG RequirementLevelStoryline Support

1.1.1 Non-text Content

All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.

A

Supported. Alternate text can be defined for each object in a Storyline course.

1.2.1 Audio-only and Video-only (Prerecorded)

An alternative for time-based media is provided.

A

Supported. Simply import caption files for narration and videos in Storyline 360 and Storyline 3.

For Storyline 2, we recommend using triggers to display a text box synchronized with the media. The display of the text box is controlled by a variable on the slide master.

1.2.2 Captions (Prerecorded)

Captions are provided for all prerecorded audio content in synchronized media.

A

Supported. Simply import caption files for narration and videos in Storyline 360 and Storyline 3.

For Storyline 2, we recommend using triggers to display a text box synchronized with the media. The display of the text box is controlled by a variable on the slide master.

1.2.3 Audio Description or Media Alternative (Prerecorded)

A

Author controlled.

1.2.4 Captions (Live)

AA

Not applicable.

1.2.5 Audio Description (Prerecorded)

In synchronized media.

AA

Author controlled.

1.3.1 Info and Relationships

Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.

A

Author controlled. Add alternate text to slide objects to provide context.

In Storyline 360 and Storyline 3, you can also structure text with tables. Be sure to add alternate text and a meaningful tab order to tables and cells to optimize them for screen readers.

1.3.2 Meaningful Sequence

When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined.

A

Supported. A custom tab order can be defined by the author in Storyline 2 and later.

1.3.3 Sensory Characteristics

Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound.

A

Author controlled.

1.4.1 Use of Color

Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

A

Author controlled.

1.4.2 Audio Control

If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level.

A

Supported. Screen readers can access the player audio controls.

1.4.3 Contrast (Minimum)

The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for large text, incidental text, or logotypes.

AA

Author controlled.

1.4.4 Resize Text

Text can be resized without assistive technology up to 200 percent.

AA

Author controlled. The author sets the font size for slide text and player controls.

1.4.5 Images of Text

If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text.

AA

Author controlled.

2.1.1 Keyboard

A

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

2.1.2 No Keyboard Trap

A

Supported.

2.2.1 Timing Adjustable

A

Supported.

2.2.2 Pause, Stop, Hide

A

Supported.

2.3.1 Three Flashes or Below Threshold

A

Supported.

2.4.1 Bypass Blocks

A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

A

Supported in Storyline 2 and later.

Repetitive navigation elements can be skipped to access slide content immediately when tabbing through a course with a screen reader.

The skip-navigation feature is automatically enabled in published courses.

2.4.2 Page Titled

A

Author controlled. Specify the course title in player properties.

2.4.3 Focus Order

If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

A

Supported. A custom tab order can be defined by the author in Storyline 2 and later.

2.4.4 Link Purpose (In Context)

A

Author controlled.

2.4.5 Multiple Ways

More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process.

AA

Supported. Use the player's built-in menu feature or create a custom menu for navigation.

2.4.6 Headings and Labels

Headings and labels describe topic or purpose.

AA

Author controlled.

2.4.7 Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

AA

Supported. A rectangle indicating focus is displayed when tabbing from item to item.

3.1.1 Language of Page

A

Supported in Storyline 2 and later. A language identifier is added to the published output for screen readers.

The author specifies the language using the Language drop-down list for the player text labels.

3.1.2 Language of Parts

AA

Author controlled.

3.2.1 On Focus

When any component receives focus, it does not initiate a change of context.

A

Supported.

3.2.2 On Input

Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component.

A

Author controlled.

3.2.3 Consistent Navigation

AA

Author controlled.

3.2.4 Consistent Identification

AA

Author controlled.

3.3.1 Error Identification

A

Author controlled. Examples: Automatic warnings for questions left blank, number validation for numeric entries, etc.

3.3.2 Labels or Instructions

Labels or instructions are provided when content requires user input.

A

Author controlled. Give learners instructions when they need to interact with slide content.

For example, provide on-screen instructions when learners need to type information into a text-entry field so they know what’s expected of them.

3.3.3 Error Suggestion

AA

Author controlled. Use states, layers, and triggers to give learners instructions when they respond to the content incorrectly.

3.3.4 Error Prevention (Legal, Financial, Data)

AA

Author controlled and specific to each learning management system (LMS).

4.1.1 Parsing

In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.

A

Storyline generates well-formed HTML output when published.

Optional JavaScript triggers are controlled by the author.

4.1.2 Name, Role, Value

A

Author controlled.