I’m working in Captivate 2019 (Model 11.8). I’m nonetheless experiencing the accessibility points beforehand mentioned.
I do know these points had been purported to be fastened in 11.5 however that doesn’t appear to be the case. I’ve additionally tried the workarounds/options urged on the web page linked above however haven’t had any luck.
All content material besides buttons learn as graphics (examined with each JAWS and NVDA). Display screen reader customers are informed that every aspect on the web page is a “graphic,” then they’re given the content material. There is no such thing as a distinction whether it is textual content, a hyperlink, or precise picture.
This has additionally triggered points with keyboard features because the readers don’t acknowledge the textual content and solely permit keyboard customers to Tab to the button(s) on the display screen. They skip over the remainder of the content material on the slide (photos, textual content captions/hyperlinks) and even when clicking these objects with a mouse and the reader on in HTML5 preview, it reads it as as graphic and/or repeats the identify of the mission after which stops.
As talked about, I’ve tried the beforehand urged options/workarounds, no luck. I’ve additionally tried utilizing the Accessibility operate on the entire slide (coming into the entire textual content I would like learn) in addition to eradicating the auto labeling on particular person objects on the slide and including labels/descriptions. Nothing makes a distinction, all of it continues to learn as graphics and ignore the precise textual content, photos, and accessibility labels I’ve added.
My group should have the ability to put out an accessible product. This all labored in Captivate 2017, and we only in the near past “upgraded” (doesn’t look like an improve proper now 
) and now nothing is working prefer it ought to. Any ideas/options/fixes I’m unaware of??