Randomised Answers also Randomise Tabbing in 360
Apr 10, 2018
In Articulate Storyline 2 you use to be able to randomise answers on question slides and the tabbing would still move through the presented answers in the order they appeared. In 360 it seems that this functionality has been removed. If the answers are not randomised then tabbing is fine but if you randomise the answers the tabbing is all over the place. Can we put the functionality that 2 did so well back into 360? Without it we will need to stop all randomisation so we can meet accessibility requirements (which is not optional in our organisation).
32 Replies
Hi William,
That certainly is odd and not what we would expect you to see.
Do you have a sample .story file that we could take a look at? Is this only happening on updated courses or courses that are created new within 360 as well?
Thanks so much for your help :)
I have tried this in a converted file as well as in a newly created file in Articulate 360. The results for me are the same. My converted story file is a little large to send but I can send a portion of it showing the issue. Conversely can you create a question slide yourself and test the results. It would be interesting to see if the same thing happens for you.
Hi William,
If you're able to share a sample or a striped down version of your final product that'll help with our testing! We can confirm then that we're using the same settings and have designed the on slide elements the same way.
If you're unable to share here in ELH, we'd happily accept a .story project shared here privately if that works better! Also, can you take a Peek of the problem? The more information the better for tracking this down.
Ok, I've attached a .story file where I recreated the situation. the first slide has the answers randomised and the second slide does not. The first one tabs through the answer options randomly but the second tabs in order of appearance (as it should). This same setup in Storyline 2 would have tabbed in order regardless of the randomisation.
Also, here is a peek at one of the questions in my course showing the differnece in tabbing between random and non-random answers.
https://360.articulate.com/review/content/51bd3f4c-7386-487f-a43b-04c8e5f30602/review
William, thanks for sharing the sample and the screencast. Super helpful!
I'm going to get this documented for our team to investigate. I'll be sure to update this discussion with any new information I get!
Hey William. Just a heads up also that this behavior is happening specifically in the HTML5 output. To continue to shuffle answers and have a standard tabbing experience, you could publish Flash first if that works for you and your learners.
Thanks!
Following...
We would also like to randomize with tabbing, but have to publish in HTML5. :-/
Crystal, if that works then fine we can publish in Flash but part of our reason for moving to 360 was to move away from Flash to HTML 5. Can I get an indication that Articulate are looking at fixing this for HTML 5?
Ok, I republished this course to Review and changed the settings to Flash/HTML 5. The random/tabbing issue still persists. Is there a way I should be testing this?
Hi there, William. I completely understand, and we'll work to monitor and prioritize this issue for our development team. Here's some specifics on how we tackle bugs.
Can you let me know what browser you're using and whether Flash Player is enabled? This site is really great at quickly gathering those details: http://supportally.com/
Here's my Flash-only output. The answer choices are shuffled (as indicated by the numbers at the end of each one), but my tabbing cycles through the choices top to bottom. This is what you'll hopefully see:
Browser and flash details:
Operating System
Windows 7 / Server 2008 R2 64-bit
Browser
IE 11.0
IP Address
202.86.33.38, 175.45.116.64
Flash Version
28.0.0
Cookies Enabled
Yes
Screen Size
2560 x 1600
Browser Size
1197 x 705
JavaScript Enabled
Yes
User Agent
Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E; rv:11.0) like Gecko
Thanks, William. That browser information is really helpful.
When you test this link in IE11 and tab through the answer choices, does the tabbing cycle through top to bottom?
I tested your link in IE11 and yes, it does tab in order from top to bottom.
The contents of this email message and any attachments are intended only for the addressee and may be confidential, private or the subject of copyright. If you have received this email in error please notify Brisbane City Council, by replying to the sender or calling +61 7 3403 8888, and delete all copies of the e-mail and any attachments.
Thanks, William. What you just tested was the Flash Only output. This bug affects the HTML5 output only, so I would recommend using Flash if you can until we find a fix.
That's fine but there will come a point when we cannot use Flash output. Do we have any idea around if this will get fixed for HTML5 anytime soon?
Hi William,
I completely understand that. While I don't have an ETA to share just yet, I'll certainly bring this one up with my team again. As soon as I get news of a fix, I'll let you know!
After 4 months is there any progress on this issue?
Hi William,
No update yet, but I promise we'll post here as soon as we have any info to share. You can also view the latest version history and list of fixes when they're updated here for Storyline 360.
Thanks for your patience.
After a year has there been any progress on this issue?
Hi there, William. Thanks for checking in!
I know you want to deliver an accessible course, and this bug is getting in the way. Although I don't have any news to share yet, this issue is on our radar.
Appreciate you bearing with us and the second there's more information to share, you'll be the first to know!
Thanks for getting back to me. I presume that you know that Adobe Flash will no longer be supported as of the end of 2020 which means that organisations like ours need to start very soon on converting our Flash courses to HTML 5. The problem with doing that for us at this stage are issue like the one here where HTML 5 does not operate correctly and forces us to either flatten our interactivity (by removing things like the randomisation of answer options) or remain with Flash with the potential that we will run out of time to convert our content. Surely you have more detailed plans and time frames around these issues than just 'having it on your radar'. Is there someone we can talk to in order to escalate this issue and get more details?
Hi William,
Thanks for sharing your thoughts. Yes, we are aware and posted about it here.
We are working hard internally on both accessibility and the Flash phase out, so this issue falls right within our top priorities.
Do you have a timeframe for this transition?
Prior to 2020, William :)
I do not have a definite time to share at this time, but we will keep the community up to date as we have information to share.
In addition, this conversation is tied to the specific issue you're running into as well and you should be subscribed to any updates that we have to share here.
Ok, it is still 2019 but not much of the year left so I am wondering if this fix will be implemented prior to 2020 as indicated by Leslie above?
This discussion is closed. You can start a new discussion or contact Articulate Support.