Forum Discussion
Tabbing to hyperlinks (accessibility) not working - Storyline 2
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).
Thanks!
26 Replies
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.
Thanks so much Leslie! Totally worked, no problem.
...and by "completely rebuilt", they mean "fixed a glaring foundational accessibility issue that was reported nearly 6 years ago so it should actually work properly".
