HTML5 restrictions


I copied a few of the Storyline features that do not work in html5 but might affect my course development.

Can someone explain what specifically does not work?


I am developing a course while trying to learn Storyline. I am publishing to html5 because my requirement is to avoid anything requiring the use of Flash. I put some of my specific questions or my assumption next to each item. 




Engage interactionsDoes this mean some of the quiz slides don’t work? Which ones don’t work or which ones do work, whichever list is shorter! 


Print results – I don’t think I need this one, but where is the option for the user to do this?



Quiz timerWhere is this used?



The markers still work, they just do not pulse or swirl, right?







I should avoid adding search to the player if publishing to html5.


Keyboard shortcuts



Any examples of some that might be annoying to the user if they can’t be used?

Navigation (Free, Restricted, Locked) – What does this mean ?– all 3 options are listed.



Browser size (current,optimal,fill)  

What does this mean? I can't change this - but what is the default?


11 Replies
Adrian Dean

Howdy Ejuana,

Excellent questions! Let's go through them here real quick.

Engage interactions - These are flash-based and won't work in HTML5.

Print results - Not currently possible in HTML5 output. The user might be able to print what is in their browser window using the browser's print option, but that won't be the same as having the functionality in the project. To setup Print results in Storyline for flash output just requires setting up a trigger with that option selected, utilizing a button more than likely.

Quiz timer - Its used for quiz questions, primarily a series of them with a Result side at the end. You would setup the Quiz timer function in the Result slide's properties. However, just like Print results, this option isn't available for HTML5 output at this time.

Markers - You are correct. They still work, just no animations in HTML5 output.

Search - Isn't currently available in HTML5 output.

Keyboard shortcuts - They don't currently work in HTML5 output.

Navigation - These aren't available in HTML5 output either. Free means that the user can go to what slide they choose, just by clicking on them in the menu in whatever order. Restricted means that users can view the current slide and/or previous slides, but can't use the menu to jump ahead or skip over slides. Locked means that the slides can't be clicked on from the menu at all, thus forcing them to view them as you designed.

Browser size - not possible in HTML5 output. The default is that it will display it at the current browser's size.

For a better reference, check out these:

Comparing Storyline's Published Outputs

Customizing the Player Menu

Changing the Browser Settings and Player Size

Always Happy to Help,


Christine Hendrickson

Hi Ejuana,

  • Engage Interactions - These are interactions that are created in Articulate Engage. This will not impact the quizzes you've created within Storyline. This simply states that if you create Engage Interactions (outside of Storyline) and import them into Storyline, they will not function in HTML5 or the Articulate Mobile Player. 
  • Print Results - This option can be provided at the end of a quiz, on the results slide. However, as the chart you've seen shows, this is not supported in HTML5 or in the Articulate Mobile Player, only in Flash. Are you just wanting to know how to add this option to a course that would be viewed in Flash/on a PC?
  • Quiz Timer - This adds a timer to your quiz. If you've specified a specific time allowed for the quiz, a timer will appear. The learner will need to complete the quiz or question in the time provided and they will see a timer (if enabled) in the course. For more information on the timer, please take a look at section 4 in this tutorial
  • Markers - Yes. Markers will still function, the animations just won't display. This is only the case for HTML5, however, the animations will work properly in Flash/AMP app.
  • Search - Correct, this feature is not supported in either mobile output type.
  • Keyboard Shortcuts - Your users won't be using standard keyboards if they're using iPads, this is why this isn't supported in the Articulate Mobile Player. The limitation for HTML5 is the same for mobile. On the PC, this limitation will really only affect you if you've used action triggers based of of keyboard commands. For example, "Submit Interaction > When: User presses: Enter".
  • Navigation - I believe this means that the course will function as if it were published with the default navigation settings. If you alter these settings to restricted, locked, or free, they will not function this way in HTML5 and in the Articulate Mobile Player app. However, keep in mind that this applies to the menunot your slides.
  • Browser size - This applies to the player size options that are available in the Player Properties. For example, if you set the player to show in full screen or in a full browser window, this may not work properly. 

I hope this helps! Please let me know if you have any questions.



Ejuana Mitchell
Christine, Adrian,
Thanks for your responses!
To clarify, I am trying to create an online course that will work in HTML5 on PCs - not mobile right now. I want to make sure the course does NOT require Flash and will still work, so I don't want to use anything that will not work in HTML5. 
  • Print Results - I don't need this option, I just wanted to know how to use it.
  • Quiz Timer - I will need to use this option at some point because the client does want timing on quizzes in later courses, I will have to require them to use Flash to use that function.
  • Keyboard Shortcuts - In this case, I will avoid using triggers based on keyboard commands.
  • Navigation - I am still not clear on this one. In HTML5, what is the default navigation in the menu if I can't change the option? Is the default free? Can the user go back to an item that is grayed out? Is the default to NOT show topic numbers?



Christine Hendrickson

Good morning Ejuana. I hope you had a great weekend!

For your question on navigation:

This just means that you cannot add restrictions to the menu. The learner will be back to move anywhere in the course, using the menu, whether you've assigned any restrictions to the menu, or not. Yes, the user can go back to a menu item that is grayed out. As far as I know, it should show the numbers, I can't see why it wouldn't be displayed as this isn't really tied to the action of navigation. But, maybe I'm misunderstanding this question.

Let me know if you need any additional clarification. 


Ejuana Mitchell


Sorry - didn't  see your response until now.

About the menu, the topic numbers show when I am editing the player, but they do not show in the presentation screen or in the actual course.

That is great for my needs because the numbers would not show correctly - I altered the sequence. making the number look non-sequential.

Hopefully, that is not a bug that the topic numbers are not showing in the course.



Jared K

I would urge Articulate to work on its HTML output offerings. I've used many flavors of CBT over the past decade and the most robust for all use cases were custom using only HTML, CSS, and Javascript. I've been able to use complex animations, interactions, branching, media, responsive layouts with media queries, etc., that would work on almost any browser going back to IE7.

Coming from a previously certified Flash dev, I'm very reluctant to recommend an authoring tool that has a Flash-first strategy at this time. The output actually breaks in some cases (mobile android leads me to a black abyss, I can't even tell what action its trying to do) which I can't allow to happen for my projects.

For these reasons I'm uncomfortable recommending using Storyline for my company's current projects.

Leslie McKerchie

Hi Jared!

This thread is dated and we have an updated list so that you can compare the Flash, HTML5, and Articulate Mobile Player output here.

Articulate Storyline makes it easy to deploy your content to learners with mobile devices. See answers to common questions about publishing mobile content here.