Forum Discussion

michaelroddick's avatar
michaelroddick
Community Member
7 days ago
Solved

JAWS and Web Objects Shifting left

I read there was a fix for something similar back in January so I am not sure if this falls within.

What I am experiencing is a shift left on a slide with a web object while using JAWS and navigating down through the content using the keyboard arrow buttons. On the slide, within the web object window, I am pulling an html page that has some example scenarios coded into an accordion using pure html and JavaScript. Nothing fancy.

While the section being read by JAWS is with in the visible area things are fine, its when I arrow down to the content below the visible area that the shift happens.

It only happens with JAWS on, otherwise it works perfectly.

Anyone have any ideas or experiencing something similar? I would love to hear your workarounds. I provided some screen caps.

 

Thanks

Mike

 

 

 

  • Hello,

    I will try to get an example in to articulate, with my workload I am unsure when.

    I did however make some new discoveries; 

    • the shift happens on any slide (not just the above stated web object). Articulate needs to revisit their January "fix."
    • the shift happens when the player is in the responsive state. (when the content sizes with the browser).
    • the only solution I found was to manually set "Zoom to Fit" to true and create a mechanism for the course to remember that setting upon relaunch (resume). Effectively locking the player to specific size.

    This is not an ideal solution (the player should work as intended) as the responsive state makes for the best user experience.

    Alternatively I suppose the variable controlling "Zoom to Fit" could set to true in the IDE but would still need the mechanism if the setting is to persist.

    As an aside I also found that if you force the player to redraw the slide (via loading a layer perse or other force reload the CSS) the redraw temporarily shifts the content back. This is for knowledge not a solution.

     

    Hope this helps others while Articulate addresses the JAWS issue.

     

     

2 Replies

  • Hello,

    I will try to get an example in to articulate, with my workload I am unsure when.

    I did however make some new discoveries; 

    • the shift happens on any slide (not just the above stated web object). Articulate needs to revisit their January "fix."
    • the shift happens when the player is in the responsive state. (when the content sizes with the browser).
    • the only solution I found was to manually set "Zoom to Fit" to true and create a mechanism for the course to remember that setting upon relaunch (resume). Effectively locking the player to specific size.

    This is not an ideal solution (the player should work as intended) as the responsive state makes for the best user experience.

    Alternatively I suppose the variable controlling "Zoom to Fit" could set to true in the IDE but would still need the mechanism if the setting is to persist.

    As an aside I also found that if you force the player to redraw the slide (via loading a layer perse or other force reload the CSS) the redraw temporarily shifts the content back. This is for knowledge not a solution.

     

    Hope this helps others while Articulate addresses the JAWS issue.

     

     

  • Hi michaelroddick,

    Thanks for sharing those details and screenshots, that’s really helpful.

    You’re right to call out the fix from January. The behavior you’re seeing does look similar at a glance. From your screenshots, it looks like the entire slide area, including the web object, is shifting and getting cut off. The key difference here is that it’s being triggered while navigating content inside a web object, rather than directly on slide elements.

    In this case, it would be helpful for us to take a closer look at your setup, including the Storyline file and the HTML content being loaded in the web object.

    If you’re open to it, could you share your Storyline file and the web object source through a support case? That will allow our team to test this behavior with JAWS and determine whether this is related to that earlier issue or something new.

    We’d be happy to investigate further with you there.