Forum Discussion
PROCESS block is NOT Accessible
Hello all,
We are developing Rise accessible courses. While using the PROCESS block, we found that it is not accessible, even though Articulate Rise states that it is accessible. The issues we are currently facing are:
- When using keyboard navigation (Tab/Shift+Tab), the focus skips the interactive navigation buttons below (1, 2, 3, etc.) and jumps directly to the next content.
- The reading order is incorrect. When the user presses the down arrow key, the focus moves to the bottom of the page, but the screen reader does not move focus to the start button or the slider content.
Regards,
Shraddha
9 Replies
- thomaspeavey-54Community Member
Hello ShraddhaM. I opened Case #01251289 on 12/9 regarding this exact issue.
Thomas - ShawnMcCreightCommunity Member
Hello! has there been any update on this? I am curious as I have run into the same issue
- KellyAunerStaff
Hi ShawnMcCreight,
Thanks for reaching out!
Since this original post is now close to a year old, I’d love to better understand what you’re experiencing and how it’s impacting your experience. Could you share which part of the process block you’re finding inaccessible and which screen reader you’re using?
I also want to share this resource on accessibility in process blocks, and the thinking behind our approach!
- ShawnMcCreightCommunity Member
Hi Kelly, what happens is the keyboard instructions are to use tab, then the arrow keys to navigate the content. What we experience with ALL the carousel type blocks is, we can use TAB to arrive at the navigation controls, but the arrow keys never arrive on the content. we are using JAWS. How is a JAWs user to navigate and interact with these types of blocks?
- thomaspeavey-54Community Member
Hello. When using NVDA, I am unable to read the introduction slide when beginning the interaction. I need to navigate to the next slide, then return to the introduction slide to read the information on the introduction slide. It would be helpful if the learner could read the content in the order it is presented. Not sure if this occurs with JAWS.
Thanks for bringing this up, thomaspeavey-54. Having to move past the introduction and return to it to access its content sounds disruptive, especially when learners are trying to follow the interaction in order.
Our team has logged this NVDA behavior as a bug, but we don’t have a fix or timeline to share right now. I’ll check whether there’s any additional information, including whether the same behavior has been confirmed with JAWS, and share anything I learn here. Your description helps us understand how this affects learners using a screen reader.
Hi thomaspeavey-54! I wanted to check to see if you've seen our updated documentation as it relates to screen reader use with the Process Block. Our team updated the article after hearing similar feedback from other users, so I hope it adds helpful context for your setup too.
- thomaspeavey-54Community Member
Hi LaurenDuvall. Yes, I have read the documentation. However, when first landing on the process block (step controls), there is no keyboard action that will activate the introduction content. Since our courses have useful information about the process on the introduction slide, it would be helpful for the learner to be able to read it before navigating to the additional steps. The current format does not allow this when using NVDA. I believe this is related to the 'meaningful sequence' or 'focus order' in WCAG. Thanks!