Storyline 360 Accessibility Maturity Plan

Issue

Status

Workarounds

Comments

Likert scale survey questions are not keyboard accessible.

• 2.1.1 Keyboard (Level A)

Planned

Create from scratch using radio buttons in button groups.

Update this question type to conform with WCAG guidelines.

Screen readers reading SVG’s text content when hidden from accessibility tools.

• 1.3.1 Info and Relationships (Level A)

Planned

Save the SVG as a PNG. Replace the SVG with the saved PNG and uncheck “visible to accessibility tools”

Ensure that content hidden from screen readers is not read.

Drag-and-drop interactions are not keyboard accessible.

• 2.1.1 Keyboard (Level A)

Planned

Storyline: Accessible Drag-and-
Drop Chat Interaction

Update drag-and-drop interactions to conform with WCAG guidelines. This includes:

• Matching drag-and-drop
• Sequence drag-and-drop
• Ranking drag-and-drop
• Freeform drag-and-drop

Unable to pause the hotspot selector in a question slide

• 2.2.2 Pause Stop Hide (Level A)

Planned

No workarounds

Add an option for the author to turn off the spinning and pulsing on the hotspot selector.

Checkmarks on correct responses do not have a text alternative.

• 1.1.1 Non-text Content (Level A)

Planned

No workarounds

The checkmark should have a text alternative as a non-text element on the page.

Unable to customize the player tab order.

• 2.4.3 Focus Order (Level A)

Planned

No workarounds

Allow authors to set the player’s tab order, such as placing the next button immediately after slide content.

Closed captions do not appear on videos opened in a new browser window.

• 1.2.2 Captions (Prerecorded)(Level A)

Planned

Set the video to play on the slide.

Let closed captions display when the video is launched in a new browser window using the browser’s built-in video player.

Unable to include multiple languages in closed captions.

• 3.1.2 Language of Parts (Level AA)

Planned

No workarounds

Include a button on the player to display multiple languages in closed captions, similar to Rise 360.

An accessibility checker within Storyline, similar to PowerPoint, would be helpful to ensure the creation of accessible courses.

• Best practice

Q2 2025

No workarounds

Add an automated accessibility checker to assist in creating accessible content for learners.

Closed captions stop playing on iOS devices on the second playthrough.

• 1.2.2 Captions (Prerecorded) (Level A)

Planned

Jump to slide for replay.

Ensure closed captions play regardless of how many times the audio is played.

Alt text on states (selected, visited, etc.) is not read if the normal state does not have alt text.

• 1.1.1 Non-text Content (Level A)

Planned

Add alt text to the normal state.

Ensure all alt text entered is read by a screen reader.

Textbox scrollbars are not keyboard accessible when enabling the Text Spacing Editor browser extension.

• 1.4.12 Text Spacing (Level AA)

Planned

No workarounds

Ensure all scrollbars are keyboard accessible.

Closed captions from layers overlap other layers.

• 1.2.2 Captions (Prerecorded)(Level A)

Planned

Hide other slide layers.

Ensure closed captions on layers for video and audio will not overlap with other layers.

Unable to add a video transcript button to the modern player.

• 3.2.3 Consistent Navigation (Level AA)

Planned

No workarounds

Adding the video transcript button to the modern player would prevent duplication of navigation and provide more controls.

Unable to autocomplete text entry fields from the browser.

• 1.3.5 Identify Input Purpose (Level AA)

Planned

No workarounds

Allow authors to declare the purpose of a text entry field and enable the browser to auto-fill fields.

Screen readers are not reading the alt text assigned to web objects.

• 1.1.1 Non-text Content (Level A)

Planned

No workarounds

Ensure that screen readers read the defined alt text for the web object.

Screen readers do not respect the focus order of the next slide if using the accessibility shortcut (CTRL + ALT + .).

• 2.4.3 Focus Order (Level A)

Planned

Use the default key to navigate to the next slide.

Allow screen readers to follow the focus order of the current slide and not resume the focus order from the previous slide.

When using a screen reader and pressing enter after entering a search term, the screen reader does not announce the results or focus shift to the results.

• 2.4.3 Focus Order (Level A)

Planned

Use the arrow keys after pressing enter on search.

Content does not change without user input, but it could be improved by shifting the focus to the search results and announcing the results after pressing enter.

Unable to pause GIF.

• 2.2.2 Pause, Stop, Hide (Level A)

Planned

Use short video.

Ensure that users can pause and start GIFs.

Unable to focus inside a web object on the slide via keyboard navigation.

• 2.1.1 Keyboard (Level A)

Planned

Set the web object to open in a new window.

Allow keyboard navigation of a web object on a slide to match navigating with a mouse.

The keyboard shortcut to pause (Ctrl+Alt+P) does not play/pause the audio from a lightbox.

• 2.1.1 Keyboard (Level A)

Planned

No workarounds

Ensure that keyboard shortcuts work on lightbox slides.

Screen readers read a slider value for each position, which provides no context.

• 1.3.1 Info and Relationships (Level A)

Planned

No workarounds

Allow labels on a slider for each position for screen readers.

The screen reader re-read the activated element instead of moving to the next element using the down arrow key in pick-many and pick-one question slides.

• 2.4.3 Focus Order (Level A)

Planned

Use the tab key to move between interactive objects.

Ensure that the screen reader announces the next element in the pick-many and pick-one question slides after pressing the down arrow key.

When using a screen reader, the incorrect layer displays in a try mode screen recording for a few seconds, even when the correct answer is selected.

• 2.4.3 Focus Order (Level A)

Planned

No workarounds

Ensure the incorrect layer is not displayed when a correct answer is selected.

The search input field does not have a visible label.

• 4.1.2 Name Role Value (Level A)

Planned

No workarounds

Ensure the search input field has a visible label in addition to the placeholder text so that the label remains when the user begins entering information.

The screen reader is not reading the slide title and state when the focus is on the selected slide in the menu.

• 1.3.1 Info and Relationships (Level A)

Planned

No workarounds

The screen reader should read the slide title and the current state of the slide when focused on the menu.

If you delete the original object from states, the screen reader still reads the normal state alt text.

• 4.1.2 Name Role Value (Level A)

Planned

Avoid deleting the original object from the normal state.

The screen reader should read the alt text on the correct objects and not on deleted items.

Closed captions (from multiple audio files) can stack while using the seekbar.

• 1.2.2 Captions (Prerecorded) (Level A)

Planned

No workarounds

Ensure that the course only shows one closed caption tile at a time.

Unable to access closed captions with the menu in the top right on mobile landscape view.

• 2.4.11 Focus Not Obscured (Minimum) (Level AA)

Planned

No workarounds

Ensure that buttons are not obscured.

Screen readers don’t announce the alt text of the disabled state correctly.

• 4.1.2 Name Role Value (Level A)

Planned

No workarounds

Ensure the alt text of the disabled state of objects is read correctly.

When you add a slider, the screen reader will announce it as Slider 2.

• 1.1.1 Non-text Content (Level A)

Planned

No workarounds

Ensure that the screen reader is reading the correct slider number.

The video button overlay does not indicate the current play or pause state of the video

• 4.1.2 Name Role Value (Level A)

Planned

No workarounds

The screen reader should announce the name of the play button and toggle to pause when playing.

Unable to dismiss object hover states with a keyboard command.

• 1.4.13 Content on Hover or Focus (Level AA)

Planned

No workarounds

Ensure hover states can be dismissed with a keyboard command.

There is not enough contrast on the small icons for the attached documents in the Resources tab.

• 1.4.11 Non-text Contrast (Level AA)

Planned

No workarounds

Ensure that the images/icons used for attachments in resources.

Unable to adjust the fill color and icon color on 360° image markers.

• 1.4.3 Contrast (Minimum)(Level AA)

Planned

No workarounds

Allow the author to adjust the fill color and icon color so that white is not always a color in the icon.

Unable to have notes for each slide layer.

• 1.1.1 Non-text Content (Level A)

Planned

No workarounds

Let layers have unique notes from the base layer slide instead of having one note for a slide and all layers.

Hyperlink states need non-color visual cue options in style settings.

• 1.4.1 Use of Color (Level A)

Planned

No workarounds

Expand options for underlining or other non-color visual cues for hyperlink states.

Not able to customize a “hover” state via triggers so that keyboard navigation works when an item is in focus.

• 1.4.13 Content on Hover or Focus (Level AA)

Planned

No workarounds

Add “in focus” or “on focus” triggers for more dynamic keyboard navigation.

Some text in the player is clipped when using custom text spacing.

• 1.4.12 Text Spacing (Level AA)

Planned

No workarounds

Ensure the player allows full text to display when using custom text spacing.

Automatic scrollbars are added when turning on accessible text but aren’t keyboard accessible.

• 1.4.12 Text Spacing (Level AA)

Planned

No workarounds

Ensure all scrollbars are keyboard navigable.

Unable to see the cursor in the data entry field with focus.

• 2.4.7 Focus Visible (Level AA)

Planned

No workarounds

Ensure the cursor displays in a data entry field with focus.

The screen reader announces an inappropriate name, “outline-container,” for the sidebar.

• 1.3.1 Info and Relationships (Level A)

Planned

No workarounds

Ensure the screen reader announces “Outline Menu” or something that correctly conveys the purpose.

Search panel landmark is exposed to screen readers even when the search is visually hidden

• 1.3.1 Info and Relationships (Level A)

Planned

No workarounds

The search landmark should only be read by a screen reader when it’s available.

The transcript button needs better accessibility

• 1.3.1 Info and Relationships (Level A)

Planned

Authors can go into Player Properties -> Text Labels and change Open to different text

The transcript button needs a more descriptive label. It’s currently announced as ‘open’, but this does not describe its function.

Web object lacks an indication that it requires a click to load the object

• 4.1.2 Name Role Value (Level A)

Planned

No workarounds

When a web object is set to click to load, the overlay should be a button so screen reader users know it’s interactive.

AI-Generated Alt Text Suggestion

• 1.1.1 Non-text Content (Level A)

Planned

N/A

Insert AI-generated alt text for slide objects to improve accessibility.

AI-Generated Captions

• 1.2.2 Captions (Prerecorded)(Level A)

Planned

N/A

Instantly generate high-quality captions for your audio and video content to boost accessibility.

Released

Release Date

The focus highlights for the prev/next buttons are now in alignment when on a lightbox slide.

February 2024

Able to navigate away from embedded Soundcloud objects with keyboard navigation in Firefox.

March 2024

Able to navigate via the keyboard when a scroll bar is automatically created in feedback layers.

March 2024

Custom focus order is followed for web objects.

March 2024

Tab key navigation on hyperlinks with a line break no longer displays a focus artifact.

May 2024

Screen readers now recognize tables.

July 2024

When using zoom to fit, the focus no longer moves to elements that are not visible when the sidebar is expanded.

December 2024

NVDA announces clickable when reading a textbox

February 2025

Screen Reader doesn’t announce light-boxed slide text

February 2025

Screen readers aren’t reading punctuation for keyboard shortcuts

March 2025