Storyline 3 - HTML output problems

Nov 09, 2018

James Dougan
By James Dougan

Hi Gang,

I hope y'all are doing well, i have 3 problems that i cannot seem to get around with my HTML5 published outputs.

Note: We run the courses in Internet Explorer (company limitation), and these problems don't occur in chrome (tho i haven't fully tested in chrome yet)

#1 Duplicated edges

When i publish in HTML5 the edges of my screen recordings duplicate like this:

 

This is how the same slide appears within storylines preview screen - This is the way its supposed to appear

 

 

More Pics:

This seems to only effect screen recordings, as elements such as the character above are not duplicated.

#2 Screen Wobble

This one might be tied in with problem 1, the screen recording tends to slightly zoom and move around, its like it removes the duplicated edges from one slide then creates more duplicated edges the next slide, creating a screen wobble effect, its difficult to explain this without recording my screen. This is really distracting.

#3 Recoding the [TAB] key as an input

This is a major problem for us, our software we are recording uses the [TAB] key to move from text field to text field (pretty much like any webpage or windows program), the problem is when we record the screen and ask the user to simply press the [TAB] key, the first press of the key seems to be ignored by storyline, thus the user always has to press the [TAB] key twice.

I have done the following to no effect:

1. Checked the key storyline is waiting for, this is set to [TAB] as expect:

2. I believe i have removed all traces of accessibility settings on each element on the slide (Right click a shape > accessibility)

 

 

Any advice would be greatly appreciated

Thank You

James

 

 

 

3 Replies
Alyssa Gomez
over 5 years ago11/09/18 at 4:16 pm (UTC)

Hi there James! These are excellent questions; let's dive in!

#1 Duplicated edges and #2 Screen Wobble:

You mentioned those two issues happen when you view the published output in Internet Explorer. Is the published content hosted on a web server or a learning management system (LMS)?

#3 Recoding the [TAB] key as an input:

The TAB key is used for navigation and accessibility. The first time you press TAB, you're bringing the "focus" to the slide itself. Do you notice that you don't have to press TAB twice if you click on the slide area first?

 

James Dougan
over 5 years ago11/13/18 at 9:55 am (UTC)

Hi Alyssa thank you for your input!

#1 Duplicated edges and #2 Screen Wobble:

You mentioned those two issues happen when you view the published output in Internet Explorer. Is the published content hosted on a web server or a learning management system (LMS)?

This problem occurs within the published output directly from Storyline 3:

 

And it also occurs exactly the same from the courses that are published onto our LMS.

 

#3 Recoding the [TAB] key as an input:

The TAB key is used for navigation and accessibility. The first time you press TAB, you're bringing the "focus" to the slide itself. Do you notice that you don't have to press TAB twice if you click on the slide area first?

 

This problem also occurs in both published on storyline and LMs courses.

Correct, if i click the slide first i do not have to press [TAB] twice, but I do not allow the course to lose focus (I don’t change windows or anything), also if I record the action of pressing [TAB] to progress to the next slide then that next slide also requires [TAB] to be pressed, the first instance of pressing TAB will have the issue but the one that follows straight after works as intended (1 press) so something is going on with how storyline cooperates with Internet Explorer. 

Remember none of these issues are occuring when i use the chrome browser, 

 

 

It's also worth noting that these problems do not occur if i use the storyline preview function.

 

Edit:

I have done some further testing:

  • If the slide prior was a text input slide the TAB button works as expected (good).
  • If the slide prior was a hotspot slide the TAB key is broken and requires 2x presses (bad).
  • If the slide prior was a broken [TAB] slide and the following slide is also a [TAB] input it works as normal.

Edit 2:

After more testing it does seem to be somehow the slide is losing focus, as i have set the expected key to F2, it wont register the key until the slide has been clicked.

Any Idea how i can fix this? Expecting the user to click the slide everytime they need to press a keyboard button isn't appropriate for our use. 

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