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!In Case You Missed It (ICYMI): Accessibility Updates in Q1 2026
Welcome to our Q1 2026 update! This quarter, we focused on improving how training integrates with assistive technologies while reducing the effort required to build accessible content. With expanded AI support for alt text and captions, better screen reader announcements, and more fully accessible interactions, it’s now easier to create training that works for a wider range of people. Our community continues to grow. We now have 916 members, an increase of 92 this quarter. We’re glad you’re here. Let’s take a look at what’s new this quarter! Product Updates Rise New: Do even more with knowledge check blocks, quizzes, and question bank questions by adding audio. Enhanced: Quiz timer announcements are available for screen readers, as well as a timed quiz section in screen reader announcement labels. Enhanced: Sorting Activity blocks are now fully accessible. Enhanced (Beta): Localize custom blocks with Articulate Localization to maintain consistency across every language. Fixed: Screen readers couldn’t read modified text labels for media player buttons. Storyline Enhanced: Manage AI-generated alt text suggestions as you work directly from the Size and Position window or the media library. Enhanced: AI alt text suggestions generated by the accessibility checker are saved throughout your workflow, keeping bulk-generated suggestions available until you review them. Enhanced: The accessibility checker now displays a distinctive icon when AI-generated alt text suggestions are awaiting review. Enhanced: Speed up your accessibility workflow by generating captions directly from AI Chat. Enhanced: Deliver accessible surveys with a built-in Likert scale question that supports screen readers and keyboard navigation. Enhanced: Get AI-generated alt text suggestions automatically when you import assets, making your courses more accessible with less effort. Enhanced: Link and file icons in the resources player tab now meet accessibility color contrast guidelines. Fixed: Slide content shifted when navigating to objects at the bottom of a slide with a JAWS screen reader. Fixed: NVDA screen reader users could access hidden scrollbars in player tab content. Fixed: The closed captions editor showed captions for text-to-speech narration even though caption generation was turned off. Fixed: The accessibility checker skipped markers when checking interactive objects for the minimum target size. Fixed: Keyboard navigation didn’t work for hyperlinked text inside shapes or text boxes with triggers. Fixed: Screen readers didn’t read alt text for object states if the original object was deleted or the normal state didn’t have alt text. Fixed: In pick-one and pick-many interactions, screen readers announced SVG checkboxes as checked before learners selected their answer. Fixed: JAWS screen readers announced numbered lists incorrectly. Fixed: The accessibility focus indicator was misaligned when text was animated by paragraph. Fixed: The Keyboard Shortcuts window didn’t display all available commands because the scrollbar didn’t work. Fixed: Screen readers announced check boxes and their alt text as separate elements. Fixed: Center-aligned text shifted left when the Accessible Text setting was enabled on the player. Fixed: Hyperlinks sometimes behaved erratically during keyboard navigation. Other Updates Interested in building your accessibility skills with others? Join our upcoming Accessibility Peer Pod in Q4. New Articles Storyline 360: Improving Video Accessibility with Audio Descriptions Updated Articles Update to Storyline 360: Our Accessibility Journey HUGE update to the Rise 360 Accessibility Journal! Accessibility Index Updated Rise and Storyline maturity plans: Improved the resolved section with clearer, more positive language and reordered updates so the most recent information appears first. Updated VPATs to better reflect the role of authors and include AI Assistant where applicableNVDA 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.
