August 14, 2019
Keyboard access not working in CP17
Comments
(7)
August 14, 2019
Keyboard access not working in CP17
Instructional Designer / Trainer
Newbie 2 posts
Followers: 0 people
(7)

I have smartshapes defined as buttons to emulate stylized check boxes. The smartshapes have normal and visited states only, with the visited state displaying a check mark. Each button calls the same shared action to toggle the display and set a variable. All show up as interactive controls in the tab order, yet the spacebar does nothing when I tab and attempt to activate the control. I ended up having to create unique shortcuts for each control and override the auto-accessibility to explicitly describe the shortcut, which is something I did not want to do. I also tried adding hover and down states to the buttons but that had no effect.

This issue reported for CP7, so I am creating a new thread as it is happening in CP17 as well. The CP7 issue was described here: https://forums.adobe.com/thread/1637398.  In that case, the issue related to using transparent buttons.  In my case, I am using smartshapes as buttons.

7 Comments
2019-08-20 09:26:52
2019-08-20 09:26:52

Are you talking about version 10, also indicated as CP2017? In that case, can you please check the full version number under Help, About Captivate? The most recent one, only authorized version, is 10.0.1.299. If you are still on an older version, please update.

Like
(1)
(6)
>
Lieve Weymeis
's comment
2019-08-20 17:20:53
2019-08-20 17:20:53
>
Lieve Weymeis
's comment

Hello Lieve,

I am running 10.0.1.299.  I discovered this morning that this issue is a bug (https://forums.adobe.com/thread/2506428). It occurs when a custom shortcut is applied to a smart shape and the smart shape is then hidden/shown.  Doing so causes all subsequent smart shape buttons to not recognize the space bar as a keyboard shortcut.  You can tab to them but cannot activate them.  As far as I have read, this has been a bug for quite some time. In my case, all I had to do was remove the custom shortcut (in this case the letter N for a Next button at the beginning of my course).  Thereafter, the space bar worked for all subsequent controls.

 

Like
(1)
>
Eric Zenor
's comment
2019-08-20 18:39:29
2019-08-20 18:39:29
>
Eric Zenor
's comment

OK, have no longer access to CP2017 myself which makes it hard to give good answers. Did you log that bug? I would really recommend to do so.

Like
(1)
>
Lieve Weymeis
's comment
2019-08-20 19:05:17
2019-08-20 19:05:17
>
Lieve Weymeis
's comment

Yes, thank you.  It is also hard for me to work in v10 knowing how many great things there are in 11.5…but customer requirements and all…

Like
(1)
>
Eric Zenor
's comment
2019-08-20 19:23:09
2019-08-20 19:23:09
>
Eric Zenor
's comment

Understand, I still have one system with 11.0 because of clients.

Please, log the but!

Like
(1)
>
Lieve Weymeis
's comment
2019-08-20 19:24:07
2019-08-20 19:24:07
>
Lieve Weymeis
's comment

Bug has been logged.

Like
(1)
>
Eric Zenor
's comment
2019-08-20 19:25:44
2019-08-20 19:25:44
>
Eric Zenor
's comment

Great and thanks!

Like
(1)
Add Comment