New smart shape 508 issue

Report · Mar 28, 2017

Running Captivate 9 on Windows 10.This has only begun occurring in past month. We're developing using smart shapes as text elements or design elements. We've customized the accessibility name and descriptions to either appear blank or reflect the text only. However, on publication as a SCORE 2004 v 4 file in Blackboard Learn, testing is identifying any smart shape as a button and installing a default text description of "Button: Trigger this button to go to the next slide"

This button designation and description is not showing up in the cptx file, nor are there any publishing settings, object style manager, or preference settings that are causing the issue as far as we can tell. Is there something that needs to be reset?

Report · Mar 28, 2017

Interesting, cannot check because I don't have access to Blackboard anymore. I wonder if this is linked with the fact that each shape style has by default 3 InBuilt states because it always can be used as a button. There is still no way to define a style separately for a shape and for a shape button. Even all Smart Shape styles for Quizzing objects (feedback message to give one example) have those InBuilt states. I always found that very weird, was less confusing in CP8.

Report · Mar 28, 2017

Worth a look, not sure if the three states are being deployed even if " use

as a button" is not selected, but worth investigating as a possible cause.

Thanks, Lieve!

Report · Apr 03, 2017

Interestingly enough, the auto-fill setting for accessibility text is "Button: Trigger this button to go to the next slide" for smart shapes, even though the default shape only has one state and has not been activated to use as a button. So - what I'm seeing is indeed an artifact from the default shape that is getting tagged on to the end of the new name and/or description we've entered in the accessibility dialogue boxes.

After further editing and republishing, we noticed that republication as an html 5 only project removed all the artifacts that were still present when published as a swf only or swf/html project. I can't say for certain that this is the solution, because we had tried several other things with the problem project files prior to this. May just be a publication glitch we will never see again.

Report · May 16, 2017

I have noticed with published course files in SWF format, there is a lot more functionality with JAWS/NVDA shortcut keys. In SWF, I can use JAWS Insert + F5 or the B button shortcut key to access any form field buttons in Captivate. And JAWS when reading buttons adds a "button" announcement on the end of any accessibility label you type into your captivate buttons. So "Play button" in the accessibility box would be read by JAWS as "Play button button". So I think that is the issue you are seeing. JAWS seems to be detecting more things in Flash content or Flash-based HTM content. Whereas in HTML5 format, you cannot use any of JAWS built-in shortcut keys. This is both a blessing and a curse for us. Because we can then use smartshape buttons as Text Boxes to allow better navigation for screen readers in courses. It will suck for JAWS users who use shortcut keys a lot and will have to manually tab every single time in order to navigate, but if you make your tab order consistent throughout courses and try to limit/pace yourself with the amount of objects on screen then it should be tolerable. Many JAWS users tend to turn narration audio off because, think about it, they are used to the JAWS voice going at astronomical speeds and a normal narrator would be too slow for them. So having your narration transcript built into the smartshape textboxes and other objects would be a great way to make your Captivate courses more independent. You would not need a descriptive transcript for the course, though it would always be handy to make one available.