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.
Currently when i use the Tabs key to move different part of the blocks this do not select the Text blocks and any text portion. IS this the way the Tab functionality work as part of the navigation accessibility in Rise?
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!
Hi there, thanks for these updates, have been following along the accessibility journey and just wondering if you are still on track to have screen reader supported in Rise 360 by end of 2020. We are developing a suite of learning that will require this and aiming to deliver this to our learners in December. Realise you can't confirm exact dates, but is this still on track for 2020? Thanks so much.
@Crystal - Following on with Alice. While we recognize that specific dates and times are hard to put out there. We are also looking at rolling out a large initiative to over 10K employees and are pressed to decide on going with Rise as the primary delivery or Storyline. Any guidance would be greatly appreciated!
Yes - the last update seems to be in August. This seems to be pushing Rise quiz banks and autoplay to the back burner, which will actually be more useful to me.
10 Replies
Thank you for sharing this info, Alyssa. Looking forward to future updates.
Currently when i use the Tabs key to move different part of the blocks this do not select the Text blocks and any text portion. IS this the way the Tab functionality work as part of the navigation accessibility in Rise?
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!
Thank you!
Hi there, thanks for these updates, have been following along the accessibility journey and just wondering if you are still on track to have screen reader supported in Rise 360 by end of 2020. We are developing a suite of learning that will require this and aiming to deliver this to our learners in December. Realise you can't confirm exact dates, but is this still on track for 2020? Thanks so much.
Hi, Alice. We're working hard to meet that goal!
@Crystal - Following on with Alice. While we recognize that specific dates and times are hard to put out there. We are also looking at rolling out a large initiative to over 10K employees and are pressed to decide on going with Rise as the primary delivery or Storyline. Any guidance would be greatly appreciated!
Yes - the last update seems to be in August. This seems to be pushing Rise quiz banks and autoplay to the back burner, which will actually be more useful to me.
Hello everyone! I’m happy to share our Rise 360 Accessibility Collection, which includes the VPAT to describe how Rise 360 conforms to WCAG 2.1 Level AA criteria.
We also updated our roadmap to include Rise 360 features we’re continuing to develop to better support WCAG.
Let me know your questions and experiences building accessible courses for all!
Thank you, Alyssa and team. This is an exciting step! And thanks for the detail on the VPAT... very helpful.
This post was removed by the author