Change the "rollover" and "down" state of Default Quiz buttons

The most recent version of Captivate is 11.5. You are either on that version or on version 11.0 which are both under CP2019. Labeling system is very confusing, but it also means that I don't know which version you use. Both are rather different, 11.5 adding a lot of features.

The problem is with your choice of button.  There are 6 button types in 11.5 and 4 in 11.0. Three of those are old type of buttons and the less flexible is the image button. On Quiz slides you can only use the old type of buttons, I am aware of that. To create an image button you need a graphics application. You need to create 3 images with the same name, one for each of the 3 InBuilt states which are included in Object styles: Normal, Rollover, Down. The name of those graphics needs to follow the rule: ending on _up, _over and _down. Have a look at the Gallery\Buttons to see some examples:

If you point to one of those files in the Object Style Manager, Captivate will automatically find the other two related files and show a Rollover and Down state.

Very long and cumbersome process, moreover you need to repeat that process for each of the Quiz buttons, because it is impossible to add a label (Submit, Skip, ...), you need 3 different graphics for each button.

Finally some good news: keep to the Transparent button, which is default in most Themes included with Captivate. You probably know that Styles are a component of the Theme. A Transparent button which is also old type, has been refurbished to replicate all the style possibilities of the newer Shape button. This includes the possibility to change the Fill to Image and to edit the Rollover and Down states in Captivate directly. Do not forget to set it as Default style for Quiz buttons, and you are able to add a label if necessary. Save the Theme as custom theme when you are ready to be able to reuse it in future projects.

More info about buttons in this blog, written for version 11.5:

http://blog.lilybiri.com/overvew-6-button-types

This type of question appears once in a while. Will try to write out a short blog, makes it easier to give more details and avoids that I have to rewrite this type of recommendations. As a trainer and former professor I can guess the origin. First there is the word 'Image button' which seems to suggest that you need that type if you want an image as button. Secondly: it is not always very clear that old workflows can be replaced by newer more efficient ones from all the information launched around each new release. Often more is published about brand new features, and finding good practice, improved workflows not always floats to the surface.

Sorry for that last comment.