New thread discussion greyed out and marked Reported

Thanks again Phil. Yes, I know. I shoulda/coulda/woulda done it differently but I'm under enormous time pressure to convert an existing Dragon Drop to be accessible and found Sally Wiedenbeck's solution on these boards, but it became exponentially more difficult keeping track of what was moving to where, what states should be monitored and how Storyline could monitor if the activity was attempted (Invalid Answer) and also provide a Try Again.

Dragon Drops aren't a great educational tool and nearly all my clients avoid them for accessibility reasons. however, this was asked for and time is of the essence, and needs must. I am not that familiar with these interactions as well, so I'm not completely understanding why dragged objects AND drop targets need Correct and Incorrect states. Do they? Which takes precedence? And what makes an item draggable - having these states?

I realised I just have to monitor the DropZone states and base my programming on that.

The video in question is merely showing how a partially OCD person like me needs to have an order on items, especially when it comes to troubleshooting. Hence the clip shows me simply trying to reorder the objects into numerical sequence but not being able to drag them, like other variables. The glitch is when it comes to trying to delete them - they won't disappear immediately as expected, and it's only when one clicks the +Object button that the deletion takes effect.

I'd love to see how you'd go about your solution. I have trouble visualising (sooooo tired) how dragging objects triggers layers.

 Anyway, thanks for looking. Here's an interesting screengrab I just received from my file when I tried to copy text from a word document into the Alternative Text field within the Focus Order panel.

And then this lovely beauty when I saved and exited.

I am almost too scared (and scarred) to open the file back up and see what's left.