Here's a set of simple tab interactions. Choose from a set of 3, 4, or 5 tabs, with the tabs on the left, right, top, or bottom. You can change the background by switching to a different color theme or apply your own background if you prefer. See a published example here.

47 Comments
Sarah Schillen

I have used this template for a course but have a challenge with the triggers. I have a similar problem with hotspots. Essentially, any time I have layers I am having a hard time figuring out how to automate the slide. Here it goes: I am having difficulty requiring the user visit each of the 5 tabs on my slide before automatically moving forward to the next slide. Each tab has a voice recording and I am trying to eliminate use of the “next button”. When I try to use states, by changing the layers of each tab to "visited"  when the user clicks, the last tab that would be visited gets skipped because the instant that the user clicks it, the tab is now "visited". I have been trying to figure out a way to make the media on each layer dictate the timeline and the state, but can' t figure o... Expand

Sarah Schillen
Jeanette Brooks
Luke Stollings
Luke Stollings
Luke Stollings

Just thought I'd post that I've incorporated this into a training I'm developing, but as the current interaction stands, it's not 508 compliant/accessible for keyboard navigation.  You can press the tab key sequentially to select any of the 3 bars (I'll use bars instead of tabs to describe these objects), but pressing the space bar does not select them.  If you take away the added object (the little indicator triangle), then space bar selection works.  Removing the little triangle takes away a little of the "sparkle" but none of  the functionality, so it's OK. Going a step further in accessible development, however, from simple keyboard navigation for a sighted user to keyboard navigation for the user of a screen reader, further modification is preferable.  I ended up getting all "old-sc... Expand

Jeanette Brooks

Hi Luke and thanks so much for taking the time to post! I totally hear you on the accessibility points, and you're correct, this particular interaction was not specifically designed to meet 508 compliance requirements. While Storyline does provide many features to optimize the accessibility of course content (www.articulate.com/.../storyline-section-508.php) it's up to individual course developers to decide which accessibility features they want to incorporate into their courses. That said, I agree that it would be GREAT to have more control over tab order and the ability to turn off screen-reader-visibility on layers. These kind of things make excellent feature requests, and it would really help our dev team to hear from accessibility experts like yourself who value these features. I'd en... Expand

Jeanette Brooks