Storyline 3 supports JAWS 16 or later with Internet Explorer 11, Google Chrome (latest version), and Firefox (latest version). You'll want to stick with those browsers to ensure the screen reader works correctly.
I have also updated my Google Chrome and Mozilla as per your suggestion
My Course output is working fine on Google chrome with Jaws reader 16 as well as 18.
When i am running my course on Google chrome it reads some extra text with each image that is, "Read only" i don't know where it is coming from but this is the only issue till the time.
As per the above comment, i have updated my Mozilla Firefox with latest version (63.0.3) but i am still facing issues with Jaws reader 16.
After some research, i found that Jaws 16 will not work on Mozilla version 57 or above as per the Mozillas official communication/notification. You can refer the same from the below link:
I have another issue with Mozilla Firefox in reading the dynamic text fields with jaws reader 18.
We have used variables and fetching these variables in text fields, for example page numbers are populated dynamically.
On one dynamic text field, Firefox jaws is not reading the text when the user presses the tab key. However, we can see that text field is selected. And on another text field, we are having the exact opposite issue, we cannot see the selection on tab key, but jaws is reading the text.
This issue is only occurring in Firefox (With Jaws reader 18). It's working as expected on IE 11 and chrome. Please let us know how we can resolve this in Storyline 3?
Hi there, Malkeet! Thanks so much for those helpful details regarding JAWS and the latest version of Firefox. We were able to test and update our documentation as a result of your post! Check out the system requirements for accessibility in Storyline 3.
As for the variable text issue, can you share the file that is behaving inconsistently with JAWS? You can use the Add Attachment button here, or share it privately with me using this link.
7 Replies
Hello, Malkeet!
Storyline 3 supports JAWS 16 or later with Internet Explorer 11, Google Chrome (latest version), and Firefox (latest version). You'll want to stick with those browsers to ensure the screen reader works correctly.
Hi Alyssa,
Thanks for your support on the above point.
IE 11 is working perfectly fine with me.
I have also updated my Google Chrome and Mozilla as per your suggestion
My Course output is working fine on Google chrome with Jaws reader 16 as well as 18.
When i am running my course on Google chrome it reads some extra text with each image that is, "Read only" i don't know where it is coming from but this is the only issue till the time.
Can u help!
Hello,
As per the above comment, i have updated my Mozilla Firefox with latest version (63.0.3) but i am still facing issues with Jaws reader 16.
After some research, i found that Jaws 16 will not work on Mozilla version 57 or above as per the Mozillas official communication/notification. You can refer the same from the below link:
https://support.mozilla.org/en-US/kb/can-i-use-my-screen-reader-new-firefox
Please confirm so that we don't spend any further effort trying to make Jaws 16 work on the latest version of Firefox.
Hi Alyssa,
I have another issue with Mozilla Firefox in reading the dynamic text fields with jaws reader 18.
We have used variables and fetching these variables in text fields, for example page numbers are populated dynamically.
On one dynamic text field, Firefox jaws is not reading the text when the user presses the tab key. However, we can see that text field is selected. And on another text field, we are having the exact opposite issue, we cannot see the selection on tab key, but jaws is reading the text.
This issue is only occurring in Firefox (With Jaws reader 18). It's working as expected on IE 11 and chrome. Please let us know how we can resolve this in Storyline 3?
Hi there, Malkeet! Thanks so much for those helpful details regarding JAWS and the latest version of Firefox. We were able to test and update our documentation as a result of your post! Check out the system requirements for accessibility in Storyline 3.
As for the variable text issue, can you share the file that is behaving inconsistently with JAWS? You can use the Add Attachment button here, or share it privately with me using this link.
Hey Malkeet. Our support team is testing this behavior, and you'll be receiving an email from them with some next ideas!
Looking forward to hear from your team.
Thanks for the Support.
This discussion is closed. You can start a new discussion or contact Articulate Support.