360 Degree Image Accessibility
Hi, I have an accessibility issue with 360 degree images and hotspots. I have a 360 formatted jpg that I inserted and I added 4 hotspots with labels that tell the user whether the hotspot is correct or incorrect. However, using the tab button, it has been consistently getting stuck on the first 2 hotspots and going back and forth instead of cycling through all of them (and the player buttons). Also, it seems like the arrow buttons don't work automatically as soon as the image loads -- I am assuming this is because it's not in focus and needs to be clicked before the arrow buttons respond (which kind of doesn't help if the person can't use the mouse). I'm mostly concerned about fine motor skill disabilities, but also for blind users. My project is for a government org so I've basically just created a workaround where if the user cannot complete the activity, they can hit Esc and an alternative form (a layer with text on it) will show up and the next button will be enabled. That's OK, but am I missing something around best practices for accessibility with 360 degree images? Vimeo and YouTube seem to have it down really well with keyboard controls but I understand there are additional factors with interactives on the 360 degree images in SL. What, if anything, else should I do to make this more accessible via keyboard and screen reader? I know I could use some javascript to autofocus the image so arrow keys work, but that seems like it should be built in already if it's the only thing on the slide. Thanks for any guidance you can provide.Disabling Background Music
Hi there, Is there a way to allow learners to enable background music after launching a course, rather than having it turned on by default? Currently, background music plays automatically, and learners must manually turn it off each time they launch a SCORM package. Some learners find this inconvenient, especially when accessing the course repeatedly. Ideally, we’d like an option within the player settings that allows learners to turn on background music only if they choose to, after the course has launched. Any guidance on whether this is possible would be greatly appreciated. Thanks in advance for your help. Best regards!Rise 360 Mobile Issue: Exit Course Button Blocking Labeled Graphic Navigation
Hi everyone, We’ve created a microlearning in Rise 360 that includes an Interactive Labeled Graphic with two clickable hotspots. During course preview, the mobile view displayed correctly and as expected. However, once the course is exported as a SCORM file and launched in our LMS, the required “Exit Course” button overlaps the labeled graphic navigation controls in mobile view. As a result, when learners open the interaction, their only option to proceed is to exit the course. We’ve attached an image showing the labeled graphic navigation being blocked by the Exit Course button. The grey box in the screenshot is included only to obscure confidential course information. Has anyone encountered this issue before, or is there a known setting or workaround that allows us to keep the required Exit Course button while still using this interactive feature in mobile view? As a temporary workaround, we’ve advised learners not to use their mobile for this course; however, many of our front-line employees prefer mobile learning, so we’re hoping to find a more sustainable solution. Thank you in advance for any guidance or best practices you can share.How do screenreaders read headers in Rise?
Do the header blocks in Rise translate to H1 and H2 for screen readers? It looks like it's more simple, just header and subheader. I have been thinking of the lesson title as H1, a header as H2, and subheader as H3, but is that right? Actually, now that I write this, I realize I've been thinking of the lesson title and the header block both as H1. Thinking of accessibility formatting, how does this work out?Rise Subheading Not H3 in WAVE
My team and I are developing courses in Rise. Upon reviewing the structure using WAVE, I see the subheading with paragraph block is not registering as H3. Paragraph text that is assigned H3 is registering correctly. Are we using the subheading with paragraph block inappropriately?Close button on Lightbox not working correctly with JAWS
Our accessibility vendor reports that when using a lighbox, the close button [the X] is not labeled when JAWS users first tab to it. Additionally JAWS users cannot reach it while navigating with the Read All command or arrow keys, and it is not in the buttons list. They add: It is read appropriately when tabbed to or when pulling up a list of buttons.
