Hyperlinks are not showing up in the Tab Order dialogue, and I cannot tab to them when running a published course.
Are hyperlinks not officially supported as accessible content? The official documentation states that only Drag and Drops and Hotspot interactions are not keyboard-accessible (https://en-uk.articulate.com/products/storyline-section-508.php). But I'm at a loss to figure out how to navigate accessible content to get to a hyperlink and trigger its action (Show Layer).
Do you have a example that you've set up that isn't working as expected? To open the hyperlink you should tab to it and then use the enter or space bar key to trigger it and open, and since it's a hyperlink you'll need to open while testing within the intended publish environment as detailed here.
I've created a quick example. Even in Preview, there's no way via keyboard to get the yellow box around the hypertext or actually trigger its trigger. We have published content that is in the intended publish environment that is behaving in exactly the same manner.
Thanks for sharing that sample here. It seems that you've set the hyperlink as a part of a larger text box, and as such that is what the tab key is highlighting, so yes there isn't a way to get to the individual text. I'd suggest look at using individual text boxes for when you need to hyperlink or using transparent shapes (like hotspots) over text so that the user can access those with the tab key.
I think if this is considered intended behaviour, then the documention should be updated to list hyperlinks as non-keyboard accessible. We have already had to change our scripting process to remove drag and drops and hotspots, so it should be made clear that hyperlinks also do not support (and there are no plans to support) keyboard-enabled navigation.
In our courses we first attempted to use the default hotspot within Storyline 2. It did not appear in the tabbing order!
Does work:
Insert an object on the screen and then set the transparency to 0% and/or no fill. The object is placed over the location of the on screen hyperlink. That is how we accomplished a tab based application.
The other option was to put links in the resources tab. This is the option that really seems to make the most sense, instead of a link in the text. State: Please refer to the resources tab for more information.
Just sharing some ideas, while we wait for this issue to be corrected.
Thanks for sharing those additional workarounds too. I've reached out to our Quality Assurance team in regards to this issue to confirm if this is working as expected (in that the text within the box is hyperlinked, and therefore the accessibility tools can only highlight the text box) so that if it's not, they can investigate it further. Since I cannot offer a time frame in regards to an update from them or a potential fix, please continue to use those workarounds as mentioned.
Once I have additional information to share, I'll post here for all subscribed and if it's determined to be working as expected we'll be able to have documentation updated as well.
Hi Ashley, any update on this? This is an issue that affects our design process directly for projects we are in the midst of and it would be good to know for sure the official Storyline position on whether embedded hypertext will be officially supported or not. Thanks!
I don't have an update to share and unfortunately I don't have a timeframe in regards to when I'll hear back from our QA team. Since it was a behavior I was unsure about (in that you're tabbing to the correct element - the text box, and the link only exists on the text) I did reach out to our team, but I'd advise going forward with the workaround mentioned.
Myself and my colleagues have just recently upgraded to Storyline 2 and when we open our old (Storyline 1) projects in the new software we noticed our old hotspots are no longer accessible. Having to do the workaround for all of this is a considerable amount of work for us.
The issue with hyperlinks is still with our QA team and I don't have any updates to share. If you have a sample Storyline 1 file where tabbing works as expected and then is broken in Storyline 2 I'm happy to include that as a part of the report.
Hi Ashley, I checked again and I definitely have a Storyline 1 course where the hotspots are accessible but when converted they're no longer accessible (unfortunately I can't share). Seems bizarre!
I can't speak to how it may have behaved, but I know it wasn't set up to be accessible, so it may have been an error in Storyline 1 that was fixed as a part of Storyline 2.
bumping this post... I think this is still an issue in 360, yes? I can't access hyperlinks that are inside of text boxes. Above Ashley states that its because the hyperlink trigger is associated with the whole text box, but only the specific text of the hyperlink makes the item react when hovered over (i.e., the trigger specifies what text the link should work for, and only that text acts like a link/rollerover)... so is there some other way to access links with a keyboard only? I tried the tab key, and the arrow keys, and pressing L (in JAWS) and nothing worked. Does this mean links are still not accessible?
This appears to be still an issue in SL360 today (4 Sep 2019). This is a big problem for screen reader users if using any workaround, as the link is accessed outside of the context of the text it might have appeared within.
Sorry if the workarounds for the hyperlinks aren't helping you. I wonder if anyone who's used it in this discussion can provide a little more insight into their approach.
I do want to share some movement we've had with accessibility as a whole and would direct you to this discussion, where one of our product experts has detailed our commitments to improve features surrounding accessibility!
I've been able to make it work by selecting the entire text object and adding a hyperlink to to the URL. This allows the text object remain in the tab order and pressing enter when the text object receives focus opens the URL in a new window.
I'm happy to report back with an update regarding tabbing to hyperlinks in Storyline 360!
We just shipped Storyline 360 (Build 3.47.23871.0) today, and you'll see that included in this release are many accessibility features. Learners can now tab to hyperlinks in text boxes and activate them by pressing the Enter key.
Make sure to update Storyline 360 in your Articulate 360 desktop app to check out all bug fixes and features included in this update!
Greetings. I am using Storyline 360 v3.51.24979.0 However, I am still unable to get my hyperlink text to be selectable in the tab order. It appears to have been fixed? I have a later SL360 version(so thought it would be working), but I cannot tab to hyperlinks in text boxes and activate them by pressing the Enter key. Is this still an issue?
Thank you for letting us know that you're still experiencing an issue with this functionality.
Accessible text styles, including hyperlinks, must use the modern text feature to make your text styles accessible. Making this adjustment allows your content to work as expected.
26 Replies
We have the same issue, can not tab to a hyperlink.
Hi Kevin and Keith,
Do you have a example that you've set up that isn't working as expected? To open the hyperlink you should tab to it and then use the enter or space bar key to trigger it and open, and since it's a hyperlink you'll need to open while testing within the intended publish environment as detailed here.
This post was removed by the author
Hi Ashley,
I've created a quick example. Even in Preview, there's no way via keyboard to get the yellow box around the hypertext or actually trigger its trigger. We have published content that is in the intended publish environment that is behaving in exactly the same manner.
Hi Keith,
Thanks for sharing that sample here. It seems that you've set the hyperlink as a part of a larger text box, and as such that is what the tab key is highlighting, so yes there isn't a way to get to the individual text. I'd suggest look at using individual text boxes for when you need to hyperlink or using transparent shapes (like hotspots) over text so that the user can access those with the tab key.
Any plans for this to be corrected?
It can be a great deal of additional unplanned work.
Thanks,
Kevin
I think if this is considered intended behaviour, then the documention should be updated to list hyperlinks as non-keyboard accessible. We have already had to change our scripting process to remove drag and drops and hotspots, so it should be made clear that hyperlinks also do not support (and there are no plans to support) keyboard-enabled navigation.
Hyperlink Alternatives
Does not work:
Does work:
Just sharing some ideas, while we wait for this issue to be corrected.
Hi all,
Thanks for sharing those additional workarounds too. I've reached out to our Quality Assurance team in regards to this issue to confirm if this is working as expected (in that the text within the box is hyperlinked, and therefore the accessibility tools can only highlight the text box) so that if it's not, they can investigate it further. Since I cannot offer a time frame in regards to an update from them or a potential fix, please continue to use those workarounds as mentioned.
Once I have additional information to share, I'll post here for all subscribed and if it's determined to be working as expected we'll be able to have documentation updated as well.
Hi Ashley, any update on this? This is an issue that affects our design process directly for projects we are in the midst of and it would be good to know for sure the official Storyline position on whether embedded hypertext will be officially supported or not. Thanks!
Hi Keith,
I don't have an update to share and unfortunately I don't have a timeframe in regards to when I'll hear back from our QA team. Since it was a behavior I was unsure about (in that you're tabbing to the correct element - the text box, and the link only exists on the text) I did reach out to our team, but I'd advise going forward with the workaround mentioned.
Hi Ashley, any update?
Myself and my colleagues have just recently upgraded to Storyline 2 and when we open our old (Storyline 1) projects in the new software we noticed our old hotspots are no longer accessible. Having to do the workaround for all of this is a considerable amount of work for us.
Thanks, Brian.
Hi Brian,
Hotspots were never set up to be accessible as per the documentation here on Storyline 1 and Storyline 2. So instead you'll want to look at using a transparent shape.
The issue with hyperlinks is still with our QA team and I don't have any updates to share. If you have a sample Storyline 1 file where tabbing works as expected and then is broken in Storyline 2 I'm happy to include that as a part of the report.
Hi Ashley, I checked again and I definitely have a Storyline 1 course where the hotspots are accessible but when converted they're no longer accessible (unfortunately I can't share). Seems bizarre!
Hi Brian,
I can't speak to how it may have behaved, but I know it wasn't set up to be accessible, so it may have been an error in Storyline 1 that was fixed as a part of Storyline 2.
bumping this post... I think this is still an issue in 360, yes? I can't access hyperlinks that are inside of text boxes. Above Ashley states that its because the hyperlink trigger is associated with the whole text box, but only the specific text of the hyperlink makes the item react when hovered over (i.e., the trigger specifies what text the link should work for, and only that text acts like a link/rollerover)... so is there some other way to access links with a keyboard only? I tried the tab key, and the arrow keys, and pressing L (in JAWS) and nothing worked. Does this mean links are still not accessible?
It would appear my workaround is still the only way for a link to appear in the tabbing order.
See my previous comment above: Hyperlink Alternatives
All the best,
Kevin
This appears to be still an issue in SL360 today (4 Sep 2019). This is a big problem for screen reader users if using any workaround, as the link is accessed outside of the context of the text it might have appeared within.
Hi Sam,
Sorry if the workarounds for the hyperlinks aren't helping you. I wonder if anyone who's used it in this discussion can provide a little more insight into their approach.
I do want to share some movement we've had with accessibility as a whole and would direct you to this discussion, where one of our product experts has detailed our commitments to improve features surrounding accessibility!
here's what i think of your workarounds: https://kylemackie.wordpress.com/2019/09/26/im-worried-that-your-awesome-storyline-presentation-is-actually-inaccessible/
Am amazed that four years later this accessibility feature is not shipped with 360. Does anyone know if this is feature is active in Captivate?
I've been able to make it work by selecting the entire text object and adding a hyperlink to to the URL. This allows the text object remain in the tab order and pressing enter when the text object receives focus opens the URL in a new window.
Hi everyone! 👋
I'm happy to report back with an update regarding tabbing to hyperlinks in Storyline 360!
We just shipped Storyline 360 (Build 3.47.23871.0) today, and you'll see that included in this release are many accessibility features. Learners can now tab to hyperlinks in text boxes and activate them by pressing the Enter key.
Make sure to update Storyline 360 in your Articulate 360 desktop app to check out all bug fixes and features included in this update!
Greetings. I am using Storyline 360 v3.51.24979.0 However, I am still unable to get my hyperlink text to be selectable in the tab order. It appears to have been fixed? I have a later SL360 version(so thought it would be working), but I cannot tab to hyperlinks in text boxes and activate them by pressing the Enter key. Is this still an issue?
Hello Derek,
Thank you for letting us know that you're still experiencing an issue with this functionality.
Accessible text styles, including hyperlinks, must use the modern text feature to make your text styles accessible. Making this adjustment allows your content to work as expected.
Storyline 360: Accessible Text Styles