accessibility
204 TopicsNVDA and RISE move from TOC to topic and...
Hi there, I am learning it is challenging to test using NVDA when you don't have the special keyboard or you are really unfamiliar with its use. For the most part I seem to be able to bounce around, and noticed when my mouse hovers over a section it starts talking (i don't recall this before), What I am struggling with is the initial start. I launch the course listen to the intro, press start, tab down to my first topic lesson objectives, I thought I would right arrow over to the content and then work through, but I can't seem to get over there, if I hover my mouse over there then select the down arrow it seems to move me through. Any tips. Also moving from a storyline block to a timeline block and getting the timeline block to start with the text and not the zoom in on image... Tips would be great, I have googled lots but nothing that has helped me. Thanks T P.S. found the edit button (cog wheel far right, not close enough to my article LOL!19Views0likes2CommentsDo I need to add media controls to MP4s that only shows for 5-10 seconds? 508 Compliance
I will often add MP4 videos from the Articulate library in my modules for very short periods of time - 5 to 10 seconds usually, as I like a lot of movement and visual interest. They are just enhancements, decorative, really, like a video of steaming 0s and 1s when I'm talking about data.. Or if I'm talking about analytics, an MP4 of moving bars and charts that I shrink down to fit within a monitor illustration. Is this practice accessible? I do have them autoplay and haven't been adding start/stop/play buttons, as they are only very briefly on screen. These modules are for a government client and 508 compliance is required. Do I need to add a tiny stop button to say, that shrunken down 'analytics' MP4 playing in the monitor for 6 seconds?24Views0likes3CommentsCanvas support for xAPI and Rise 360
I have an issue with Canvas configuration for an LRS because Canvas does not have a native xAPI support and we found a loophole to this problem by using Storyline and configuring an LRS in the xAPI published package and uploaded it as SCORM in Canvas but the embedded configuration for the LRS allowed for us to get data in our LRS. The institution wants to use Rise primarily which takes away our LRS configuration that Storyline has. Any suggestions on how we can make this work with Canvas? We were thinking a middleware LTI possibly but I wanted to get some opinions on here. Thank you.12Views0likes0CommentsHow to enable Closed caption to show as default from start in Articulate Rise
Dear Articulate Team, Could you guide me on How to enable Closed caption to show as default from the start in Articulate Rise. Do we have a feature to enable CC from the start of the video in Rise. An early solution will be appreciated. Best. Siba10Views0likes0CommentsScrollbars still not working in text entry boxes
Hi all. Are there any plans to make scrollbars work in text entry boxes? This has been an issue for about 6 months now. I've got 'Add scroll bars' selected in the 'Overflow handling' options, but no scroll bar appears. I've attached an example Storyline file. I'm using the latest version of Storyline 360.39Views0likes7CommentsChange slide with Focus Order panel open
I would love if you could change slides when the Focus Order panel is open. I'd like to see the same behaviour as the Format Shape and Size and Position panels, where you can just navigate through slides and check properties with the panels open as necessary. I think this would be a huge difference when checking through your contents focus order for accessibility.11Views1like0CommentsLooking for examples of alt text for math equations
Hi everyone, the Storyline team is currently exploring ways to support math equations and we've heard from several customers that accessibility, specifically screen reader support, is very important. But we would like to hear from more users to make sure we deliver something that's actually usable and valuable to you. If you use equations, could you share how you approach alt text for accessibility? Do you use short descriptions, long descriptions, or both? We'd also love to see examples of how you describe specific equations to better understand your process and needs. Your feedback will help shape this feature! Annie Kim Product Manager, Storyline284Views5likes7CommentsStoryline 360 not compliant with WCAG 2.1 AA accessibility guidelines
I see that Articulate claims on this page that "Storyline 360 supports WCAG 2.1 Level AA, including screen readers, keyboard navigation, visible focus indicators, and more." I'm confused though, because Articulate also highlights on page 11 of its Accessibility Conformance Report here that Storyline 360 is not compliant with WCAG 2.1 (Level AA), based on the fact that its text input fields do not support WCAG criterion 1.3.5: Identify Input Purpose. It also states that it does not meet criterion 3.1.2: Language of Parts. Obviously, if Articulate 360 only supports most of the criteria for Level AA, but not all of the criteria, then it is does not satisfy the requirements of WCAG 2.1 (Level AA) compliance. Therefore, I have advised my client that their requirement of WCAG 2.1 (Level AA) compliance cannot be achieved if we use Storyline. Could you please clarify if the report is now outdated and if any recent improvements to the software allow it to meet criteria 1.35 and 3.1.2? That is, is Storyline 360 now compliant with WCAG 2.1 AA, as per the claim on this page?89Views0likes26CommentsScreen Reader Not Reading Button States
Hey everyone, I noticed that after the last couple of Storyline 360 updates, my screen reader (JAWS and NVDA) no longer reads the alt text for button states. For example, I added "visited" for the alt text under the button's Visited state. This used to work fine but now the screen reader does not read the "visited" alt text and just reads the alt text for the normal state. My screen readers are up-to-date. Has anyone else experienced this?71Views0likes9CommentsAccessibility 360 images
Hi! I have run into a problem with keyboard accessibility on the 360 images. Using NVDA screen reader. When the slide first loads, the hotspots and markers are able to be accessed by keyboard (good) but if I click on a hotspot or marker to show a layer, once the layer is closed, I can't tab to any of the hotspots or markers again. The arrow keys still work to move the image and I can access the button that is on top of the image. Is there something I'm missing? Example module https://360.articulate.com/review/content/6cc9596b-1250-4685-8322-ba85bf2e8def/review12Views0likes1Comment