Forum Discussion
TAB order not working
My latest course is behaving funny. I have text boxes on the screen however no matter what I do, I cannot get the tab to go the boxes. I have ensured that the Accessible check box is selected but yet using the tab key only goes to the buttons on the page. I have tried deleting the text boxes and retyping and still the same thing. Never had an issue with this in the past.
I am having the same issue. Got really excited because the hotspot seems to finally be accessible, but now my text boxes are not. I can only tab to buttons.
Hello Mark and Nicole!
With the latest update to Storyline 360, which is Build 3.36.21213.0, we've made some enhancements to accessibility.
You specifically mentioned Tab Order, so I wanted to share this documentation which explains it fully.
In short:
- Text and images are read immediately by screen readers so learners don’t have to press any keys to hear the slide content. These objects are read in the tab order you defined in Storyline.
- Use your screen reader's navigation keys (e.g., Down and Up arrow keys) to move through the objects on the slide.
Hi
I can't seem to get this to work using the built in Microsoft narrator?
Confidential communication
Westpac Banking Corporation (ABN 33 007 457 141, AFSL 233714)
Westpac Institutional Bank is a division of Westpac Banking CorporationHi I have the same problem but with SL3. The text box is in the tab order list but I am not able to get to it. So Jaws will not read it. i have the latest updat of SL3.
Hi Mark!
Storyline 360 courses work with JAWS 16 and later, NVDA, VoiceOver, and TalkBack in our supported browsers.
Right now, Narrator is not supported.
Hi Lauren,
I am facing a similar issue where text box tab ordering is not working similar to Mark's problem. I am using the latest updates of the Storyline and am using NVDA as screen reader. Is there anything which is updated in Storyline which is causing this issue? Because I have few older published courses of January this year which work absolutely fine whereas if republish with the updated Storyline the same problem occurs.Hello Irfan!
I'm happy to lend a hand! In Storyline 360 Update 37 (Build 3.37.21453.0) released in February changed the tab order behavior. What you've found in previous versions is that you had to tab to every object on a screen. Now you will only need to tab to interactive objects such as data entry fields, graphics, videos, buttons, etc.
If this sounds different from what you're noticing, please let me know!
Hello Lauren,
Thanks for the update, in earlier versions we had the freedom of adjusting the tab order as well as alt-text for non interactive elements thereby giving us multiple solutions to provide for accessibility. I have few queries as follows:- In the current update, do the non-interactive elements readout themselves?
- Does changing the tab-order will have any effect on reading order?
- Earlier we could use ChromeVox to test the accessibility, now it seems it doesn't read the textboxes.
Thanks again for replying.
Hi Irfan!
Great questions! I'll answer each question individually as you've asked them.
In Storyline 360, Update 38 (Build 3.38.21779.0) non-interactive elements will read out when you move through the slide using the keyboard.
Changing the Tab Order does affect the reading order as a user will move through the slide following the tab order.
Lastly, ChromeVox isn't currently supported so I'm not familiar with its behavior. Storyline 360 courses work with JAWS 16 and later, NVDA, VoiceOver, and TalkBack in our supported browsers.
Let me know if there is anything else that I can clarify!
Hi Lauren,
I'm coming to this thread late, but was just upgraded to 360. I understand the screen reader being able to read text elements without the need for tabbing. Here's a question regarding tab order and a text/shape element.
Recently, a non-sighted user asked me if there was a way he could skip a slide without having to tab through every element on screen. Granted this was the SL3 version, but I was curious and was wondering if I created a button using a shape and added the words "Skip Slide" in it, if that would work. So, with my SL360 version, I added a transparent button that has the words "Skip Slide" and placed it at the top of the tab order. Unfortunately, even though I placed it at the top of the tab order, I still have to tab through all of the other elements on the slide before I get to the transparent "Skip Slide" button I created.
In the older SL version, this same user could not click any of the menu items to move past slides he'd already worked through. I'm wondering if the SL360 menu will allow him to navigate through to any slide?
The courses I create are placed in an LMS created by Oracle if that makes a difference.
Any help/suggestions would be great.
Hi Cathy,
With the accessible player in Storyline 360, the tab key now only focuses on interactive objects in the slide, presents the Skip Navigation shortcut, and then immediately jumps to the Next slide button on the player, drastically reducing the number of keystrokes needed to move to the next slide.
It may be that you no longer need a "Skip Slide" button, and it's worth testing a sample project to get a feel for the accessible player. This comparison below provides some more detail on the differences before and after the player was implemented.
I recommend taking a look at this article, as well as the resources Lauren shared above. Let us know if you have any further questions!
Thankful to stumble upon this thread. I have a related concern in that scrollboxes are also not appearing in tab order. if this issue is mobility related and someone is utilizing tab/return to go through the course but is not using a screen reader, how do they complete the text in a scroll box if it never highlights?
Hi Ren,
I have embedded a web-object, in a Storyline file. The WebObject contains a image, buttons and text. This file was working well while published in Storyline 3 and in earlier version of 360. I could read all text image elements using JAWS reader. Now with the latest updates of SL 360, the published version is not able to read the web-object elements, and not I am not able to click on buttons in the web-object using space or enter key.
Please let us know if there is any special care needs to be taken while integrating the WEB-Object in latest updated version.
