Forum Discussion
Player Setup Recommendations for 508/WCAG 2.1 AA: Menu, Transcript, Navigation Buttons
Lately, I’ve been seeing an increased focus among organizations and government entities on ensuring Storyline courses meet WCAG 2.1 Level AA and Section 508 standards. While Storyline 360 offers several ways to create accessible content, I’m looking for general best practices for configuring the Storyline player so that it is straightforward for developers to implement while also providing a seamless experience for screen reader and keyboard users and meeting these requirements.
I would love to hear your recommendations on the most effective way to set up the player, whether that means using the built-in player features or developing a custom navigation interface. Specifically:
- Transcripts & Glossaries: Do you recommend using the built-in player tabs, such as the Notes panel and Glossary tab, or is it better to build custom on-screen versions? If using the built-in player, does the Notes panel function sufficiently to meet accessibility requirements, or would you recommend a different approach for transcripts? If you do use the Notes panel, do you recommend placing it within the menu sidebar or at the top?
- The Menu: For menus that outline the course structure, do you recommend excluding it to reduce “tab fatigue” for screen reader users, or including it so learners can better track their progress? If a menu is included, do you prefer using the built-in Storyline menu or creating a custom one? If you use the built-in menu, is it best practice for the sidebar to start collapsed to keep the focus on the main content, or expanded for easier access? Also, when using the built-in player menu, do you recommend including subheadings?
- Navigation Buttons (Next/Prev): Do you recommend using the built-in Next/Previous buttons or adding custom on-screen buttons? While I know the built-in buttons now support accessibility shortcuts, many developers still seem to create their own Next/Previous buttons. I assume this is to provide a more intuitive end-of-slide experience.
In any case, I would value your suggestions and would especially appreciate understanding the reasoning behind the recommended setup.
3 Replies
Hi BrittanyD, I would recommend using the built in player if your developers aren't very experienced with accessibility, as they just have to focus on making the content in the slide accessible and not the controls as the player components are accessible.
Regarding transcripts and glossaries, you can use the glossaries component in the player, or if you'd like to design your own you can add a layer to you Master slide the can be Shown/Hidden.
Using the Notes for transcript I'm not a fan of, as the Notes tab is available at the and of the slide (after the media player controls and slide navigation buttons) when using a screen reader. I like a transcript to be easier to access and so use layers on individual slide and provide access at the beginning of the slide.
Don't worry about tab fatigue as it is possible to bypass the table of contents. Having the menu open/closed by default is personal preference but it could be worth defaulting to open for larger courses to show users the content they will be completing.
People will develop their own navigation buttons in order to achieve a particular design, but the onus is then on the developer to ensure those added elements are accessible. It's all possible, but there is more work involved and needs a bit more guidance.
In summary, using the built in player components makes it easier for the developer to meet WCAG requirements, but the trade off is the design flexibility.
Providing orientation of the various components and shortcut keys available is a good idea.
I think one of the most important aspects of building accessible content is learning how to test it and learning how to use a screen reader correctly.
Some of the key items my testing includes:
- Complete the course using keyboard only
- Complete the course using keyboard + screen reader only
- Check colour contrast
- Ensure semantic HTML is used
- Check ALT text
- Check closed captions and transcripts for video/audio content
- Ensure all content can be accessed in the intended order.
Hope that helps.
Cheers,
SamFor WCAG 2.1 AA / 508 compliance, stick with built-in player features where possible—they’re more reliable for accessibility.
- Transcripts: Notes panel works if consistently used, but an on-slide transcript toggle improves visibility and usability.
- Menu: Include it for structure, but keep it collapsed by default to reduce tab load. Avoid deep hierarchies.
- Navigation: Prefer built-in Next/Prev for keyboard and screen reader consistency; custom controls only if fully accessible.
Bottom line: prioritize consistency, clear focus order, and minimal cognitive load over heavy customization.
Brittany,
I use the built-in player tabs (Notes and Glossary). I rename Notes to Transcript, so it is labeled with something that is more aligned with how I use it. The Transcript (Notes) replicates all the audio on a slide. I have the Transcript (Notes) and Glossary on the left pane.
With the menu, I use the built-in menu and I have it set so it will collapse as a section is viewed. I also do not lock the menu. I have the sidebar collapsed, but that is because I include a slide at the beginning that alerts the user that the eLearning contains audio, video, or both. To get it to function as I wanted, I had to have the sidebar collapsed. I originally had the menu open with that information on a Cover Photo (option in the Player), but the LMS I use was not displaying it.
I use the built-in navigation buttons for the most part. Occasionally, I restrict the NEXT button if I want to ensure they have viewed everything on a slide that is only visible once they have viewed a slide’s layer.
On the Player, I have Accessibility controls, Captions, Playback speed, and the Seekbar (with allowing to drag) checked. The text setting for “Accessible text by default” is also set in my Master. I include a slide at the beginning of an eLearning that shows (with screenshot plus rectangles) the basic eLearning features (navigation, audio controls, menu controls, menu, glossary, and transcript). I also include a lightbox slide that is available from a link in the top right corner of the Player (where Resources typically are) that has a list of keyboard shortcuts for accessibility. Alt text is added to all images and buttons, and captions are included for all audio and video. The Focus Order can be tricky when you have objects other than a title and basic text, so that is always adjusted as necessary.
That is a bit more information than basic Player setup, but you might find it helpful. Good luck!
Donna
