Tabbing to hyperlinks (accessibility) not working - Storyline 2

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?