custom buttons in Storyline not working with ipad trackpad
Hi, has anyone come across similar issues? Storyline content using player frame for generic navigation (next/back), but has some custom buttons on screen for certain functions. When viewing on an ipad and using a trackpad on a detachable keyboard the buttons in the player work OK, but the custom buttons on screen aren't being recognised. Almost like the player takes the focus? They can be selected by tapping on the screen, just not the keyboard. Anyone found a solution or is it a bug? ThanksStoryline 360 Update 104
Earlier today, we released Update 104 of Storyline 360. This update includes a handful of accessibility related fixes and enhancements. 🛠️ Fixed in this release: Checkmarks on correct responses now provide text alternatives, meeting WCAG 1.1.1. Lightboxes now open reliably when navigation controls are enabled. Screen readers will now announce default alt text for text entry fields Additionally, the Accessibility Checker got an upgrade: scene-level violations now display a thumbnail of the scene making it easier to spot exactly where an issue lives without extra hunting around. The attached gif shows violations for "Scene title defined" and "Scene title distinctive" issues with thumbnails of the affected scenes. Accessibility is one of those areas where small tweaks can have a big impact for learners, and we're always looking for ways to make it simpler to build courses that every learner can access. What else would help you as you work toward your course accessibility goals? Check out the full release notes for Update 104 here: Storyline 360 Version HistoryMute controls across all browser windows launched by the course
Is this even technically possible? Problem: I want to be able to allow learners to have a single audio mute control across a whole course but not impact the PCs own mute settings - when introducing Text-to-Speech to SL360 slides and also Captivate Web Objects launched from button triggers. Any thoughts from the community seeing as this is not wholly Articulate content? Thanks. Currently, it will require: a mute button for the SL360 player, for the slides of the course a mute to be used each time the learner opens the simulation in a new browser window The simple answer, you might say, is to mute the PC and not rely on the mute buttons. However, in the environment where I work, it is important not to mute the PC, as the user might forget to unmute it. Of course, if this isn't technically possible, then that is what they will have to do if they don't want to hear the audio. Why are we not using SL360 for capturing? I have further investigated how capturing works with the extra effort spent. I'm not happy with the downsides compared to using Captivate, as this is for simulation work. No single player bar for the whole simulation - individual bar plays for each captured image Extra triggers required for right-clicks, double-clicks - within the Try again layer Action Fine Tuning more fiddly to edit - even though both products place the click event after the click instead of before it actually happens The only way simulations would work natively (in-slide player) as opposed to SL360 captures also being launched as web objects, is to use the Modern Player as it would need to have controls for fullscreen, but Articulate still refuse to allow customers to customise the player. They force adherence to strict contrast rules, impacting the ability to use Brand colours which still have strong contrast but not enough to meet the rules.Erratic focus order behaviour in Rise course
Hi @ Articulate, can you tell me if a focus order issue has been reported or fixed lately in Rise 360. I'm currently accessibility testing some content for a client and have a found there is a serious issue with the management of the keyboard/screen reader focus when new content panels are revealed. When on a page, if a new content panel is reveal (for example, selecting a continue button), the keyboard/reading focus is returned to the top of the page. This means when using a screen reader, I keep being sent to the top of the page, and then have to use headings to return to where I should be in the page. The same for keyboard, once I select a button that reveals new content, my keyboard focus is back on the title of the page, meaning I need to tab through any content I have previously tabbed through. The content was published on 17/09/2025, and so I am hoping this issue has been an gone and a re-publish will resolve it?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 2025
