Did an update at some point break my DIY tabs?
I swear this used to work sweet and everyone loved it now it being funky. I've been having to use rise for a bit and this is my first go back on sl in a while. Anyway. So I do this diy tab thing with a main content box and then number boxes to change it, easy peasy. 2 custom states OVER and ON. basically hover and selected but I don't want them auto. The triggers it uses are; <change 1 to over when user hovers over 1 IF 1 IS NOT ON, set content to 1 when user clicks 1 and when content is 1 change 1 to ON and when any other number box is ON set 1 to NORMAL repeated as needed> Hopefully that makes sense and it's all working except for the hover behaviour, its just going back to normal regardless. It works better if I turn off restore previous state but then it stays as over. Are my triggers wrong? Do I need to add an ELSE? Should I turn off auto restore and just put a 99% transparent box behind it to trigger the change instead when user hovers over that? Should I just ditch the over step? (I like clickable things to let you know they're clickable before you click though, OVER also has a 10ms fade in/out because it looks better) See the behaviour here and the relevant triggers/states below. solo page sl file version attached https://360.articulate.com/review/content/bb66506d-ac4a-4e3c-992f-ae476a042d36/review triggers for number box to go over and change content box triggers for setting number boxes to on based on content box triggers for returning number boxes to normal when a different number is clicked number box states content box states (w/o content) Help me articulate forum, you're my only hope.Change HTML source language in Rise course
Dear community, We developed an e-learning in Dutch using Articulate Rise and have gotten it tested on accessibility. One of the comments on the course was that in the HTML of the course the source language is shown as English ("html lang=en"), even though the full course is in Dutch. This results in screen readers selecting the language as English instead of Dutch which causes issues in, for example, wrong pronunciation of words. To overcome this users will have to manually select a different language on their screen readers. I am wondering whether there is some kind of way to fix this and change the source language? Anyone experience with this? Many thanks for your help!Localization proxy language hack in Storyline 360: what can break?
Hi everyone, I’m using the Articulate Localization Add-on in Storyline 360 and I ran into a limitation: the target language I need (Papiamento) isn’t available in the Localization language list. So I’m considering a “proxy language” workaround and I’d love to sanity-check it with the community. What I’m trying to do In Localization, I add a supported language as a placeholder/proxy (e.g., English or Dutch — same script, LTR). I don’t rely on AI translations. Instead, I replace all translated strings manually with my own Papiamento translations (copy/paste). The goal is that the multilingual interface (language selector + localized content) shows Papiamento content everywhere, even if the internal language entry is technically a proxy. In other words: the course would display Papiamento text everywhere (content + questions/answers + feedback), but the language slot is a listed language. Main question Is there anything that could go wrong with this approach? I’m trying to identify pitfalls beyond “it’s not officially supported”. Questions / possible pitfalls (please confirm/deny) Metadata / language tagging: does the published output get tagged as the proxy language (e.g., HTML lang attributes, player language settings, LMS reporting)? Player UI strings / system messages: are those fully editable via Localization, or could some UI strings remain tied to the proxy language? Layout / text expansion: do you see UI/layout regressions when the real strings differ in length from the expected proxy language patterns? Accessibility: could screen readers behave incorrectly if lang metadata remains the proxy language? Maintenance: any gotchas when updating the source course later (re-sync overwriting manual edits, harder diffs, etc.)? What I’m looking for If anyone has tried something similar (using a listed language as a container for a non-listed language), I’d appreciate: What actually breaks (if anything) Best practices to minimize risk Whether you’d recommend a different workflow Context: I’ll publish to [SCORM 1.2 / SCORM 2004 / xAPI / Review / Web]. Thanks in advance!Compatible Screen Reader
Hi, Is anyone able to recommend a free screen reader that is compatible with content published via Storyline 360 (not Rise)? I was under the impression that NVDA (https://www.nvaccess.org/download/) would work, but unfortunately it doesn't seem to. I've attached a sample of the Storyline file in question if this helps. Kind regards, WillAccessibility issues
One of our clients is performing accessibility QC on a Storyline SCORM package using an automated accessibility testing tool. While the client has not explicitly mentioned the tool name, based on the type of issues reported, it appears that a tool such as axe DevTools may have been used. As per my understanding, tools like axe are primarily designed for evaluating custom HTML websites where developers have direct control over HTML structure and ARIA attributes. However, this course has been developed using Articulate Storyline, which automatically generates the HTML and ARIA markup through its player framework. Given these authoring tool constraints, we are unsure how to address certain reported issues that require direct HTML or ARIA-level changes. Has anyone encountered a similar situation, and could you please share how such accessibility findings are typically handled or communicated when working with Storyline-generated content? Also, attaching the list of issues that we received.Storyline Accessibility Issue
Hello all, I am currently building out a course that will have 5 different SCORM files. In files 1-3 the focus order is automatically displaying the course title. Note: The course title refers to the 'Player Feature: Title' that appears at the top of the screen near the menu when participants are accessing the course. File 4 is being very weird and is not displaying the course title at all except for one slide and it displays the wrong course title. The title is set correctly in the player, I have gone into the slide master and am unable to find and turn on/off the slide master title accessibility. In the focus order screen I am unable to delete it or type in alt text. Question 1: how do I turn off the course title in the focus reader while still displaying the title at the top of the screen? Question 2: If I can't do the above, how do I turn on the title so it is also included in the focus order for lesson 4 and is the correct title? Below is what the focus order looks like for file 1-3 with the 'Slide Master - Title' included Below is the focus order with the incorrect Slide Master - Title, it should read "Social Media" instead of "Environmental Scan". Below is the focus order with the missing 'Slide Master - Title' from the 4th fileFeature Request - Enable Screen Reader Support During Preview (by default)
Yesterday, I stumbled across the "Enable screen reader support during preview" feature that was tucked away in the Storyline Options window. Is there a reason why this option isn't checked by default? Apparently, this feature has been around for at least two years (probably longer), but I didn't know it existed and was publishing a new version of the course every time I needed to check something. I attended the webinar on the Beginner's Guide to NVDA and Storyline for Accessibility Testing and this option wasn't mentioned, so I imagine that a lot of other IDs and e-learning developers who care about accessibility are unaware of it as well. I see that the "Use Upgraded Text for new projects" was automatically enabled for me in that same window and was curious about why screen readers weren't given the same treatment as it wouldn't impact users who don't have one installed and anyone who has one can cut it off when they don't want to be in speech mode. If it can't be checked by default, is there a reason why it can't be added to the preview toolbar as well?Localization Closed Captions not appearing on Layers - HELP!
I have a file created in English and translated to French using the localization feature. Due to timeline management, some slides have layers for french vs english. When published, the CCs for only the SECOND layer in the order of layers shows up. So if English is selected as the language, English CC shows. If French is selected, French CC does NOT show. But on this slide below, only the English CCs show up
