Assistance with finding a solution to the JAWS screen reader ‘clickable’ issue in our RISE module
Jun 12, 2019
Hi,
I have researched on the Articulate website and found out that Rise 360 doesn’t fully support screen readers yet, according to the Articulate Accessibility FAQs link below.
"Rise 360 courses don't fully support screen readers yet. We're currently working on screen reader support. Stay tuned!”
https://articulate.com/support/article/Articulate-360-FAQs-Accessibility
”Rise 360 courses don't fully support screen readers yet. We're currently working on screen reader support. Stay tuned!”
However I was wondering if anyone could assist me with finding a solution to the only issue I have been unable to resolve after a sight impaired staff member tested a RISE module I recently created with her JAWS screen reader.
The issue is that the JAWS screen reader is repeatedly saying that the content throughout the module is ‘clickable’ when it is reading the information off the screen.
Is there anything that can be done about this or is it just a simple case of having to wait until Rise 360 courses fully support screen readers?
If there isn't anything that can be done now than it would be really helpful if you could you please provide me with an update on the progress of addressing this issue in RISE ?
I look forward to hearing from someone soon.
Regards Robyn
15 Replies
Hey Robyn!
Rise 360 doesn't have full screen reader support just yet, but we're working on it! If you use a screen reader on a Rise 360 course now, you may find that it doesn't perform well.
We'll let you know when screen reader support is ready!
Thanks Alyssa. I look forward to when you have enabled full screen reader support.
Is there an eta on this? Looking through the comments it's been on the cards for 2 years. We can only legally use accessible software, and at the moment Rise misses out whole chunks of text when using a screen reader - is there a list of blocks that work with screen readers?
I'm sorry I don't have an ETA to give you, Jemma. I can't specifically endorse any blocks for screen reader support since it isn't finalized at this stage.
We'll let you know an update as soon as we can.
Adding my voice to this discussion to be kept updated.
Yup, I have a visually impaired colleague who cannot tab correctly in Rise as it skips sections and also reads out the underlying content not on the screen sometimes. Is there a way to manage the tabbing sequence?
Hi Darren,
Learners should be able to navigate Rise 360 courses entirely with their keyboards. This article explains how.
You may still see issues using a screen reader with Rise 360 because screen readers are supported yet. We're working on that, and we'll update you when it's ready!
We are creating a course that needs screen reader support. I keep seeing the statement "we are working on it, stay tuned etc. What is the actual ETA??
I'm sorry I don't have a firm ETA to give you, Marianne. Our target timeframe for WCAG 2.1 compliance is by the end of 2020, but of course we'll let you know if we reach our goal sooner than that.
Any word on this?
We're still on track to be WCAG 2.1 compliant by the end of 2020. Thanks for checking in, Patricia!
Hi - any updates on this? I am having this same issue in Storyline 3
Hi Kristy! It looks like Lauren answered your question in the Storyline forum here! You can keep the conversation going in that discussion if you'd like!
Hi - thanks! The other forum is a different question though (the accessibility of markers and if screen readers can read marker text). This one is about why JAWS is reading "clickable" throughout my Storyline 3 course when there are no clickable elements - only plain text. As an example, I have a screen of plain text in a textbox on the screen. As JAWS reads through it, it is randomly announcing the word "clickable" in the middle of sentences. There is absolutely no clickable content on the screen. It's two text boxes ( a title and body content) and an image. It does this throughout my course.
I am wondering if others are having the same problem with their courses? I am using Chrome, JAWS and Storyline 3.
Hello Kristy!
I'm happy to help! Unfortunately, the issue where JAWS announces "Clickable" continuously is a common complaint with JAWS. It reads "Clickable" on websites as well. One suggestion is to change the settings in JAWS under the Web/HTML/PDF section.
Here's a screenshot:
They suggest unchecking the box next to Indicate Element Attribute.
Please let me know if that does the trick!