Rise 360 Accessibility Journey

Our team has been working behind the scenes to make accessibility improvements to Rise 360. Now, we’re ready to reveal what we’ve accomplished so far! 

We know how important accessibility is to you, so we put together a journal where you can find all the details on the features we’ve enhanced in Rise 360 as we work towards WCAG 2.1 compliance. And we’ll keep this journal updated as we continue our accessibility journey.

Click the link below to check it out!

Rise 360: Our Accessibility Journey

4 Replies
Alyssa Gomez

Hello, SibaPrasad!

Thanks for your note. I'd like to differentiate between keyboard navigation (Tab/Arrow keys) vs. screen reader navigation

Keyboard navigation (Tab/Arrow keys) helps users navigate to the interactive elements in your lesson with the use of a keyboard. Interactive elements are objects you can click to perform specific tasks, such as buttons, hyperlinks, and zoomable images. As you've noticed, you won't be able to tab to text elements because they are not clickable/interactive. 

Screen reader navigation doesn't exactly use the Tab key to go from one element to another. Screen readers have their own controls to navigate through page elements, both interactive or static text elements. Your tab focus will continue to jump to the interactive elements on your page, and your screen reader will read the active selection. If you would like to read all the visible text elements on your page, you must utilize the screen reader's navigation controls. This also depends on the screen reader you are using. 

Please keep in mind that screen reader support isn't ready yet, but we're hoping to release that enhancement soon. Stay tuned!