Storyline + accesibility issues

Oct 20, 2013

Hi there,

I'm trying to make a course compliant with accessibility standards by adding alternative keyboard strokes people can use instead of using the mouse. I am finding that forward and back arrow keys work fine on all PCs, but using CTRL + a number on the number pad (to jump to a screen) is not working on some PCs.

Does anyone know why this is an issue? The blurb for Storyline says that 'you can execute most Storyline functions using a keyboard'!

Thanks for any help.

3 Replies
Ashley Terwilliger-Pollard

Hi Sue and welcome to Heroes!

I tested it within my own Storyline file, and assigned a "Jump to slide" trigger when users presses a key CTRL+7 and it successfully moved to the next slide. Do you know if there is anything specific about these users PCs? Possibly something as simple as having the number lock turned on? 

Sue Stubley

Hi Ashley,

thanks for the reply. No I don't think there's anything specific about these PCs, and the number lock isn't on. Do you know of anything else that would inhibit the use of keyboard keys? This isn't connected to browser security / pop-up problems is it? This PC in particular has been having those types of issues.

Cheers,

Sue

Ashley Terwilliger-Pollard

Hi Sue,

I haven't heard of it being a problem with browser security, but it doesn't mean that it can't happen. I'd suggest having this user try in a different web browser if possible, as it sounds isolated to this particular user's computer, correct? If you're  able to test it and replicate the problem and determine a specific combination (i.e. not in Chrome, IE, etc.) that isn't working, please let us know and share the .story file so that we can do some further testing. 

This discussion is closed. You can start a new discussion or contact Articulate Support.