October 3, 2017
Shared Actions for Easy Navigation Controls
Comments
(3)
October 3, 2017
Shared Actions for Easy Navigation Controls
I've been an eLearning designer and developer since 2005. In 2015 I started my own eLearning design company. I began creating Adobe Captivate video tutorials to help promote my business through my YouTube channel at https://youtube.com/captivateteacher. My intention with my YouTube videos was to attract attention from organizations looking for a skilled Captivate developer. This strategy proved successful as I've worked with clients worldwide, helping them build highly engaging eLearning solutions. In addition, my YouTube channel presented another benefit of attracting aspiring Captivate developers to seek me out as a teacher. I now offer online and onsite training on Adobe Captivate, teaching users the skills to build engaging and interactive learning.
Legend 639 posts
Followers: 981 people
(3)

I record Adobe Captivate tutorials on procedures I use myself. One such topic that I haven’t covered before now is shared actions. I simply haven’t had a reason to use them in my everyday work. I would use “advanced actions” for the navigation controls I would put at the beginning of my course and display for the rest of the project. One problem is that you can’t have items displayed for rest of project and contained in a non-static fluid boxes. I solve this problem using a shared action in this video tutorial.

 

 

3 Comments
2018-06-20 21:19:17
2018-06-20 21:19:17

The ‘change state of’ selection is greyed out. (4:09 of your video). How can I select this option?

Like
()
2017-11-01 19:53:48
2017-11-01 19:53:48

I use that same advanced action structure for my Play/Pause toggle button, Paul. However, I do not make the buttons display for rest of project. I found that you can no longer control the tab order of that button (or any button that you set for rest of project) past the initial slide it originates. I need a consistent tab order for accessibility. Hence, I make individual play/pause toggle buttons for my slides as well as separate advanced actions. Additionally, you can add different accessibility text to your button states. But screen readers will not read the new accessibility text unless you program javascript to refocus the keyboard cursor on the button so that screen readers can read out the changed accessibility text to users.

Like
()
(1)
>
mferguson192291
's comment
2017-11-02 02:27:41
2017-11-02 02:27:41
>
mferguson192291
's comment

I didn’t display anything in this tutorial for rest of project. In this case, each slide has its own set of controls and the shared action is repeated on each version of those controls.

Like
(1)
Add Comment