Screen readers not working correctly on Rise quizzes
Has anyone had issues with this? We have found that the Microsoft screen reader reads out the incorrect answers that have NOT been selected when doing quizzes. The screen reader will say "Your answer...[insert incorrect answer here]" when it has just said aloud the correct answer you have just selected. See recording here: Devices on the go | Rise 360 - Awesome Screenshot Is this something someone can help with? Is there a screen reader that's better equipped to understand Rise quizzes that we should be using instead? Many thanks,Storyline Text-to-Speech loses neural voice when using hyphens to separate letters
I work for an organisation that has an initialisation in its name and we often create courses with text-to-speech. We use a neural voice (English UK: Amy). The initialisation is also a natural word so I have to specify to TTS to spell it out. A while back I noticed that separating the letters with spaces created too great a pause between each letter, so I started separating them with hyphens, which sounded more natural (e.g. 'D-O-G' rather than 'D O G'). More recently however, any time I try this, the neural voice is replaced by the standard voice. I understand that using SSML tags (<say-as interpret-as="characters">) will cause the neural voice to drop too, so I wonder if hyphens are interpreted as a shortcut to this somehow? But I still have older projects where I use hyphens and this doesn't happen, so I wonder if it's a Storyline issue. Example: Neural voice dropping | Review 360 Example of it working fine in an older project (press the speaker symbol to activate): Neural voice not dropping example Story file attached. Storyline version is 3.99.34516.0Storyline 360 – Random Focus Highlight Appearing on Interactive Elements During Mouse Navigation
Hi Articulate Community, We are working on an accessibility-compliant Storyline 360 course and are facing an issue with the visual accessibility focus indicator. We have enabled a visible accessibility focus color in Storyline because keyboard-only users need to be able to identify which interactive element currently has focus. Expected behavior When a learner navigates using the Tab key, the currently focused interactive element should have a clearly visible focus indicator. The focus indicator should move as the learner moves through the interactive elements using Tab / Shift+Tab. During mouse-only navigation, we would not expect the focus indicator to appear or remain unexpectedly around interactive elements. Current behavior When testing the published course, we are seeing the following: During normal mouse navigation, a yellow/amber outline or highlight sometimes appears around an interactive element. The highlighted element is not always the element we expect to have focus. The highlight appears only on some interactive elements and seems to occur inconsistently. It can remain visible after a mouse click. When we navigate using the Tab key, the focus indicator works as expected and provides a clear visual indication of the current keyboard focus. This creates a visual issue because the focus indicator was intentionally added to support keyboard accessibility, but during normal mouse interaction it can appear unexpectedly and make the interface look as though an element is still selected or focused. The concern is not that the accessibility focus indicator exists. We understand that a visible focus indicator is required for keyboard accessibility, and we want to retain it. Our question is specifically about the unexpected appearance of the focus indicator during mouse interaction. Could anyone confirm whether this is expected behavior in Storyline 360? Is there a supported Storyline setting that allows the focus indicator to remain visible for keyboard navigation using Tab, while preventing it from appearing or remaining visible unexpectedly during normal mouse navigation? Could browser focus behavior cause the Storyline accessibility focus indicator to appear after a mouse click? Are there any known issues in recent Storyline 360 builds involving unexpected or inconsistent focus indicators? We would particularly appreciate guidance from Articulate on whether this is expected browser/Storyline focus behavior, a known Storyline issue, or something that can be controlled through Storyline settings. Thanks in advance!Storyline labelling buttons as graphics
Hi there. I'm having an issue where I have two image buttons names True and False. The set up is the same for both buttons. When I run my course through our accessibility team they are coming back to me saying the True button is labelled as a button, which is correct, but the false button is labelled as a graphic. I'm not sure why the false button is acting differently to the true button. Please can anyone help.Changing Storyline Modes
Hi, Is there a way for a user of a course to change between light, dark and custom modes within Storyline? On researching this, I know that the traditional solution is to create different versions within one course, but can this now be done by changing a setting within the player to give the user the choice at that level? Thank you in advance.Erreur de langue, accessibilité, texte alternatif
Accessibilité : texte alternatif généré dans la mauvaise langue. Malgré les différentes indications, le compte paramétré dans la zone Europe, Paris... tous les contenus générés par l'IA dans Storyline 360 sont en anglais, surtout les textes alternatifs (accessibilité). Pouvez-vous me dire commet remédier à ce bug. MerciDouble/nested heading tags in Rise
In a few recent Rise builds (created between June and August 2026) we've encountered headings established through Heading, Subheading, Paragraph and heading, and Paragraph and subheading blocks that have two heading tags, one nested within the other. E.g., <h3><div><div><h2><span>heading text</span></h2></div></div></h3> (see also attached screenshot). We have not been able to diagnose why this is occurring and haven't been able to purposefully replicate it yet, beyond copying an "infected" heading and pasting it elsewhere, which spreads the issue. It only seems to involve <h2> and <h3> tags. So far, we've seen <h2><h2></h2></2>, <h3><h2></h2></h3>, and <h2><h3></h3></h2>. I don't recall encountering <h3><h3></h3></h3> or any other heading levels. We've been able to remedy the issue by just recreating those blocks from scratch or using paragraph blocks in which we manually assign headings. Sharing just to see if anyone else is encountering this..?How do I export Closed Captions?
My SME said I used the wrong term in the narration in a couple of my slides. He didn't tell me where. Helpful right? I was hoping to export the closed captions to search them for the term but there's no Export in my menu, which is what all the older help info says. Translation doesn't include closed captioning. Is there any way to download the captions as a batch anymore?Rise360 Section 508 Recommendations
Hello everyone, We are running into obstacles with Section 508 compliance, particularly when using Rise 360. While our defects vary in complexity, the main ones that our team is stumped on is "Content is announced in an illogical order," and focus order issues. We follow the same template for all lessons, but I am wondering if anyone in the community has ran into these issues or something similar? We have contacted the 508 office for assistance, but getting an outside perspective on things may be helpful. We keep our lessons fairly barebones, and again use the same template for everything. Are these issues caused by maybe a screen reader setting since we're getting wildly different scores (some courses passed, but some are getting extremely low scores despite the consistency in design), or is it a Rise360 setting we need to adjust? Any guidance is appreciated. Thanks!
