Captivate HTML5 Blank Project and Keyboard Navigation

Question

Hello All,I have found that during some publishes the default browser keyboard navigation, using tab to move between elements and space/enter to select them, is not working.The problem seems to come from the Captivate javascript file.This happens whenever you tab across elements or try to "press" one via space/enter.I would not bother, since the actual mouse click events seem to behave as normal., however it is a customer derived requirement. Have any of you experienced this problem?I am not using the current version of captivate but the one previous, 10.0.0.236. This is due to the auto-play feature being removed in the current version.

olerd81870073 · Accepted Answer

NEW FINDINGS.After much tampering and playing around it seems that if you have a shortcut key command on a button, or smart shape as a button, then hide said button for any reason on or near start up of the course it will cause a cascading error that blocks keyboard navigation.Example:We have a lock step course with custom next and back buttons. They are unlocked based on page completion and page number. On the first page we were hiding the previous button, since you cannot go back from page 1. Both back and next were using shortcuts commands, as an attempt to alleviate this issue for 508. However it seems hiding the buttons with shortcut commands causes all of the issues. After removing the shortcut command, the original 508 controls were able to be accessed again.To keep with our theme of having the custom shortcut keys, I added them back using jQuery in an attached js file.Hope this helps anyone else who runs into this issue.I will leave this open in case anyone wants to add their custom solution here.

olerd81870073 · Answer

After tracing the error code down, its seems to be this line

this.gc=this.item.getContext("2d");

That only gets an error when tabbing to an element or pressing enter/spacebar after tabbing to element.

The best I can figure is that the canvas element in question is not being loaded (or being stored in memory and not reloaded when needed) causing it to come up as missing when called on.

This happens in responsive and non-responsive html5 published courses.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.