Custom Player Tab with Keyboard Shortcut
Hello! I recently watched the webinar on How to Create an Accessible Drag-and-Drop Interaction in Storyline 360 and in there they show a custom player tab that shows all the accessibility controls. It looks as though it has a keyboard shortcut enable for the custom tab itself, and I was trying to find information on how to do that. They mention it was covered in another webinar called How to Create Accessible Courses with Articulate 360 however it seems as though that webinar was updated and no longer covers the custom tab. I like to include a 'navigation help' screen in my courses for people who are unfamiliar with the storyline player, or just not as tech savvy and may need assistance, but I cannot figure out how to add a keyboard shortcut to that menu to make it more easily accessible to those not using a mouse. Can anyone point me to the original webinar where that subject was covered, or maybe fill me in on how they added a keyboard shortcut to that custom menu tab? Thanks!Accessibility Issue
We are developing an accessibility compliance course for one client. we have set Focus Order in text+ image screen. We have published the course to review 360 and tested using NVDA software. While testing we noticed that it's not reading alt text for image in sequence. when we go back by clicking up arrow and then click the down arrow it reads the image in sequence. Please guide us in this case.Rethinking Storyline's Accessibility Checker Guidance on Accessible Video Controls and Autoplay
Storyline’s new accessibility checker is a very useful tool and can be leveraged to create more accessible courses. However, the guidance on disabling autoplay and turning on accessible video controls appears misguided. The following course passes the accessibility checker but has two playback controls that are not synced together. Please visit the Inaccessible Course Example. This design would not be very usable or accessible. For context, the courses I am working on include transcripts in each course's notes section. Can someone show me an example where the accessible video controls feature is implemented successfully? Is there a way to avoid duplicate player controls? Why can’t the transcript feature be included in the main Storyline player? Including the transcript feature could alleviate the need for accessible player controls and improve the learning experience. Also, it would be great if the AI workflow could create captions and add a transcript automatically. This would be a significant time saver. The accessibility checker should prompt the author to check the captions and transcript to ensure they are accurate as well. Another issue is the autoplay setting. The accessibility checker makes it seem straightforward to turn off autoplay. The author needs to set the option “Play video” to when “clicked” or “triggered.” Unfortunately, this change causes the Storyline Player to not control or stay in sync with the video. Implementing autoplay globally across a course appears to be much more complex. The University of California’s Office of the President has an article called, Avoiding Autoplayed Media. This article goes into the technical steps required to configure autoplay for a slide or a course in Storyline. It does not reference the “Play video” toggle. Instead, the author must leverage triggers and variables in the project to stop slides from autoplaying globally. In this example, I configured a trigger to stop the video when the rectangle appears on the slide. I configured another trigger to start the video when the rectangle leaves the slide. I also used guidance from How to Pause and Sync Videos with Timeline in Storyline 360. This is because by default, Storyline enables “Pause on click.” However, the video can get out of sync with the timeline if clicking on the video pauses it. This technique creates a variable to track when a user clicks the video to ensure it stays in sync with the Storyline player. This technique is necessary to ensure the learner does not get the timeline out of sync with the video. This No Autoplay Course Example incorporates those techniques. Is there an easier way to stop slides from autoplaying? Would Articulate consider adding an autoplay option to Storyline’s player? If Articulate included this option as part of the player controls, it would be significantly easier to implement and be available on most Storyline courses. This would allow learners to toggle autoplay on or off, similar to how platforms such as YouTube operate. Authors would not need to dedicate time to configure this option. My last suggestion is to consider incorporating a manual check tab in Storyline’s accessibility checker. The checker currently does not guide authors on how to review the focus order of each slide. The checker could provide guidance on how to use the focus order tool and check the color contrast of each slide. It could also provide information about accessible button names and how to ensure they are consistently represented across button states. For example, PowerPoint will flag a slide as having a read order issue if the order is different than how the content is presented visually on the slide. The author must manually check the read order to confirm that it is correct. Storyline could implement a similar feature or use AI to provide some guidance on potential focus order issues. Thank you for your time, and I appreciate any feedback you can provide.Focus Order, Accessibility, and Set Focus
Okay, I need some help please. I was contracted by a company working on this gigantic project (over 150 storyline files) that are non accessible and they wanted screen reader accessibility. Granted, this project has been in the works for 8 years, and changing how they built stuff is not an option. They use a lot of modal layers instead of dialog ones, which seems to cause a lot of problems for Screen Readers. Every time you open a new layer, NVDA loses focus. To rectify this, I've added a "Set Focus" on "Text" when the timeline starts on "Text" in the new layer. This fixes the screen reader, but for non screen reader users, it adds that ugly yellow square that looks like a glitch if you don't know where it's from. I see a lot of posts here saying Set Focus isn't the best trigger....but when I don't use it, opening layers is a nightmare and I have to find "Back to top" and start over, which can be infuriating, and I would be infuriated if I needed to keyboard nav this project. I just found out that unchecking "Prevent users from clicking on other layers" seems to make this work without a set focus....but I was keeping that checked because if you use back to top in a layer, you have to recycle from the beginning....and some slides have like....12 layers ... ouff. Does anyone know what could be done without drastically renovating way too many files and layers?Accessibility 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.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!Activating subtitles / Closed Captions by default
Hello, I want to display subtitles by default on a video in Rise360. So I Edit the video and upload a vtt file. Then on the video the user can click the CC button to display the subtitles I choose. Is there a way where the learner doesn't need to activate the subtitles, and that it can already be on a defined langage (or the only one in my case), instead of the default: "Caption off"? Thank youClosed Caption issues with AI Text to Speech
Hi all I am loving the new AI Text to Speech voices but have found an issue with the Closed Captions. The Closed Caption placeholders are not lining up or splitting where expected. Image 1 is how the closed captions are displaying for the voice to text. Image 2 or 3 are both examples of how I would expect the captions to display, with the placeholders aligned to speech. Either of these would be acceptable. Is anyone else experiencing this? Not sure if this is a bug or an enhancement request or if I'm missing something? Thanks all! Niki Stoyles
