Forum Discussion
Most accessible interactions
Hi LisaEdmondson-4 the following link provides information on which interactions are accessible, and which are not: https://www.articulate.com/about/accessibility/storyline-360-accessibility-conformance-report-vpat/
It is possible to make the drag and drop interactions keyboard accessible, but treating the interaction differently. For example, allowing the keyboard user to "select" the drag item, then tab to the drop target and "select" the drop target. You can then have a trigger that checks if X is selected and Y is selected, then correct and so on. This is a simplified explanation, as they is more to it than that, but this is the solution that is required.
LeslieMcKerchie I am working on creating an accessible drag-and-drop using the information from this webinar. It is very helpful. I have a couple of additional questions.
1. I started with a drag-and-drop template and then added the accessibility triggers as shown here. Do I need to rebuild this on a black slide, or will it be okay having already started with the template?
2. How can I test if the "select" and animation path work? The drag-and-drop trigger works, but I don't know how to test whether the animation trigger is working for the accessibility option. It doesn't appear to be, but maybe you need a screen reader for it to work?
Hi snugent
It would be helpful if we could see the slide you're working on so we can better understand the setup and recommend any next steps.
Could you import the slide into a new project and share the .story file for folks to take a look?
LeslieMcKerchie Here is an example. I tried adding a trigger that would let the user select an item and press Enter to move the selected drag item to the drop. However, I can't test if it is working. In the preview, I am unable to use the tab key to navigate through the elements. I can only move to the controls.
Hi snugent
Thank you for sharing that example. It was really helpful.
What you’re running into is actually something we weren’t previously aware of. I’ve reported this behavior to our engineering team and linked this conversation so they can investigate further. We’ll follow up as soon as we have any updates to share.
In the meantime, I put together a small sample to offer an alternative approach. On slide 2, I recreated a similar select-and-move interaction without using a freeform drag-and-drop. This version supports both mouse and keyboard interaction, and the focus indicator appears as expected when navigating with the keyboard.
While it’s not a direct replacement for drag-and-drop, it can help provide a more accessible experience for now.