Forum Discussion

DaveSundberg's avatar
DaveSundberg
Community Member
4 years ago
Solved

Web Object Accessibility focus

Hello,

I am using a web object to display a web page which works fine but I can't seem to use the arrow keys UNLESS I select inside the web object with a mouse. There seems to be no way to give focus to the page inside via keyboard. Is there something I'm missing or is this just how SL operates? If it is, it breaks accessibility for us and makes it unusable.

thanks, dave

  • Hello everyone,

    Happy to share that we've just released a new update for Storyline 360!

    In Build 3.106.35838.0 we’ve included essential fixes and new features. One of the bugs we’ve fixed is:

    • Keyboard navigation didn’t work for web objects on layers, and screen readers didn’t announce their alt text.

     

    Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You’ll find our step-by-step instructions here.

    Please let me know if you need additional help.

21 Replies

  • Hello, was there ever a solution found for the original problem posted four years ago, other than the  javascript workaround share by Jamie 9 months ago?

    I have a course with multiple videos. The course has been tested using both NVDA and Jaws. All videos work ok with the screen readers except for two that are from YouTube. I have tried both embedding in an iframe and using the web object approach. I have tried with and without setting 'disablekb=0' (as in theory it should default to working with keyboard controls). 

    The videos sit in a dialog layer, but I have also tried putting them on the base layer, and have tried as a standard layer.

    However, similar to Dave's experience in the original post, the video will only play if selected with a mouse click. The video (as web object or online video) is in the focus order, but it doesn't appear to be 'seen' when using keyboard controls; tab just goes straight from controls in the surrounding player, to the button that takes the learner back to the base layer screen.

    Any idea what I am missing in this set-up? 

    Note: If Jamies workaround is the solution, is this for embedding in an iframe or as web object?

     

    For info:

    I've looked for help online at

    'Articulate: Storyline - how to add YouTube videoshttps://access.articulate.com/support/article/How-to-Add-YouTube-Videos-to-Articulate-Storyline-360-Courses

    elearning heroes - editing web objects

    Storyline 360: Editing Web Objects | Articulate - Community

    And various pages under the storyline accessibility section.

    • DaveSundberg's avatar
      DaveSundberg
      Community Member

      Hello,

      Could you post the example on Review and send me the link to take a look at it? I think this issue has been resolved but since you are experiencing the issue, it may not be.

      Thanks, dave

      • KirstyLeeder-a8's avatar
        KirstyLeeder-a8
        Community Member

        It doesn't look like my first reply was sent. I appreciate you replying to my post Dave.  In the link 'Accessible videos' (or not!) there are two slides. One is based on my original set up embedding a YouTube video in an iframe, and the other uses a web - object. Both slides are set up the same, in that the video is on a dialog layer. You can select both of them with a mouse click, but I (and my screen reader tester) are unable to select them using keyboard controls.  Grateful for any suggestions you have. 

  • Thanks Dave. 

    Appreciate you responding so quickly.

    For info, I am previewing in Chrome, and trying to view using keyboard only, to emulate how our screen reader testers would navigate.

    This scene has two slides in. One has the original set up using iframe, and the other uses web object to open the same video. Both slides are set up the same in terms of video layer is a dialog.

    Accessible videos (or not!)

    Kirsty

  • Hmm, did you get the reply I sent Dave, with a link? I'm not seeing it here. I will check back again later.

      • KirstyLeeder-a8's avatar
        KirstyLeeder-a8
        Community Member

        Very odd. I have posted the same message twice now, explaining what is in the file and including a link to the Review 360 file. It initially shows in the feed, but when I come back it has gone. I'll reach out direct to our articulate support, but will come back here if/when I get a solution. I do appreciate you responding so swiftly though.

  • Resolved my issues by not having the video (embed or web object) on a dialog layer. Help provided by Dan at OmniplexLearning :).

    Although as I posted above, I did originally try this and it didn't appear to work, so I will put that down to 'user error' in saving/publishing!  

  • Hello everyone,

    Happy to share that we've just released a new update for Storyline 360!

    In Build 3.106.35838.0 we’ve included essential fixes and new features. One of the bugs we’ve fixed is:

    • Keyboard navigation didn’t work for web objects on layers, and screen readers didn’t announce their alt text.

     

    Launch the Articulate 360 desktop app on your computer to take advantage of this update, and click the Update button next to Storyline 360. You’ll find our step-by-step instructions here.

    Please let me know if you need additional help.