Change Text States with In-Slide Continue Buttons
Jun 22, 2022
Hello! I am trying to basically create a little click through window in my slide that uses "Continue" and "Go Back" buttons to go through 3 different paragraphs. My plan was/is to use triggers to change the state of the text to do so, with a condition on one of the triggers that it can only change to state 3 if the body text is in state 2. The relevant triggers can be seen here:
When I preview the course, it immediately jumps to the third state (Future) when I click "Continue," instead of jumping to the second state (What They Do). Yet when I click "Go Back" from the third state, it includes the second state. I feel like it is probable that I am just missing something obvious, but I cannot figure it out. I have attached a video walkthrough of the issue, but if any of this is unclear, please let me know. Thank you in advance for your help!
8 Replies
It looks like the triggers are firing in sequence. For example, trigger one, change A to B (which happens). Then the next trigger change A to C if state is = to B (which it is) so then it triggers right after.
You need a way to separate the clicks so they don't all happen at once.
Here's how to do it using a variable to count clicks.
https://360.articulate.com/review/content/4cff7fea-54cc-4f66-8dd5-24080fb1087f/review
You may want to play around with other ways to display the text if you're using a screen reader for alt text. Layers may be a more manageable option.
Thank you so much for all your help Tom! So just to clarify, screen readers will only pick up on the "Normal" text, and not text after a state change? I had considered using layers but had thought it may be clunkier, though now it seems like that may be the better option.
The states should be read as they are interactive, however, I'd test it. Sometimes, it's still just easier to pull the text out of states for editing and whatnot. The end user doesn't know if what they see is state, layer, or new slide. I'd test it and then see what is easiest for management of the content.
https://articulate.com/support/article/Storyline-360-Accessible-Slide-Content
As a side note (thought about this last night), I'd still use the variable, however, if you change the trigger order, the button would work as designed.
https://360.articulate.com/review/content/a64649dc-5bef-43b2-a21b-0fcbb0db2204/review
Thank you Tom!