Forum Discussion
Change colors and/or hover for the Next and Previous buttons on Player
I need a better color contract for the next and previous buttons on the Storyline player - the buttons are not an accessible color contrast - is it possible to adjust the color so there is better co...
It's not ideal but a workaround is to change the css output.min.css file. Naturally every time you publish you have to re-apply, you will overwrite your css changes. I make it a part of my release process. Not that big of deal my changes are light.
For example, let's say you want to change the next and previous hover color to neon green and really make it pop. You can try it by publishing your course to web, now inspect the page, on pc hit F12 for developer tools. Inspect element. Now select your next button, that will highlight your element, on the styles pane you will note the which one it is. In my circumstance it was output.min.css:693. What that means is it's the output.min.css file and its line 693. In my case the css was:
body:not(.is-touchable-tablet) .cs-pxabnsnfns10111100101 .cs-button:hover .text {
color: #BABBBA;
}
I changed to:
body:not(.is-touchable-tablet) .cs-pxabnsnfns10111100101 .cs-button:hover .text {
color: #09f332;
}
Hit save and reload. Now hover over next and prev. See that its neon green. You shouldn't need to clear your cache but maaaybe.
Repeat process for discovering your desired elements and change the attributes accordingly.
Andy
Hi Andy. Thanks for your response. Sorry for not being a CSS guy, but are you saying you are doing this in the published html page in the browser which will work even if the SCORM is added to an LMS?
Or is this using the browser to find out what needs changing and where and then diving into the published folder before you zip the contents to make the SCORM zip file?
Thanks, SteveLong answer:
I used the publish for web just to identify the elements of the changes I need to make.
But then you when you publish for say SCORM 1.2 it generates all the files as it does for publishing for the Web browser. You then make that change in your published SCORM output. You zip that up as normal and load that into any LMS. The changes will carry over at the course level irrespective of LMS. What I like about publishing to the web and viewing in my local browser is I can iterate through changes quickly. But when I do it for real yeah you put it in your SCORM package. Remember though you have to reapply every time you publish, so I save this to the end of my workflow. I test in the design phase to make sure it all works and looks good. Then I don't worry about it until the end.
Short answer: Yes it works when packaged for SCORM. See long answer for details.
Thanks Andy. I suspected it was the latter, but thought I better check. It made the most sense 😄
Cheers, for that and food for thought for any move to the modern browser which feels less modern because of this workaround. 😜
