In Case You Missed It (ICYMI): Accessibility Updates in Q3 2026
Welcome to our Q3 2026 update! This quarter, we made it easier to add captions and structure content in Rise while improving caption workflows, alt text guidance, and screen reader experiences in Storyline. We also had the chance to talk about accessibility together at Articuland Orlando. Our Accessibility Group has reached 1,042 members! That’s 72 more people since our last update, and it means we’ve crossed the 1,000-member mark. Thanks for being here, sharing what works, and helping one another create more accessible training. Let’s take a look at what’s new this quarter! Highlights This Quarter This quarter’s accessibility updates centered around three themes: Making content easier to navigate and understand In Rise, authors can adjust heading levels within labeled graphic markers. A clear heading structure helps screen reader users understand and navigate content. The custom block audio player also received accessibility improvements. Making captions easier to create and manage Rise can now generate captions for uploaded videos and AI Avatars in custom blocks. In Storyline, authors can export all closed captions for a project at once or from the Video Tools Options tab. We also fixed issues that could cause captions to disappear or fail to update after media was edited. Connecting at Articuland Orlando I loved being at Articuland Orlando, hosting a session, and having accessibility conversations with customers and colleagues. Meeting people in person gave us another opportunity to hear about the work you’re doing and the questions you’re navigating. Thanks to everyone who stopped to talk! Product Updates Rise Enhanced: Adjust heading levels within labeled graphic markers to give content a clearer structure. Enhanced: The custom block audio player received accessibility improvements and a compact layout. Enhanced: Automatically generate captions for uploaded videos and AI Avatars in custom blocks. Enhanced: Rearranging blocks in the editor now uses less motion. Storyline Enhanced: Export all closed captions in a project at once, or export captions from the Video Tools Options tab. Enhanced: Alt text with exactly 150 characters no longer triggers the accessibility checker’s action to shorten it. That recommendation now appears at 151 characters or more. Fixed: Closed captions could be removed after editing a video. Fixed: Authors couldn’t separate closed captions to separate instances of the same video. Fixed: JAWS announced an object’s noobject’s te alt text instead of its selected-state alt text when learners navigated with the arrow keys. Fixed: Closed captions for AI text-to-speech did not update when narration was edited. Fixed: Closed-caption text could be missing after an AI voice was updated or regenerated. Fixed: The focus indicator highlighted an inactive area when tabbing through an Invalid Answer message. Other Updates Customer Story Artisan Learning Builds Accessible Training for Every Learner With Articulate 360 Artisan Learning shares how it considers accessibility while creating training for a wide range of people and projects. Its story is a reminder that choices such as adding captions, writing alt text, and supporting keyboard navigation can help more learners take part. Updated Articles Rise 360: Our Accessibility Journey Storyline 360: Our Accessibility Journey Accessibility IndexYou spoke, we listened: Alt text at exactly 150 characters no longer gets flagged
Hi everyone, At Articuland Orlando 2026, I had the chance to chat with many of you about accessibility in Storyline 360, and one piece of feedback I wanted to follow up on came up. The "Accessibility Checker" recommends keeping alt text to 150 characters or fewer, but it was flagging alt text that was exactly 150 characters, creating noise for authors who were already doing the right thing. When I got back from Orlando, I brought this to the team, and we fixed it. As of Storyline 360 Update 127: The 150th character now counts within the limit Only alt text that is 151 characters or longer will trigger the recommendation to shorten it To get the fix, update Storyline 360 through the Articulate 360 desktop app. A huge thank you to everyone who shared feedback at Articuland. Conversations like these directly shape what we build, so please keep them coming. If you run into anything else with the "Accessibility Checker" or have ideas for making a11y easier in Storyline 360, drop a comment below. Thanks, RonnieStoryline 360: Keyboard focus missing for right-click trigger
Hey all, I have a short simulation built that functions well with a mouse, but keyboard navigation gets stuck when the trigger is "user right clicks" on a hotspot. In these cases, the focus indicator is missing, and the user cannot even focus on the hotspot. Any ideas?[REDUNDANT] Storyline custom focus control
========================================================================= Update 18 March 2025 This functionality is now redundant. Please use the native focus trigger in Storyline 360 64 bit March 18, 2025 (Build 3.98.34222.0) ========================================================================= There have many been times, when using Storyline to develop content, it has not been possible to get the kind of screen reader focus control that I have needed. Using layers for this can only get you so far. I developed a JavaScript function that allows you to send the screen reader focus to the text field that you want, via any trigger. Adding the following JavaScript to your projects Slide Master will make it available throughout your module: // Check if function has been defined already if (typeof window.setFocus === "undefined") { // Get reference to the Storyline Player var $player = GetPlayer(); // Set the amount of time to delay before attempting to send focus to the target element (milliseconds) 1000 = 1 second. var $interval = 200; // window.setFocus = function ($target, $announce = false) { // Get the target element, based on the passed argument setTimeout(function () { var $div = document.querySelector('[data-acc-text^="' + $target + '"]'); var $id = "acc-" + $div.dataset.modelId $div = document.getElementById($id); if($announce) { $div.setAttribute("aria-atomic", "true"); $div.setAttribute("aria-live", "assertive"); } // Send focus to target, after defined $interval $div.focus(); }, $interval); } } Once the function is defined in your Slide Master, you can then call the function on the page using a JavaScript function, which can be triggered by any Storyline trigger such as timeline start, timeline end, button click etc. // The second argument will determine if the content should // be announced to assistive technology using aria-live=assertive // This will announce the text contents to the screen reader window.setFocus("Customer in the queue", true); // This will just send focus to the element. window.setFocus("Customer in the queue", false); The first argument, which is passed in the "" quotes, is the text contents of the text field you are targeting. You do not have to include all the text, just enough to ensure it is unique. For example, if you have two text fields: "Customer in the queue talking on their phone." "Customer in the shop staring into space." Passing the words "Customer in the" would not be specific enough, as there would be two text fields found. However, passing "Customer in the queue" would send the focus to the text field that contains the text "Customer in the queue talking on their phone." The second argument (true or false) determines if the target elements contents should be announced to the screen reader when it receives focus.In Case You Missed It (ICYMI): Accessibility Updates in Q2 2026
Welcome to our Q2 2026 update! This quarter continued our focus on supporting the creation of accessible training and improving the learner experience. From new capabilities for identifying accessibility improvements to refinements for screen reader users, keyboard navigation, and color contrast, these updates reflect our ongoing commitment to accessibility across Rise and Storyline. Our community continues to grow. We now have 970 members, an increase of 54 this quarter. We’re glad you’re here. Let’s take a look at what’s new this quarter! Highlights This Quarter This quarter's accessibility updates centered around three themes: Identifying accessibility improvements earlier Storyline Labs introduces an experimental Color Contrast Check that helps identify color contrast issues across an entire project, while updates to Rise theme colors ensure contrast is calculated correctly across supported theme elements. Giving authors more control Storyline now lets you choose which objects are visible to screen readers, giving you greater control over how your training is presented to assistive technologies. Improving the learner experience Across Rise and Storyline, we refined screen reader support, keyboard navigation, focus management, and question interactions to provide a more predictable experience for learners using assistive technologies. Together, these updates continue our focus on supporting accessible training and improving the experience for everyone who creates and completes it. Product Updates Rise Enhanced: To improve accessibility, we've globally applied WCAG 2.1-compatible contrast to theme color elements that previously had contrast calculated incorrectly. Enhanced: Improved screen reader focus behavior so that, after answering a knowledge check, focus moves directly to the next relevant content. Enhanced: Improved tooltip behavior so that only meaningful tooltips are displayed for interactive elements like the block selector and sorting activity. Enhanced: Preview now opens the entire course, with full navigation. Enhanced: The video player is now consistent across the app and provides a refined experience with better responsiveness on mobile devices. Storyline New: Easily control which objects should be visible to screen readers with a new accessibility toggle in the timeline. New: Storyline Labs is here! Access experimental features early from the Labs button in the File or View tab. Available in Labs: Color Contrast Check helps identify color contrast issues across an entire project using the accessibility checker. Fixed: Screen readers announced extra text when certain question types were used. Fixed: A trigger designed to fire with a user click incorrectly executed when using a screen reader. Fixed: Text-entry fields didn't follow the defined custom focus order during preview. Fixed: Windows Narrator read bulleted and numbered list items twice. Fixed: Screen readers didn't correctly announce nested list items in the Notes panel. Fixed: The accessibility checker incorrectly reported issues on screen recording slides where all objects were hidden from accessibility tools. Fixed: The focus order was incorrect for screen readers when the Transcripts tab was opened. Fixed: Drop-down question choices didn't display a scrollbar when the list couldn't fit all choices. Other Updates Updated Articles Storyline 360: Working with Buttons Rise 360: How to Use Process Blocks Rise 360: Our Accessibility Journey Storyline 360: Our Accessibility Journey Storyline 360: Working with Variables Storyline 360: Working with Triggers Storyline 360: Pick-One Questions Accessibility IndexNew Tutorial! Create and Control Glassmorphism Effects With JavaScript In Storyline
Hi Heroes, I'd like to share the latest episode in my Storyline Magic Series on my YouTube channel! In this episode, we'll delve into 'Glassmorphism'—a modern and powerful design technique that blends translucent surfaces with frosted glass effects. This approach not only enhances the aesthetic of your content but also helps learning designers create depth and establish a clear visual hierarchy. I’ll show you how to create and control this stunning effect entirely within Articulate Storyline 360. Let me know if you'd enjoy seeing more comprehensive start-to-finish project builds like this in the future! And see how other Storyline devs are using Glassmorphism here: https://community.articulate.com/blog/e-learning-challenges/using-glassmorphism-designs-in-e-learning-course-development-310/1151525 --- My name's Chris Hodgson, an eLearning developer and software trainer based in the UK. I enjoy creating fun, unique, and engaging online experiences using Articulate software! Connect with me on LinkedIn - https://www.linkedin.com/in/chrishodgson44/
New in Labs: Color Contrast Check in Storyline 360
Hello, my fellow a11y friends! We just launched the new Color Contrast Check inside Storyline Labs, and it’s ready for you to try out! This feature integrates directly into your built-in Accessibility Checker, making it easier than ever to catch text and object fill contrast issues before you publish. No extra tools required. We want to build the best possible version of this tool, which means we want to hear from you. Turn it on in your Labs settings today, test it out on your current projects, and let us know what you think. Check out the New in Labs: Color Contrast Check in the Accessibility Checker post for more details!Accessibility Checker - Switch off accessible objects
I'm using the accessibility checker to make all my courses 100% accessible. I open the project file, run the checker and go through each line, one by one. The most common error is an object (rectangle / line / icon) not being accessible. Why does a horizontal line ever need to be accessible? So I'm going through turning them all off as they don't need alt text. This is painful, some project files have 000s of errors. Is there a quick way to untick the accessibility of all shape type objects. Icons from the media library are grouped and the main group and its elements all need to be switched off. The acc checker doesn't allow multi select and when in the timeline selecting all and unticking doesn't always work. Its taking forever!Accessibility - Screen Readers and TTS
Hi, I'm currently completing an apprenticeship in Digital Learning Design, and I'm working through some content on accessibility. Previously, all our storyline courses had text-to-speech added on, but the accessibility features such as alt text and focus orders weren't used. Since I've learnt more about screen readers through my apprenticeship, I've been following correct processes and designs for best practice with screen readers. However, as these read out the text on screen, I'm wondering if the text-to-speech I manually add onto all slides is still required? Part of me thinks it might be too much if both the audio on the course and the screen reader are reading the content out loud, but then we might have learners with dyslexia, for example, who might not require a screen reader but still prefer to have the text read aloud. How does everyone else navigate this? Do you use both or one or the other? Thank you!
