Forum Discussion

cinlove's avatar
cinlove
Community Member
5 months ago

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 r...
accessibility
advice
Articulate 360
articulate 360 teams
rise 360
SudeepaGanguly's avatar
SudeepaGanguly
Community Member
5 months ago

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

 

  • StevenBenassi's avatar
    StevenBenassi
    Staff
    5 months ago

    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.