I can't seem to be able to tab through the content of my HTML5 output projects of Storyline 2 update 10. Can this be fixed by myself or will there be an upcoming update to fix this?
Where are you hosting and testing your HTML5 content? Are you viewing it in an LMS or web server? You'll also want to confirm you're using one of the supported browsers detailed here.
If you're using one of those browsers and still having a hard time, are you able to share a copy of your .story file and give us a bit more information about what is happening when you try to use the tab key and where you're testing it so that we can try to replicate?
I'm doing an HTML5 web output only. Testing locally in Google Chrome. The file I shared is not my project but I still can't tab/select the shapes or button to get to the other slides without using the mouse.
Testing locally may be a part of the issue as we do recommend uploading and testing in the intended publish environment. You could use one of the options here and I'll take a look at your course in the meantime as well.
Sorry - I wasn't reading your initial post clearly (post vacation brain still...) but you said only in the HTML5. Our output and accessibility set up is currently only supported in Flash - so that is why you're unable to tab to those elements.
I certainly understand David, and although browsers like Chrome and Firefox are going to default to HTML5 output, you can still use Flash in both of them, it's a setting accessible within individual browser controls. I know the topic of a full shift to HTML5 has been going on for some time in the forums, and I know it's something our team continues to investigate and keep an eye on - but I don't have any other information to share at this time. We do have the white paper here in terms of mobile deployment which tends to err towards HTML5 - so you may want to review that as well.
6 Replies
Hi David,
Where are you hosting and testing your HTML5 content? Are you viewing it in an LMS or web server? You'll also want to confirm you're using one of the supported browsers detailed here.
If you're using one of those browsers and still having a hard time, are you able to share a copy of your .story file and give us a bit more information about what is happening when you try to use the tab key and where you're testing it so that we can try to replicate?
Hi Ashley,
Thanks for the quick feedback.
I'm doing an HTML5 web output only. Testing locally in Google Chrome. The file I shared is not my project but I still can't tab/select the shapes or button to get to the other slides without using the mouse.
Hi David,
Testing locally may be a part of the issue as we do recommend uploading and testing in the intended publish environment. You could use one of the options here and I'll take a look at your course in the meantime as well.
Hi David,
Sorry - I wasn't reading your initial post clearly (post vacation brain still...) but you said only in the HTML5. Our output and accessibility set up is currently only supported in Flash - so that is why you're unable to tab to those elements.
Thank you Ashley,
I will have to wait for the next updates, hoping the accessibility set up will work one day on HTML5.
Most used browser like Mozilla and Chrome are backing away from Flash in 2017.
I certainly understand David, and although browsers like Chrome and Firefox are going to default to HTML5 output, you can still use Flash in both of them, it's a setting accessible within individual browser controls. I know the topic of a full shift to HTML5 has been going on for some time in the forums, and I know it's something our team continues to investigate and keep an eye on - but I don't have any other information to share at this time. We do have the white paper here in terms of mobile deployment which tends to err towards HTML5 - so you may want to review that as well.
This discussion is closed. You can start a new discussion or contact Articulate Support.