Forum Discussion
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.
9 Replies
Hi cinlove!
Sorry to hear you're having trouble navigating a Rise 360 course with the JAWS screen reader!
Our team has identified a Rise 360 issue causing screen readers to focus immediately on a Process Block's navigation buttons, skipping over the slide content from the Block itself. After a recent Rise 360 update, we determined that the Process Block behaves like a carousel, and screen readers should dictate a Process Block in the following order:
- Controls
- Previous Button
- Next Button
- Process Block Slide Content
However, when testing this on my end (with JAWS), I was unable to switch focus to the slide content itself. I would like our support engineers to have a closer look at this issue, so I've opened a support case on your behalf. Also, it would be helpful to see a copy of the Rise 360 course you're working with. I've sent you an e-mail with steps on how you can share that privately.
You're in excellent hands troubleshooting with our support engineers, and we can continue the conversation through your case.
Thanks for responding, Steven. Please let me know when there is a solution ready.
Hi cinlove!
Thanks for following up!
Our team would be happy to review your Rise 360 course, and test its playback with the JAWS screen reader. It's possible you may have missed the e-mail I sent on 07/18/2025. No worries! I've just resent that e-mail again, for your reference.
Please let us know if you've received it!
Removing link
Hi, cinlove!
I've added this link to your support case so our Support Engineers can take a closer look.
Hi,
I have also received the same feedback from our accessibility testing team. Unfortunately our in-house restrictions prevent me from accessing the support function via the work network so cannot share links to the content. Would it be possible to include me in the support ticket (or send me an email confirming it is under investigation so I can evidence it has been raised and is being addressed!)?
KellyAuner Our Accessibility team faced the same issue with the process block. We are using Jaws. The screen reader is reading it has list of items. So if we have 4 steps, its reading list with 6 items, and ignoring the start process button, its reading step 1 as list 2 and so on. Ideally it should be "The start button will launch the modal and when the user clicks on "Next"/"Previous", set the focus on the newly visible text (for that, ensure the text is in a paragraph "p" with the attribute tabindex="-1" and move the focus with the function "focus" function) When the user closes the modal by any mean, move the focus again on the "Start"/"Begin" button with the JavaScript "focus" function.
Any solution to this would be helpful
Hi SudeepaGanguly!
Sorry to hear you and your team are also experiencing this setback!
As I've shared with others, it's easier to troubleshoot this type of behavior if we could see a copy of the affected Rise 360 course. I've opened a support case on your behalf, and sent you an e-mail with steps on how you can share that privately with our team.
You're in excellent hands working with our support engineers, and we can continue the conversation through your case.
