Forum Discussion
Build an Accessible Drag and Drop Interaction in Storyline
If you've ever needed to build an accessible course in Storyline, you may know that the built in drag and drop interactions are not accessible (see the VPAT).
However, with some extra work it is possible to create your own drag and drop interaction in Storyline that is fully accessible.
The issue with drag and drop interactions and accessibility is that people who access the computer using only a keyboard or assistive input device, and no mouse, cannot click-and-drag. So, the interaction must have another option, that works through the use of keyboard inputs (typically, the tab and enter keys). In Storyline triggers, anything that is done "on click" can be mimicked by a keyboard or other input device. To build a keyboard-accessible drag and drop requires building a second set of triggers that function using click-based rather than drag-based interactions.
Here is how to build your own keyboard accessible drag and drop interaction in Storyline.
Please note that you may include other elements that are not fully accessible. Take a look at the WCAG Guidelines to evaluate other aspects of your course creation
This interaction relies on a user-selected submit button. This button needs to be on the slide, as the triggers used are not compatible with the built-in submit button in the Storyline player.
Note: It will be easiest to create all layers, elements, and states before creating the triggers.
LAYERS NEEDED
Base Layer – Most of the triggers will be on the base layer.
Correct – A feedback layer for when the user submits the interaction, when all items have been moved to the correct drop location.
Incorrect – A feedback layer for when the user submits the interaction, when the interaction is incomplete or some items have been moved to the wrong location on the screen.
BASE LAYER
Elements Needed
Drag items – one or more
Drop targets – one or more
Submit button – one
Drag Item States
Normal - The built in state. This does not need to be modified.
Selected - Create a “Selected” state. Make sure to edit the selected state to include a visual indicator that the item is selected. An easy way to do this is to add a “glow” shape effect in a color contrasting the object.
Drop Correct - Create the “Drop Correct” state. You may want to visually signal that the drop was completed. One way to do this is to darken or desaturate the object in the “drop correct” state.
Drop Incorrect - Create the “Drop Incorrect” state. Make this state visually identical to the Drop Correct state.
Triggers
Submit Button
1. Show layer Correct when user clicks
If Drag item 1 state equals Drop correct
And Drag item 2 state equals Drop correct
… (Continue through the rest of the drag items)
2. Show layer Incorrect when user clicks
If Drag item 1 state does not equal Drop correct
Or Drag item 2 state does not equal Drop correct
… (Continue through the rest of the drag items)
Drag Items
For each drag item:
1. Change the item’s state to Drop Correct when it is dropped on the right drop target
Change state of Drag Item 1 to Drop Correct when user drops Drag Item 1 on Drop Target 1
2. “Deselect” all other drag items when this drag item is selected (Change other drag items’ states to Normal, if they are currently selected)
Change state of Drag Item 2 to Normal when user clicks Drag Item 1
If Drag Item 2 state is equal to Selected
Change state of Drag Item 3 to Normal when user clicks Drag Item 1
If Drag Item 3 state is equal to Selected
… (add this trigger for all other drag items on screen)
3. Change the item’s state to Drop Incorrect when it is dropped the wrong drop target(s)
Change state of Drag Item 1 to Drop Incorrect when user drops Drag Item 1 on either Drop Target 2 or Drop Target 3 … (include all incorrect drop targets in the list)
Drop Targets
For each drop target:
1. Move the selected Drag Item along a motion path to the Drop Target when the user selects the drop target. NOTE: The move triggers MUST be before the state change triggers in the list
Move Drag Item 1 on Motion Path* when the user clicks Drop Target 1
If Drag Item 1 state is equal to Selected
* For the motion path, create a line motion path with start and end points in the center of the drop target. This will move the object to the correct location without showing movement on screen. Make sure to go into the path options and select “locked” for origin. This will ensure that no matter where on the slide the object starts from, it will move to the correct position with the trigger. Name the motion path something descriptive so you can identify it in the trigger list (ex: Drag 1 to Drop 1 Path).
NOTE: When you create a motion path, Storyline automatically adds a trigger to the object to follow the motion path when the slide timeline starts. Make sure to go in and remove all of these triggers.
… Make this trigger for all drag items on the slide.
2. Change the state of the corresponding Drag Item to Drop Correct, if the Drag Item is selected
Change State of Drag Item 1 to Drop Correct when the user clicks Drop Item 1 if Drag Item 1 state is equal to Selected
3. Change state of the selected drag item to Drop Incorrect for all drag items that do not match with this drop target
Change State of Drag Item 2 to Drop Incorrect when the user clicks Drop Item 1 if Drag Item 2 state is equal to Selected
… Make this trigger for all remaining drag objects on the slide.
CORRECT LAYER
Elements
Text box(es)
Continue button
Triggers
Continue button
Jump to next slide
INCORRECT LAYER
Elements
Text box(es)
Try Again button
Triggers
Try Again button
Jump to slide (current slide) – this restarts the interaction on the slide base layer
NOTE: Make sure the slide is set to “Reset to initial state” for the “when revisiting” selection in the slide properties.
And there you have it! It looks like a lot, but once you've done it a time or two you can get the hang of it.
Below is an example .story file of this interaction. It uses the same names as the instructions above so you can see how this all looks in a project.
99 Replies
- SalWiedenbeckCommunity Member
Hi Dominic,
Your triggers for showing the correct feedback layer and the try again feedback layer were identical, when they need to be different. They should look like this:
Your show layer correct was how it should be. Your show layer Try Again should be set to happen if the state of any drag item is drop incorrect (you had it to drop correct), and the conditions on it should be set to 'or' not 'and' so that it shows the try again layer if any of the drag items are in the drop incorrect state.
Hope this helps!
- EllysaYesCommunity Member
Hi Sally thank you so much for sharing! This is an excellent resource as faculty often use drag and drop and form view despite its accessibility issues. Is there any way to use this technique for instant corrective feedback? Or would that require the learner pressing the submit button after every choice they make?
- SalWiedenbeckCommunity Member
Yes, you could build it so something shows up as soon as the item is dragged to the drop target/as soon as the drop area is selected by the keyboard. It would just be a different trigger than the submit button trigger
- SalWiedenbeckCommunity Member
Dominic - just noticed a couple other things in your file:
1. You built these triggers on top of the built-in drag and drop. Unfortunately, that won't work for a keyboard accessible option, because the way the built-in drag and drop is created, a keyboard user cannot select the drag items. Go to the Insert tab and select remove freeform to change this.
2. If you want your user to try again, change the try again button on that layer to "jump to slide" and set it to the same slide. Make sure your slide settings are 'reset to initial state.' This will reset the interaction on the base layer when the user clicks the try again button.
3. When using the keyboard interaction (after completing step #1 above), your drag items move to underneath the drop targets. Make sure your drag items are at the top of the timeline stack so they move to on top of the drop targets instead of underneath.
These should all be quick + easy fixes, but let me know if you want more detailed information.
- SalWiedenbeckCommunity Member
Hi Dominic,
Your new file seems to be working for me - what specifically is not working for you?
The only thing I see is the drop targets are still above the drag items in the timeline stack, so in the keyboard use the drag items move behind the drop targets instead of in front.
- DominicKnowles-Community Member
Hi Sally
I've resolved the issue having the drag items in top, but in preview the content doesn't move when using the Tab and enter keys. Should it work with these keys?
- SalWiedenbeckCommunity Member
Dominic - It did work for me with those. I tabbed to a drag item, hit enter to select it, then tabbed to the drop target, and hit enter again. That moved the drag item to the drop target as it should.
- DominicKnowles-Community Member
Sally - Thanks for the reply. I'll need to look into it as it is not working for me.
- DominicKnowles-Community Member
Can you suggest anything?. I have used as laptop and normal keyboard and neither work.
- JulieWillett-f0Community Member
Hi Sally. I want to attempt to build this. I have one question - does this approach work for a screen reader? I have been told that several layers are hard with accessibility because the screen readers will read all layers as if they are on one layer. It doesn't react to the triggers that leave layers inactive until they are triggered. Have you tested it with a screen reader or is that still an accessibility issue, even if we satisfy the keyboard compliance?
- SalWiedenbeckCommunity Member
Hi Julie,
Yes, this has been tested and worked with JAWS. I am curious where you heard that about screen readers and layers, that's not how that should be working. If it is an issue for your users and the screen reader they are working with, you can also change the feedback layers to separate feedback slides, and change the 'show layer' triggers to be 'jump to slide' triggers.- RobiCalderaro-6Community Member
Hi,
I tested it with NVDA and it didn't work.
- RobiCalderaro-6Community Member
Hi,
I tested it with a screen reader, and it didn't work. Tabbing and selecting didn't do anything, apart from moving the first drag item.
Thank you for sharing though :)
- LizWatkins-5857Community Member
This is great, but I can hear my client saying they do not want the user to be able to put all three into one box.
- SJKJCommunity Member
Hi Liz, did you find a fix for this issue? Thanks!
- RobiCalderaro-6Community Member
Hi,
Thank you for the example. Tabbing through it doesn't work.