iFrame video becoming a keyboard trap
We have several Rise tutorials that use YouTube content embedded using iFrames. Doing accessibility testing, we recently discovered that these become keyboard traps. Users can tab into the content and play it, but the standard guidance of using esc to navigate out of the video isn't working and tabbing through also doesn't seem to work. Does anyone have insight into what we need to do to make this content fully keyboard accessible? Has anyone else had this issue? Thanks!NVDA Storyline 360 Software Simulation Issue
Hello all, I have been working on a software training course for a while, but I cannot share the product file, so I have tried my best to replicate the issue with a brief PowerPoint activity. My current project file has 6 scenes and 452 slides. I am looking for the easiest fix to the issue at this point, while avoiding backtracking on work. Any assistance would be GREATLY appreciated as I am close to my wits' end. Below is a synopsis of the issue, the fixes I have tried, and the attached PowerPoint Activity project file. Build Background: I used the screen recording features in Storyline 360 to create both Try Mode Steps and Test Mode Steps for scenes in the course. I turned off Show Animation in the Capture Action Fine Turning. I have ensured that hotspot and text entry interactions are at the top of the timeline, above all other elements. I have deleted triggers where possible, but some of the Play Video Screen Recording Action When the User Clicks Hotspot 1 remain, as the program won't allow them to be deleted even after turning off the animations, so I have disabled them. I had to make additional cover-ups to hide employee IDs and information, as I did not have a fake user account. The cover-ups have been hidden from accessibility tools. Issue: When navigating the course with NVDA and Microsoft Narrator, the Try Again layer keeps deploying as the user selects the hotspot button for a second and announces "Incorrect," which will lead to annoyance and confusion for the learner. The Try Again layer does not deploy in the Test Mode Steps scenes, but it does in the Try Mode Steps scenes. The Try Again layer does not deploy when using keyboard navigation without a screen reader enabled. I do not want to remove the Try Again feedback, as it is important for sighted users. Triggers on Base Layer: When the user clicks outside Hotspot 1 - Show layer Try Again When the user clicks Hotspot 1 - Jump to slide next slide (Disabled) When the user clicks Hotspot 1 - Play video Screen Recording Action Triggers on Try Again Layer: When user clicks Try Again - Hide layer this layer Solutions Tried But No Success: Running the file as a published SCORM in test environment, Review 360, and in preview mode- Try Again layer still deploys in all environments. Expanding the hotspot area beyond the identified bounds. Changing the order of the user clicks outside Hotspot 1 and the user clicks Hotspot 1 triggers on the base layer but Storyline 360 does not allow me to change the position of these triggers under Hotspot 1 in the trigger menu. Adding back in the correct layers of the screen recording as shown in scene two of my attached example.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 advanceNVDA Keyboard Navigation Issue in Process Block (Step Progression)
I’m testing the Process block for keyboard and screen reader accessibility using NVDA and wanted to confirm expected behavior. Initially, NVDA reads the step buttons (Step 1, Step 2, etc.) along with the left/right navigation arrows, and then proceeds to read the content of Step 1. After the Step 1 content is read, pressing Tab moves focus to the next interactive element in the following block, rather than moving to Step 2. At the moment, the only way to reach Step 2 is by using Shift + Tab to go back to the step buttons and activating it. Is this the expected keyboard interaction for the Process block, or should Step 2 be part of the natural tab order immediately after the Step 1 content?New Audio Descriptions Resource
We recently published a new article on improving video accessibility with audio descriptions in Storyline 360. If your videos include important visual details, such as on-screen text or charts, audio descriptions help ensure that learners who are blind or have low vision can access key information. In this resource, you’ll learn: When to use audio descriptions Differences between standard and extended descriptions How to add them in Storyline 360 Tips for writing effective descriptions How WCAG guidelines apply Are you using audio descriptions in your courses? Are there other accessibility topics we should cover? We want to hear from you!Testing Carousel/Process block in Rise using NVDA
Hi everyone, Has anyone tried testing the carousel and process blocks in Rise with the NVDA screen reader? And if yes, could you please share the key-strokes combo you used so the screen reader picks up both the Alt text for the images and the text in the steps? I am struggling with the text element - the screen reader picks up the image Alt Text, but doesn't go to the text if using the drop arrow. Any advice would be highly appreciated. You are great! Thanks.Accessibility 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.In Case You Missed It (ICYMI): Accessibility Updates in Q4 2025
Welcome to our Q4 2025 update! This quarter, we focused on making accessibility easier to create and better to experience. Across Rise and Storyline, we introduced new AI-powered tools for captions, alt text, and narration, expanded options for accessible design, and fixed issues that affected keyboard and screen reader users. Together, these updates help authors save time while building learning experiences that work well for people using a wide range of assistive technologies. We're excited to see our community grow. This quarter, 71 new members joined, bringing us to 824 people who care about accessibility and inclusion. We're happy you're here with us. Let's take a look at what's new this quarter! Product Updates Rise New: Boost your video's accessibility with AI-generated captions you can easily fine-tune using an intuitive built-in editor. New: Add audio to scenario blocks for content that's even more interactive content. Enhanced: Use the Bullet Style options in the text formatting toolbar to modify the size and color of bullets and numbers in lists. Enhanced: Modify the spacing between buttons with this convenient button stack setting. Storyline New (Beta): Easily translate text-to-speech audio and AI-generated narrations with Articulate Localization to make your content more inclusive. Enhanced: Automatically generate alt text for your assets all at once, then edit or finalize each description right from the accessibility checker. Enhanced: Save time and boost accessibility by automatically generating AI captions for uncaptioned audio and video files when you import a Storyline 360 project. Enhanced: Streamline your captioning process with AI Assistant. Generate captions automatically when you import media with flexible settings to fit your workflow. Enhanced: Quickly improve accessibility by generating captions for course audio and video content in one step. Enhanced: Maximize efficiency while ensuring accessibility by generating captions after recording audio in Storyline 360. Enhanced: You can now add alt text to your cover photos to improve accessibility. Enhanced: Improve caption readability on any background by turning text shadow on or off. Enhanced: You can now chat with AI Assistant to generate text-to-speech narration from your slide notes in addition to your slide content or script. Fixed: Marker title text disappeared when turning accessible text off. Fixed: The accessibility checker incorrectly reported missing text styles on slide master layouts even when they were already applied. Fixed: Textboxes displayed scrollbars that couldn't be accessed with the keyboard when users enabled a text-spacing browser extension in Google Chrome. Fixed: Keyboard navigation didn't work for web objects on layers, and screen readers didn't announce their alt text. Fixed: NVDA screen reader users could access disabled buttons through arrow-key navigation. Fixed: Screen readers inconsistently announced the slide title and state. Fixed: Windows Narrator added an unwanted description before the slide title. Fixed: The focus indicator didn't work correctly for hyperlinks and images with zoom enabled. Fixed: A scrollbar didn't appear as expected when text overflowed. Fixed: The text for the keyboard shortcuts toggle didn't meet color contrast guidelines. Fixed: The focus indicator didn't highlight the volume control when users viewed videos in full-screen mode. Other Updates New Articles Accessibility Standards Around the World Updated Articles Storyline 360: Our Accessibility Journey Storyline 360: Navigation for Screen Reader and Keyboard-Only Users Storyline 360: How Screen Reader or Keyboard-only Navigation Works for Multiple Choice and Multiple Response Questions Rise 360 Accessibility Conformance Report Storyline 360: JavaScript Tips and Examples Rise 360: Create Custom Blocks Storyline 360: Tips for Importing Microsoft PowerPoint and Articulate Presenter Content Accessibility Index We also hosted accessibility stations at the Articuland Summit and DevLearn, where we had the chance to talk directly with many of you about accessibility. We shared our Accessibility Quick-Start Guide, a concise course designed to help you understand the basics of accessibility, apply best practices, and know where to go next. at DevLearn and LeslieMcKerchie at Articuland Summit We’d love to hear from you. What update caught your attention this quarter? Are you planning to join us at axe-con 2026? Let us know in the comments below.Introduction
Welcome to our Accessibility Group! We're excited to have you join this collaborative space, where you can find inspiration and connect with like-minded individuals. We're all human and learning on this accessibility journey. Use this group to ask questions, share ideas, support each other, and learn about the latest guidelines and laws. Together, we'll grow in accessibility maturity and create a supportive community through this safe and inclusive space.
