Text Entry Field is cutting off half the text
Hi I am having issues with a text entry field. It shows differently on the Preview mode. It cuts off half the text. This is how it shows in design mode. However, when I preview it it shows like this. I would like it just to show Line 1 in full and when it overlaps into a new line it shows line 2. The current format of the text entry box is Vertical Alignment: Top Multiline - checked. It's even worse when I amend the vertical alignment to middle. The text box size is 320 px wide and 20px in height. Please can someone offer some guidance how to amend this.Accessibility Issue with Rise 360 Process Block and JAWS Screen Reader
Our team is developing courses in Rise 360 and submitting published versions for review by our Accessibility Team. Although Articulate documentation states that the Process Block is accessible, our reviewers found that these blocks are completely skipped when using the JAWS screen reader. Has anyone experienced similar issues? Are there any known workarounds or best practices to improve screen reader accessibility for the Process Block in Rise 360? Any insight or suggestions would be greatly appreciated.NEW: Accessibility Checker in Storyline
Hey folks, just wanted to make sure you saw Storyline's latest update this week. Included is a feature that's sure to change how you build accessible courses forever. Built into Storyline is now an accessibility checker. With one click, the accessibility checker scans your course and generates a detailed report listing accessibility issues and shows you step-by-step how to fix them. Key features: Real-time scanning: One click, and it instantly finds potential accessibility issues. Guided fixes: It doesn’t just find problems, it shows you exactly how to fix them and includes one-click fixes. Learn by doing: You organically pick up accessibility best practices as you build your course. Documentation: Storyline 360: Improving Experiences With the Accessibility CheckerJAWS Not Reading Tab Order Correctly on Assessment Slides
Hi everyone, I’m running into an issue on the assessment slides in my Storyline 360 project where JAWS is not reading the tab order correctly. The user tested it using both the Tab key and the Up/Down arrow keys, but JAWS jumps around the screen instead of following the expected reading order. I’ve already updated the focus order to reflect the correct sequence, and all objects are visible to accessibility tools. My version of Storyline 360 is up-to-date. Has anyone else experienced this or have suggestions for further troubleshooting? Thank you! ShannonTransparent Shapes and States
I like the idea of the accessibility checker, but I am having problems deciding how to do what it is telling me. I am also having issues with the flow because some items are on the base layer and some on layers. How do I set the order when the layers are meant to be popup information? I am building a game that needs to be accessible. The problem is it has transparent shapes that bring up images on hover. Those images have a lot of text that is too much for Alt Text. The Shapes also have a Selected State that shows a check mark when selected. This all works great of sighted people but how do I handle them with keyboard and screen reader? How do I help the keyboard or screen reader tell the person what is going on? The Accessibility Checker tells me I have to have the video controls on, but I do. It shows me things that I have working, why are they appearing on the list?How can I restrict the right arrow key from jumping to the next slide until the timelines end?
I’m currently working on a project that includes 508 compliance, focusing on keyboard navigation. Specifically, I want to restrict the Right Arrow key from advancing to the next slide until the current slide is completed. I created triggers in Articulate Storyline to manage this and also locked the slides using the menu options. However, the restriction only works on the first slide—keyboard navigation doesn't work as expected on the remaining slides. I’ve tried using both SlideComplete and AudioComplete variables, but neither approach is working consistently. Interestingly, the logic works fine with mouse clicks, but not with the keyboard. Has anyone experienced this or have suggestions for making keyboard navigation work properly across all slides? Please help me with this issue! ThanksButton States Read as "Unlabeled" by Screen Reader
Hello! I am experiencing an alt text 508 issue. I created a chapter selection screen where each chapter is represented by a sticky note with the name of the chapter, and an icon indicating it is ready to start or revisit. Each sticky note has 3 states: normal/default, a state change that occurs when the previous button was selected (i.e., after chapter 1 is selected, chapter 2 changes to say "start"), and a state change that occurs when it is selected (showing a replay button). I have used custom states and triggers to accomplish this and everything is working well. The issue is that these buttons' custom states are being read by a screen reader as "unlabeled one button" or "unlabeled two button," etc. I have gone to each state and added alt text (e.g., Chapter 1 - selected), but it's not being read correctly by the screen reader. This is posing a 508 accessibility concern. Does anyone know why these buttons' states' alt text isn't being read by the screen reader?Rise lesson headers - Small too small, but Medium too large
Before I submit a feature request, I wanted to see if others are dealing wth the same conundrum. The Small size for the Lesson Header is significantly smaller than the Medium and, given the lack of controllable text size options, doesn't feel like a separate header and can easily be confused as just being another content heading. Colored backgrounds and images help, but not enough. The Medium is such an increase in the vertical space taken up by the header that learners with slightly older laptops with lower screen resolutions or need to be zoomed, may have their window dominated by the header. So, they clearly see a header but have to scroll to get to the content/interaction. We don't even bother with the Large. Is anyone else trying to find a happy place between these options - a sm-edium? For example, if the Small had options to make the text larger, or if there was an option where the vertical space was between the Small and Medium, it would be a great improvement for us.How to add iframe title?
Our Higher-Ed client performed 508 testing on our Storyline presentation. They reported that "The iframe does not have a title" as it relates to A11Y-3447. The ANDI Output states " Iframe has no accessible name or [title]." I relayed back to the client a reply from an Articulate staff member I found on another discussion but that did not satisfy the client's expectations. ("A course in Storyline 360 doesn't use an individual webpage or iframe for each slide. We meet this criterion with Storyline 360 by displaying the course title as the page title that appears on the browser tab. Screen readers announce the course title (i.e., the page title) when the course first launches.") We then tried to force an iframe title into the published SCORM output, but it seems to be stripped out upon playback testing. Is there a way to force an iframe title into the published output?
