Accessible systems training
Hi all, I was wondering what people's thoughts are on best practice of making systems training in Articulate Storyline360 accessible, targeting WCAG 2.2 AA. Presumably the system being recorded itself needs to be accessible to this standard for users. How does the built in screen recording show me/try me type content behave with screen readers and key board navigation? Any experiences from end users that use assistive technologies, that have been through systems training? Thanks in advanceAccessibility Checker Results Export?
Is there a way to export the full results of the accessibility checker? Our Accessibility office is trying to work with us on changes necessary and they don't have a license to access the software. We want to be able to easily share the results with them. I am also registered for the Yukon Learning Accessibility course in Feb. 2026.Return focus to hyper link from layer
This might be a bit of a niche requirement, but it came up a few weeks ago when testing content for a client. If you use a hyperlink (text with a link on it) to show a layer in Storyline, you cannot return the focus to the hyperlink that showed the layer, when closing the layer. Storyline does not return the the focus automatically like it does with other elements such as buttons, nor is it possible to return the focus to a hyperlink using triggers, as the hyperlink is not exposed as an object that you can send focus to. The result is that the focus is returned to the top of the current slide when closing a layer that has been shown using a hyperlink. Maybe the Storyline engineers can fix this up? The solution is a bit of JavaScript. Firstly, we need to add some JavaScript to the Storyline project, to make a function available throughout the project. The best way to do this is to add the following JavaScript to the "When timeline starts on this slide - Execute JavaScript" to the Slide Master. window.RM_focusToLink = function(index) { const arrindex = Number(index) - 1; setTimeout(function(){ var link = document.querySelectorAll('#slide a')[arrindex]; link.focus(); },100); } Then, within the layer, you need to add the following JavaScript to the button (or any other trigger) that is closing the layer: window.RM_focusToLink(1); The number 1 that is placed within the brackets is the argument that needs to be passed to target a specific link on the slide. In this case, it is link number 1 which just means it's the first link on the slide (with regards to the order it appears in the Document Object Model). I did consider targeting the link using the text within the link, but then considered that could be duplicate links with the same name, and so using the index is the safest. For any programmers out there, I'm starting the index at 1 rather than 0 (zero) to make it more user friendly. I have attached a demo file.In Case You Missed It (ICYMI): Accessibility Updates in Q4 2024
Welcome to 2025! Since my last update, this accessibility group has grown by 61 members, bringing its total to 403 members. The first ICYMI edition was published on October 23, 2024, and established a foundation, but we can keep it short and sweet from now on. Product Updates: Rise 360 New: Immerse all learners in customizable interactive experiences with accessible scenario blocks that offer alternative text, screen reader support, and a visible focus indicator. New: Select the source course language when exporting your training for translation. Enhanced: Select the text of a hyperlink to apply formatting, including changing the color of the text. Enhanced: Line height and letter spacing are now available in the text formatting toolbar. Storyline 360 Enhanced: Expand your reach with a new AI text-to-speech model that supports Hungarian, Norwegian, and Vietnamese in addition to the 29 other languages already supported. Enhanced: You can now add text-to-speech narration and sound effects to markers. Fixed: Text alignment wasn't preserved in existing projects. Upcoming accessibility features: We've released Rise Accessible Drag-and-Drop Questions (Q1 2025, but released before posting this) and added Rise Math Equations. Current accessibility items on our feature roadmap include: Storyline Accessibility Checker Storyline Math Equations Rise Math Equations Updates in articles, documentation, resource center, or training: Refreshed: Storyline 360: Working with Hyperlinks New blog: What Is Section 508? A Quick Guide to Section 508 Compliance Upcoming webinar: Beginner's Guide to NVDA and Storyline for Accessibility Testing New entry in Storyline 360: Our Accessibility Journey - Accessibility Enhancements to Kick Off 2025In Case You Missed It (ICYMI): Accessibility Updates in Q2 2025
Welcome to our Q2 2025 update! We’ve got plenty of progress and highlights to share because a lot can happen in just a few months. The group continues to grow, with 125 new members joining us this quarter, bringing us to 658 people who care about making things more accessible. That’s incredible, and we’re so glad you’re here. Let’s take a look at what’s been happening! Product Updates Rise 360 New: Articulate Localization launched! Instantly translate Rise 360 courses into 70+ languages with fully integrated AI translation. New: Generate text-to-speech audio and transcripts with AI Assistant. New: Insert audio in text, quote, statement, image, list, carousel, flashcard, tabs, and accordion blocks. Enhanced: Matching knowledge check blocks have been reworked to better reflect their original design while retaining full keyboard support and comprehensive screen reader integration. Storyline 360 New: Articulate Localization launched! Instantly translate Storyline 360 courses into 70+ languages with fully integrated AI translation. New: Insert AI-generated alt text for slide objects to improve accessibility. New: Improve the accessibility of your content. Get actionable feedback based on key WCAG guidelines to instantly identify barriers like missing closed captions and disabled course playback speed. New: Instantly generate high-quality captions for your audio and video content to boost accessibility. New: Enjoy more sizing options for the modern player. Lock the player size or let it adjust to learners' browsers. Enhanced: Create inclusive content from the start with a template that meets accessibility standards. Enhanced: Use the Esc key to close any window in Storyline 360. Enhanced: We improved the screen reader experience by adding a customizable player text label for the sidebar menu landmark. Fixed: NVDA screen readers didn't follow the correct focus order. Fixed: Closed captions showed up earlier than expected and could stack up on each other while using the seekbar. Fixed: Screen readers incorrectly announced some graphic elements despite their being invisible to accessibility tools. Fixed: Screen readers skipped some lightboxed content if the browser window was maximized or the system display scaling was set to 100%. Other Updates New articles AI Assistant in Storyline 360: AI-generated Alt Text Suggestion Storyline 360: Improving Experiences With the Accessibility Checker AI Assistant in Storyline 360: AI-generated Captions Storyline 360: New Project Accessible Template How E-Learning Redefines Accessibility for All Learners Rise 360 Accessibility Maturity Plan Storyline 360 Accessibility Maturity Plan Reach 360 Accessibility Maturity Plan Updated articles Storyline 360: Our Accessibility Journey Accessibility Index Training Reimagining Storyline Interactions for Accessibility and User Experience Register now: Create More Inclusive E-Learning with the New Storyline 360 Accessibility CheckerAccessibility 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!
