I am working on a course that has to be accessible with JAWS - I got some feedback that says JAWS says the word "Graphic" before reading on screen text and that it reads the screen frames overtop of the recorded audio.
Is there anything I can do to prevent this from happening?
Hi Nancy! Sorry you are having issues with this, but I do know that our QA Team has this on their radar and is working on it. I am unable to provide a timeline on that and I am not aware of a workaround though.
My company is developing a course for a major corporation on accessibility to showcase best practices. We were assuming it would be possible to use Storyline to produce our course, however we are running into the above mentioned issue which is a showstopper for us. Articulate makes a big show of being 508 compliant - http://www.articulate.com/support/storyline/storyline-is-508-compliant. The very first item on the list of compliance is Jaws, and for every text box it reads, it says "graphic" out loud.
I think it is pretty disingenuous to call Storyline 508 compliant with this kind of bug in it. Please provide a fix or a workaround. You're selling your vision impaired audience short.
There is a known issue with our QA team right now in regards to the word "graphic" being read out loud. Can you let us know which version of Jaws you're using and I will add this thread to the existing issue for our QA team?
Hi Ashley, if it helps you at all I just did some testing using JAWS 14.0 and I hear the word graphic being read out load on test boxes. I think version JAWS 15 is the latest version.
Thanks Nancy for sharing there here - I hadn't heard it about Jaws 14 yet, but knew it was occurring in Jaws 15 - so I'll add a comment to the existing QA report.
I just checked in on the QA report regarding this issue, and it still is with our QA team for review. It seems it may be a matter of how JAWS is reading information based on some of the information provided on this site about accessibility.
Articulate Storyline 2 Update 5 is now available for download. It includes WCAG 2.0 support, several new accessibility features, better HTML5 performance, and bug fixes. Click here for details:
8 Replies
Hi Nancy! Sorry you are having issues with this, but I do know that our QA Team has this on their radar and is working on it. I am unable to provide a timeline on that and I am not aware of a workaround though.
My company is developing a course for a major corporation on accessibility to showcase best practices. We were assuming it would be possible to use Storyline to produce our course, however we are running into the above mentioned issue which is a showstopper for us. Articulate makes a big show of being 508 compliant - http://www.articulate.com/support/storyline/storyline-is-508-compliant. The very first item on the list of compliance is Jaws, and for every text box it reads, it says "graphic" out loud.
I think it is pretty disingenuous to call Storyline 508 compliant with this kind of bug in it. Please provide a fix or a workaround. You're selling your vision impaired audience short.
Hi Dave and welcome to Heroes,
There is a known issue with our QA team right now in regards to the word "graphic" being read out loud. Can you let us know which version of Jaws you're using and I will add this thread to the existing issue for our QA team?
Hi Ashley, if it helps you at all I just did some testing using JAWS 14.0 and I hear the word graphic being read out load on test boxes. I think version JAWS 15 is the latest version.
Thanks Nancy for sharing there here - I hadn't heard it about Jaws 14 yet, but knew it was occurring in Jaws 15 - so I'll add a comment to the existing QA report.
Hello,
We are developing a course with Storyline and are running into the same issue where labels like “graphic” and “button” are being read by the reader.
Can you tell if there has been any traction on a solution to this?
Thanks!
Hi Mark,
I just checked in on the QA report regarding this issue, and it still is with our QA team for review. It seems it may be a matter of how JAWS is reading information based on some of the information provided on this site about accessibility.
Hi All!
Articulate Storyline 2 Update 5 is now available for download. It includes WCAG 2.0 support, several new accessibility features, better HTML5 performance, and bug fixes. Click here for details:
This discussion is closed. You can start a new discussion or contact Articulate Support.