Ack! My accessible SCORM isn’t working in my LMS!
summary
Shows that accessible content can still fail at delivery: a blind tester using a screen reader cannot register (Coassemble redirect issues), so the course never reaches learners. Recommends three concrete practices: test registration and self‑enrollment end‑to‑end, publish in a neutral LMS first (SCORM Cloud or Reach360) then in the target LMS, and use vetted course templates/course shells for consistency. Mentions tools (Articulate Storyline/Rise, Adobe Captivate, SCORM/Tin Can/HTML), two rounds of UAT with assistive‑technology users, and keyboard‑only checks.
AI-written summary · about
chapters (14)
- 0:00Accessible SCORM troubleshooting intro
- 2:50Why accessible learning matters
- 7:28SCORM in LMS delivery issues
- 9:32ADDIE for implementation testing
- 12:22POUR in Universal Design
- 14:52Registration testing with assistive tech
- 17:25Tip 1: Self-registration works
- 20:12Tip 2: Test content in neutral LMS
- 24:28Tip 3: Template for consistency
- 26:37Crowdsourcing troubleshooting tips
- 30:16Budget testing with internal teams
- 32:46Testing in actual LMS
- 35:37Overcoming MVP mindsets
- 37:45Key takeaways and next steps
related talks
48mAchieving Optimal Accessibility in Storyline and Other eLearning Environments
53mAccessible eLearning and More through Universal Design
51mWhat Is The Future of Accessibility?
53mAdapting Courses and Gamified Content for Blind and Low Vision Learners
47mA Beginner’s Guide to Inclusion and Accessibility
36mSustainable Accessibility Learning
40mAccessibility, Eyes Closed
25mHello Accessibility, my old friend