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.

 

43 Replies
Sally Wiedenbeck

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.

Scott Wiley

I always avoid drag and drops for these very reasons. When you consider you can only answer (drop) one question (drag) at a time, why not consider a multiple choice quiz, multi-radio button interaction, drop-down matching, etc.?

It just seems to be a lot of work for little payoff to the learner, or the developer.

Carolyn Seiger

I'm running into a bit of a problem.  I have a drag and drop exercise where drag items are being sorted into two categories.  I've created separate spaces for each drop, but set it so that the drag item that falls under that category can go to either drop target and still be considered correct.  For some reason, using the keyboard will not allow me to move the drag items to the drop target.  Can anybody help me figure out how to set that up?  The problem is on Module 3 Slide 10.

Shane Drosi

Hi there! Thanks for the detailed documentation. I re-created the activity and was successful with the drag and drop functionality. For some reason, when I tab and select an item and then tab to drop it on it's target, when I select on the target, the item goes away. It also does not show the "Drop Correct or Incorrect State" when tabbing, but does when dropped manually. I have re-built the triggers twice and can't seem to find the issue. Any advice?

Eric Kowalik

Shane, the reason the item goes away is because the target is higher than the item in the timeline so when the item moves to a target it "disappears" because it is being placed beneath the target item.

To fix this, right click the item and in the drop down select Bring to Front > Bring to Front. Your item is now above the target in the timeline and will show up when moved to it.

The item does not show the Drop Correct or Incorrect state because you need to adjust the Change State condition on your target. Change the conditions from "If the state of target 1 = Selected" to "If the state of item 1 = Selected".

Amanda Fraize

I'm hoping that Articulate is working on offering template slides that preformatted for accessibility, additionally identifying web parts that are and/or are not accessible. I work for the federal government, so have learned the hard way what to avoid in order to be 508 compliant for web posting. JAWS can be unpredictable and often can read what isn't evident.  I love Articulate and would love for our national 508 office to be confident in the software as well.  

Kelly Auner

Hi Amanda,

We appreciate your feedback. Accessibility is very important to us, and we're committed to refining our Storyline 360 features to be accessible for everyone. Here's a resource on how to design an accessible course.

I understand that you'd like the option to choose from templates that are pre-formatted for accessibility. As we’re working on accessible features, our team is also looking at the accessibility of our Content Library templates. We’ll continue to share updates to our feature roadmap and in relevant E-Learning Heroes discussions.

If you discover an accessibility issue, please let us know!