Hello, I am currently using Storyline 2, Update 12: 1705.520 and am running into issues with markers not responding to tabbing navigation. Other buttons are working fine.
Thanks for the sample file and screen recording! I was not able to use tab to open the marker...it didn't even make it to the player buttons (just kept highlighting the URL and site info icon). I have the same version of Chrome (Version 62.0.3202.94 (Official Build) (64-bit)).
I created a test file (attached) as well, and I was able to tab to open a marker using Storyline's preview function. I then copied and pasted one of my markers from an existing project and I couldn't tab to open it, even though the other marker still worked. To test it further, I uploaded it to tempshare http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/sto_1c051c5fl1l5b8ph11gl6jqmrd9/story_html5.html?lms=1 , but I couldn't get it to work in Chrome or explorer.
I am running into a similar problem. I can tab to the markers, open them, and tab through the content; however, when I hit enter or the space bar to access the content, the state doesn't change. The state does change when I click on the marker with mouse. The problem is my navigation is tied to all the marker's being in the visited state. Not sure why this works fine with the mouse click, but not using the keyboard commands. Is there any way to resolve this without adding additional variables and triggers? Any suggestions are appreciated.
Thanks for that link--now I see what's happening! The end of the URL you shared has story_html5.html, meaning you're viewing the HTML5 output. Keyboard navigation, as well as other Section 508 accessibility guidelines, are supported in Flash output for Storyline 2.
To view the Flash output, you'll want to view the story.html file in a Flash-enabled browser.
Give that a try, and let me know if you see a difference!
Hi there Laurie, would you mind sharing a sample slide with me? It sounds like you've got some triggers associated with your markers, and I'd like to get a better idea of your set up. Also, what version of Storyline did you use to build the project?
I built the project in Storyline 2, but now am working Storyline 360. I will attach a sample slide. The issue I am experiencing is related to the markers changing state after being viewed. The state changes correctly to "Visited" when I click on them with a mouse; however, if I tab to them and then hit Enter or the Space bar, the state remains normal even though I have viewed the content contained in the marker. The next button is triggered to normal once all the markers are in the visited state. I hope that makes sense. Thanks for your quick response.
Just to add to that, I experienced while testing it locally, and in a different file (on a text box state change) in published output on Chrome Version 62.0.3202.94 (Official Build) (64-bit). It seems that in some situations the enter key will not trigger the state change on some objects like a mouse click will.
Thanks for the sample file, Laurie. I'm seeing the same thing--using keyboard navigation to open a marker does not change the marker's state to visited.
I'd like to share this with my team to find out whether or not this is a bug. Once our support engineers do a bit more testing on your file, they'll contact you via email with what they found. I'll also follow along with your case and share updates here!
I was able to view the proper file in a Flash-enabled browser, but the tab navigation was still not working for the marker I created (I can use tab to highlight it only - similar to Laurie's issue below. I cannot reveal the marker's text contents with the Enter key or Space bar...but a mouse hover/click will reveal it).
I will continue to troubleshoot...perhaps the way I customize the markers affects how it responds to tabbing?
We'd love to test your file as well - so if you can share here or send along to our Support team that'll help! It does appear that Laurie's issue was reported to our team as a possible bug - so the more examples the better!
I seem to be having the same issue. I can use the mouse to hover/click/reveal content, but when I try to do the same process with the keyboard (tab/hit enter), the content is not revealed.
I've attached my SL file (with the one screen) here.
Any ideas or work-arounds I might try to get this past a Section 508 audit?
Thanks so much for sharing your file with me! I am seeing some buggy behavior where tabbing to a marker will not open a layer in the HTML5 output, but the Flash output works normally.
I don't have any workarounds to offer at this time, but if that changes, I'll let you know. Thanks again for bringing this up to us, and I'm sorry if it's slowing you down!
I'm having the same issue as Laurie and haven't found another thread about this: "I can tab to the markers, open them, and tab through the content; however, when I hit enter or the space bar to access the content, the state doesn't change. The state does change when I click on the marker with mouse. The problem is my navigation is tied to all the marker's being in the visited state." Has this been resolved? Is there another way to get the state to change? Thanks!
Hi there, Ellen. So sorry you've hit this roadblock.
Our team is still investigating the issue where markers do not change to visited state when using keyboard navigation keys. As soon as we have a fix in place, we'll let you know!
While we haven't found a workaround yet, we're happy to have a thorough look at your file to see what tailored approaches we can offer. If you're able to share the .story file, please use this private upload link!
I wanted to share that we aren't seeing this issue in Storyline 360 (Build 3.49.24347.0), where markers aren't changing states using keyboard navigation. If you're still running into this snag, make sure you're using the latest version of Storyline 360.
If you have additional questions, don't hesitate to reach out to us in this discussion or in a support case.
19 Replies
Hi Michelle,
This is a known issue in Storyline 2 documented here. It'll be fixed in a forthcoming update for Articulate Storyline 2. Enable the Check for updates at startup feature to be notified when new updates are available.
Thank you, Ashley!
Hello, I am currently using Storyline 2, Update 12: 1705.520 and am running into issues with markers not responding to tabbing navigation. Other buttons are working fine.
I appreciate any tips anyone may have. Thanks!
Hi Dafne! I put together a quick sample file for you using Storyline 2. Are you able to tab to and open the marker on this slide?
Here's a screen recording of my test in Chrome.
Hi Alyssa,
Thanks for the sample file and screen recording! I was not able to use tab to open the marker...it didn't even make it to the player buttons (just kept highlighting the URL and site info icon). I have the same version of Chrome (Version 62.0.3202.94 (Official Build) (64-bit)).
I created a test file (attached) as well, and I was able to tab to open a marker using Storyline's preview function. I then copied and pasted one of my markers from an existing project and I couldn't tab to open it, even though the other marker still worked. To test it further, I uploaded it to tempshare http://s3.amazonaws.com/tempshare-stage.storyline.articulate.com/sto_1c051c5fl1l5b8ph11gl6jqmrd9/story_html5.html?lms=1 , but I couldn't get it to work in Chrome or explorer.
I am using Windows 7 Professional, if that helps.
Thanks again!
I am running into a similar problem. I can tab to the markers, open them, and tab through the content; however, when I hit enter or the space bar to access the content, the state doesn't change. The state does change when I click on the marker with mouse. The problem is my navigation is tied to all the marker's being in the visited state. Not sure why this works fine with the mouse click, but not using the keyboard commands. Is there any way to resolve this without adding additional variables and triggers? Any suggestions are appreciated.
Hi Dafne,
Thanks for that link--now I see what's happening! The end of the URL you shared has story_html5.html, meaning you're viewing the HTML5 output. Keyboard navigation, as well as other Section 508 accessibility guidelines, are supported in Flash output for Storyline 2.
To view the Flash output, you'll want to view the story.html file in a Flash-enabled browser.
Give that a try, and let me know if you see a difference!
Hi there Laurie, would you mind sharing a sample slide with me? It sounds like you've got some triggers associated with your markers, and I'd like to get a better idea of your set up. Also, what version of Storyline did you use to build the project?
I built the project in Storyline 2, but now am working Storyline 360. I will attach a sample slide. The issue I am experiencing is related to the markers changing state after being viewed. The state changes correctly to "Visited" when I click on them with a mouse; however, if I tab to them and then hit Enter or the Space bar, the state remains normal even though I have viewed the content contained in the marker. The next button is triggered to normal once all the markers are in the visited state. I hope that makes sense. Thanks for your quick response.
Just to add to that, I experienced while testing it locally, and in a different file (on a text box state change) in published output on Chrome Version 62.0.3202.94 (Official Build) (64-bit). It seems that in some situations the enter key will not trigger the state change on some objects like a mouse click will.
Thanks for the sample file, Laurie. I'm seeing the same thing--using keyboard navigation to open a marker does not change the marker's state to visited.
I'd like to share this with my team to find out whether or not this is a bug. Once our support engineers do a bit more testing on your file, they'll contact you via email with what they found. I'll also follow along with your case and share updates here!
Hi Alyssa,
I was able to view the proper file in a Flash-enabled browser, but the tab navigation was still not working for the marker I created (I can use tab to highlight it only - similar to Laurie's issue below. I cannot reveal the marker's text contents with the Enter key or Space bar...but a mouse hover/click will reveal it).
I will continue to troubleshoot...perhaps the way I customize the markers affects how it responds to tabbing?
If i have a moment, I'll also submit a ticket.
Thanks for your assistance!
Hi Dafne,
We'd love to test your file as well - so if you can share here or send along to our Support team that'll help! It does appear that Laurie's issue was reported to our team as a possible bug - so the more examples the better!
This post was removed by the author
Hi Ashley,
I seem to be having the same issue. I can use the mouse to hover/click/reveal content, but when I try to do the same process with the keyboard (tab/hit enter), the content is not revealed.
I've attached my SL file (with the one screen) here.
Any ideas or work-arounds I might try to get this past a Section 508 audit?
Thanks so much!
Birgit
Hi Birgit,
Thanks so much for sharing your file with me! I am seeing some buggy behavior where tabbing to a marker will not open a layer in the HTML5 output, but the Flash output works normally.
I don't have any workarounds to offer at this time, but if that changes, I'll let you know. Thanks again for bringing this up to us, and I'm sorry if it's slowing you down!
Sounds good -- thanks for looking in to this!
Best,
Birgit
I'm having the same issue as Laurie and haven't found another thread about this: "I can tab to the markers, open them, and tab through the content; however, when I hit enter or the space bar to access the content, the state doesn't change. The state does change when I click on the marker with mouse. The problem is my navigation is tied to all the marker's being in the visited state." Has this been resolved? Is there another way to get the state to change? Thanks!
Hi there, Ellen. So sorry you've hit this roadblock.
Our team is still investigating the issue where markers do not change to visited state when using keyboard navigation keys. As soon as we have a fix in place, we'll let you know!
While we haven't found a workaround yet, we're happy to have a thorough look at your file to see what tailored approaches we can offer. If you're able to share the .story file, please use this private upload link!
Hi all!
I wanted to share that we aren't seeing this issue in Storyline 360 (Build 3.49.24347.0), where markers aren't changing states using keyboard navigation. If you're still running into this snag, make sure you're using the latest version of Storyline 360.
If you have additional questions, don't hesitate to reach out to us in this discussion or in a support case.