Previous Accessibility Issues Still Causing Problems
I am working in Captivate 2019 (Version 11.8). I am still experiencing the accessibility issues previously discussed.
I know these issues were supposed to be fixed in 11.5 but that doesn’t seem to be the case. I have also tried the workarounds/solutions suggested on the page linked above but have not had any luck.
All content except buttons read as graphics (tested with both JAWS and NVDA). Screen reader users are told that each element on the page is a “graphic,” then they are given the content. There is no difference if it is text, a link, or actual image.
This has also caused issues with keyboard functions as the readers don’t recognize the text and only allow keyboard users to Tab to the button(s) on the screen. They skip over the rest of the content on the slide (images, text captions/links) and even when clicking those items with a mouse and the reader on in HTML5 preview, it reads it as as graphic and/or repeats the name of the project and then stops.
As mentioned, I have tried the previously suggested solutions/workarounds, no luck. I have also tried using the Accessibility function on the whole slide (entering all of the text I want read) as well as removing the auto labeling on individual objects on the slide and adding labels/descriptions. Nothing makes a difference, it all continues to read as graphics and ignore the actual text, images, and accessibility labels I’ve added.
My organization must be able to put out an accessible product. This all worked in Captivate 2017, and we just recently “upgraded” (doesn’t seem like an upgrade right now ) and now nothing is working like it should. Any thoughts/suggestions/fixes I’m unaware of??
The post Previous Accessibility Issues Still Causing Problems appeared first on eLearning.