How to Build a Morphing Menu in Storyline
This tip comes from our certified training partner, Yukon Learning. The morph transition in Storyline lets you create seamless transitions between your slides. In this video, we'll break down a project we shared in an Articulate E-Learning Heroes Challenge. Check out the example here. You can always learn more through their blog and YouTube channel. And if you want live facilitated training, they're your go-to resource. The Articulate Trainer Blog Youtube channel Sign up for trainingPlayer 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.Advanced Storyline? Creative Way to Use Button Sets w/ Quizzes
Discover how advanced Articulate Storyline skills aren’t limited to complex variables or JavaScript. In this tutorial, you'll learn a clever technique using button sets in Articulate Storyline 360 to create multiple quiz questions on a single slide.Small Details, Big Impact: Microinteractions in Storyline
Microinteractions may be small, but they can transform how learners experience your course. In this session, guest speaker Phil Mayor will share practical ways to add motion, feedback, and polish in Storyline to make your interactions more engaging and intuitive. You’ll leave with simple techniques you can apply right away to bring your eLearning designs to life.Storyline: Drag-and-Drop Puzzle Interaction
Want to create an interactive puzzle game in Storyline 360? Dive into this free download and follow this blog tutorial to learn how to craft your own effortlessly. Explore this project. This template will work for folks using Storyline 360, the continuously updated version of Storyline included in Articulate 360. Want to try it out? Get a free trial of Articulate 360 right here. And subscribe to our newsletter to find out about other helpful downloads.
