Process Block Accessibility Issue
I perform accessibility testing on a lot of Rise content, and one of the most frequent issues I raise is the focus order of the "Next" button for the first slide of the Process Block potentially causes problems for screen reader users. The issue is, that when using a screen reader, the "Next" button appears in the focus order prior to the content on the first slide. This means that a screen reader user could miss the content on the first slide if they were to go ahead and select the "Next" button (which seems logical) rather than continuing down the page to the contents of the first slide. My suggestion would be to remove, or add an aria-hidden="true" to the Next button for the first slide. This would then allow screen reader users to continue down the page to the contents of the first slide and use the START > button instead. I'm sure I have logged this as an issue in the past, and will do again, but just wanted to raised it here so I can track the issue.New attempt with free seekbar but reset quiz
I've created a course and a quiz at the end. The course setting on LMS is with 3 attempts. There are multiple videos on each slide. I've restricted the seek bar until the learner watches till the end of the timeline Nextbutton will not be activated. When I start a new attempt (after completing their first attempt) on the LMS, I would like the learner to be able to freely navigate through the menu and the seekbar. In other words I would all the slides to be in resumed state when the user enters a new attempt but quiz score is reset and they can comfortably take up the quiz. This way they can view what they wish to and learn if they missed out anything necessary to complete the quiz with a passing score. How would I be able to get this? Please assistContent 360 Storyline Templates that Meet AA WCAG Accessibility Requirements?
Hi everyone, I'm a longtime Rise 360 user who is starting to dive into Storyline, and I'm finding it a bit more complex when it comes to accessibility. In Rise 360, many of the templates/sample courses meet WCAG requirements, and if they don’t, I can easily check which block types aren’t accessible via the online list Articulate provideshere. However, with Storyline, I can't seem to find similarly straightforward information. Does anyone have any recommendations for Articulate Storyline templates that meet, or mostly meet, AA WCAG standards? For example, I recently imported the slides from the "Illuminate" template, and while they look fantastic, I noticed some issues right away—like the very light grey font on a white background, which doesn’t meet contrast requirements. I'm really excited to get started with Storyline, but I’d love some advice on which templates might be better to use, especially those that are more accessible out of the box. Any suggestions or tips would be greatly appreciated!Bug dans l'ordre du focus et NVDA
Bonjour, Je vous écris car je remarque un gros bug dans l'ordre du focus sur Storyline. Je suis en train de créer une liste déroulante avec les éléments de liste qui s'affichent dans un calque. A chaque fois que je clique sur un élément de liste, cela à normalement pour effet d'attribuer une valeur à une variable et de fermer le calque. Le comportement attendu (et qui fonctionnait avant) est que lorsque le calque est fermé le focus se remet sur le bouton qui a ouvert le calque en question. Or, lorsque je clique sur le dernier élément de liste, le focus semble visuellement fonctionner correctement (NVDA affiche un contour en couleur sur le bouton qui affiche la liste) mais NVDA lit l'aria-label de l'élément suivant (dans mon cas bouton "valider") pour ensuire lire correctement l'aria-label de mon bouton de liste. J'ai fait plein de tests est le bug persiste. Il n'y a aucune logique dans ce bug 😅 J'ai remarqué d'autres bugs du même type. Tout fonctionne à la navigation au clavier mais avec un lecteur d'écran c'est la cata. Voici un lien vers le Review : https://360.articulate.com/review/content/46333b49-dcb2-4e74-8435-198af003c106/reviewScreenreader reading incorrect question choice text - even after alt text has been changed
Hi, Whenever I create a quiz in a Storyline 360 course (or edit a quiz from a template course), I usually duplicate the question slides to speed up the question creation process so I don't have to reformat the slides every single time. However, when I test the course with a JAWS screenreader, it often reads the OLD question choices text even after I've changed/updated both the question choices AND the corresponding accessibility text for each choice. This means I have to go back and rebuild each individual question slide from scratch so that the screenreader will read the choices properly, since it will only read the "original" question choices text. If Articulate could address and correct this issue in the near future, it would save me entire days of re-work on future projects. Thank you.Student Adjust Lesson Player
Hello, I am doing some research on authoring tools and LMSs for a college course and would like to know if the end user (learner) can modify the lesson player for an SL or Rise course. If so, to what extent are they able to adjust the player? Thanks in advance!! JenniferTheme Color on Tab Label Text
I am looking for a way to turn off the default choice of the theme color on tab labels. I chose a color for my course theme that has the proper 4:5:1 contrast for the buttons, etc. in the course, but the selected tabs on my course show the text in the theme color and it appears I am not able to select a different color for that text. It does not have the right level of contrast. Please help! I am not able to find a color with good contrast there, that will also work with things like the ordered lists.NVDA and Rise Video Player
Hello, anyone else have this issue: We have multiple videos in our course (using Multimedia/Video block. Not embed). When testing for accessibility using NVDA 2024.3, it reads the "Volume Level" button repeatedly. This is causing us to fail accessibility criteria. Has anyone experienced this issue as well? Does anyone have a solution? It is not the project since we have tested on a few and the behaviour is the same. Note: embed YouTube videos don't seem to have this issue. Thanks in advance for any input/ideas!
