Accessible Design Doesn't Have to Be a Drag
summary
Shows how a standard drag‑and‑drop becomes usable by blind and motor‑impaired learners by layering keyboard triggers, motion paths and states on top of the visual interaction. Builds the prototype in Articulate Storyline, follows WCAG 2.5.7, and publishes a free downloadable template that uses about 40 triggers and cost eight hours to create the first time. Keyboard navigation works with tab/enter/arrow keys, testing recommends NVDA or other screen readers, and the template returns correct, incorrect and try‑again feedback.
AI-written summary · about
chapters (21)
- 0:00Accessible design intro
- 1:28Drag and drop failures
- 3:53States and motion paths
- 6:00Setting up triggers for drag and drop interactions
- 8:30Testing accessible drag and drop
- 10:37Feedback and keyboard nav
- 12:25Focus order and alt text
- 14:10Universal design for all
- 15:36Downloadable template
- 17:26Q&A on interactions
- 20:45Draggable interaction Q&A
- 21:49Trusted Tester insights
- 22:55Beta testing feedback
- 23:36Time investment for templates
- 24:42Finding 508 testers
- 25:45LMS integration
- 26:48Animation guidelines
- 28:14Screen reader testing
- 29:39Closing remarks
- 30:01Screen readers quick guide
- 31:06Final Q&A
related talks
46mExclusive design
48mAchieving Optimal Accessibility in Storyline and Other eLearning Environments
01h 02mBeyond Compliance: Creating Exceptional Screen Reader Experiences in Learning Design
31mDeveloping for Everyone
41mTales of Accessibility Failures
44mDesigning with Accessibility in Mind
22mInclusive UI design
57mDesigning for people who use a mouse