Issues with NVDA screen reader and multiple choice questions within Rise 360
Our team is currently working on a Rise course around accessibility in the workplace, and of course this entire course would need to be fully accessible in the broadest sense of the word. We have been testing and developing our first few lessons within Rise 360 and have come across the following issue: when using only keyboard navigation and the NVDA screen reader, if the user answers a multiple choice question, it seems as if the focus of the screen reader shifts towards the sidebar. It begins reading all of the lesson titles, instead of the intended behavior of stating if the answer is correct or incorrect and then reading the feedback. This behavior does not occur with JAWS. We have also tested this on various PC's, NVDA settings and both a preview and published version of the course. It also seems to occur in clean projects containing just a multiple choice question block. Any advise on this matter is welcome. Thank you!Building a course that is navigable using Dragon (or similar)
Hi, I work for a Public Sector organisation, and want to make my courses as accessible as possible. I have alt text and reading order sorted, but wanted to ensure that my courses were navigable by voice navigation using Dragon or something similar. I really just need to know where Dragon takes it's name for the objects on the screen from. For instance, if there is an activity and the user has to select three objects, I want to be able to add in navigation prompts to the slide for instance 'voice navigation prompt - use raindrop 1, raindrop 2 etc'. Do I need to add alt text to the objects, or does Dragon read the object title that's displayed on the timeline? Or am I overthinking this, and Dragon makes it clear to the user what the object is called and so what they need to say to select it? thanks!AI Text to speech not updating closed captions
When I create a new AI text-to-speech file it adds captions just fine. * But when I go to update that file on the timeline, even with the "generate CC" box checked, it still has the old captions. If I delete the existing captions, re-generate the audio with the box checked, and save, no new captions appear. What can be done about this? * Also, the AI generation doesn't honor SSML very well. I can't correct its pronunciation of certain words without writing the prompt phonetically, then manually changing the CC every time I update the script.HIPAA and Accessibility Readers
Anyone else struggling to get JAWS or NVDA to read HIPAA and like terms correctly? Support suggested I write it as Hip-Uh in the alt text so I went back to every text box that had the word written as HIPAA and replaced it and now I have many accessibility issues because the limit number of characters for alt text is 150 and some of those paragraphs went far beyond 150. Any suggestions?Accessibility Audit Results - Headers/Statements
I assume and from what I can see many others are encountering issues with RISE controlled elements appearing on Accessibility compliance audits and reports. I have a number of items that appear to be outside of the authors control, and on the other hand I see Articulate reporting as recently as yesterday that they are fully compliant. What concerns are others encountering, and what work arounds have folks identified to address concerns? From my end, some of my most common flags are: Critical - Pulsing marker on interactive graphics can not be turned off, or set to stop after 5 pulses within RISE solution (ie:without use of custom CSS). High - Text is cut off when user increases text spacing. (ie Flip cards, and knowledge check results). Solution again seems to only be in custom CSS. High - Knowledge check question headings are aria-hidden. When using JAWS, this causes the heading to not be announced. Medium - Non text Contrast do not meet minimums for Lesson completion status icons (circles), audio player bar. (Rise says is the is the authors responsibility but even on white background it fails. Medium - Checkbox lists are double labelled. "Inputs have aria-labelledby and label element" Medium - All buttons, and most labels force to ALL CAPS even when label is suctom set to sentence case. Has anyone had any luck overcoming any of these or getting Rise to actually address them? Or do you have others to add to the list?Equation Builder and JAWS reading it as a button
Our 508 review team indicated JAWS is reading the LaTeX equation as a button, which is not 508 compliant. This is what I have: This is how it appears (correctly): This is how it appears in the focus order under Alt-Text After JAWS reads the alt-text, it verbalizes "Button." This is not 508 compliant per our review team, as the impaired learner expects it to act like a button and attempt to click it. Is there anything wrong here that can be fixed, so JAWS does not read the equation as a button? Thank you.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.
