Forum Discussion

Matthew_M's avatar
Matthew_M
Community Member
10 days ago

Picture States and Visibility to Accessibility Tools

Hello! I recently build some interactions in a project using the "Insert pictures as states" feature (https://www.articulatesupport.com/article/Storyline-360-Adding-and-Editing-States ) based on this tutorial Flipbook Animation in Storyline | Sync PNG Frames to a Slider or Dial where the user could then animate the states. It's a neat way to get some animation into storyline as well. 

The trouble I have is the "Object is visible to accessibility tools" is checked on for all of these pictures within the states. Right now it's like 30 images; 1 per state, 30 states, all on one main picture 'object'. 

I do not want to have to go to each state to uncheck each image if I can help it. 

I tried using the accessibility checker, as it lists all the images in all the states as missing alt text, and allows you to uncheck them from there, but there is some strange behaviour.

 

When you uncheck just one of these, they ALL disappear from the accessibility checker, and are ALL disabled to accessibility. However, this also disables the main object on the timeline. When I then try to enable the main object on the timeline again, so there is at least something visible by a screen reader, ALL of the pictures get turned back on. So it's an all or nothing situation.

Any chance I'm missing something here, and there is some other way to disable all these images for screen readers, but still leaving the main timeline object enabled?

 

accessibility
e-learning development
storyline 360

1 Reply

  • EricSantos's avatar
    EricSantos
    Staff
    4 days ago

    Hi Matthew_M,

    Thanks for sharing those details.

    I’d like to investigate this further before confirming whether this is expected behavior or something we should report to our team. Would you be able to share:

    1. A simplified Storyline file that reproduces the issue with just a few picture states.
    2. Whether this also happens in a brand-new Storyline file.
    3. A short screen recording showing what happens in the Accessibility Checker.

     

    One thing that would be especially helpful is comparing whether the same behavior occurs when images are added manually to states versus using Insert Pictures as States. That will help us determine whether the behavior is specific to that workflow.

    If you'd prefer not to share your Storyline file publicly, you're welcome to open a support case and send it to us privately. We'll be happy to take a closer look.