Ralph Whitbeck

This is why it is so important to get out of your own little bubble. You need to be exposed to good code, tools, techniques and processes. You need to see what good looks like. You need to know what is possible. I run into so many isolated developers who have so many gaps in their knowledge. Invariably they are always doing things the hard way and just assume that's the way it has to be. So take a class, goto a user group meeting or conference, attend an online webinar, browse coding videos on youtube, read a book, whatever works for you, but break out of your bubble.

4

2 Comments

Accessibility compliance is not a semantic checklist. As an Accessibility Consultant, I keep encountering a persistent misconception: “If the code is semantic and WCAG boxes are ticked, the website is accessible.” Semantic HTML is essential. ARIA correctness matters. Automated checks are helpful. But accessibility does not live in the source code alone. Real accessibility lives in the user experience of people who rely on: • Screen readers • Screen magnifiers • Voice control • Keyboard-only navigation • Cognitive support tools • Alternative input devices A page can be perfectly “semantic” and still be: ❌ Confusing to navigate ❌ Overwhelming to understand ❌ Painful to operate ❌ Technically compliant but practically unusable When accessibility becomes a compliance exercise instead of a usability commitment, we create a dangerous illusion — a false sense of inclusivity. Accessibility is not just about passing audits. It is about removing friction for real humans. If users struggle, compliance has failed — no matter what the report says. Let’s move the conversation from: “Does it meet guidelines?” to “Can people actually use it comfortably?” Because accessibility without usability is just theater. #WebAccessibility #Accessibility #DigitalAccessibility #A11y #InclusiveDesign #UserExperience #UX #AssistiveTechnology #WCAG #AccessibilityTesting #Usability #DesignThinking #ProductDesign #HumanCenteredDesign #AccessibilityConsulting

14

Actually Claude is a game changer when it comes to interactivity and authoring tools personally, I've built a full interactive SCORM package using claude (disclaimer it took too much tokens and I'm using paid account) This bringings the most important question, " why do we pay for just one slow in production famous authoring tool more than 1700$ while we can pay less developing in less time😅" Note to HR recruiters, if you are still hiring learning designers for the FAMOUS authoring tool professioncy not for the mindset nor their learning designing capabilities, you are so doomed!

2

2 Comments

Most Instructional Design mistakes don’t happen in the storyboard… They happen before you even open the file. Over time, I’ve realized great IDs aren’t just content creators—they’re problem solvers, experience designers, and

8

The 5th Design Learning Session for 2025 was an exploration into constraints of legacy systems - and how content writers are left trying to explain workarounds that users shouldn't have to think about - presented by Ashley Draper, from the Cornerstone Design team. The session explored why content can’t fix broken flows, sharing real design examples from our Design team, and how backend constraints can ruin an otherwise simple interaction. While we can't out-write a broken experience, a shift toward AI-powered, agentic systems, is raising the bar for clarity, collaboration, and truly seamless UX. A special thank you to Ashley, and to all our participants! Thank you Jai for driving the presentation and Anjali as always for your guidance and support! #contentdesign #learningseries #AI

51

1 Comment

I got a question for ya'll: Is the eLearning authoring tool as we know it dead? It's a question I’ve been thinking about a lot lately. So, let's discuss! Ya know, a few months back, I invited Jeff Batt into my community to talk about vibe coding...and one of the things he showed was how he was using tools like Lovable to essentially vibe code his own eLearning authoring tool. And I gotta say...it was pretty damn impressive. Since then, I’ve seen more and more people using vibe coding to build custom interactions and other learning elements, and then embedding those into the tools they already use. And this is what got me thinking... If we can vibe code the interaction, at what point can we vibe code the whole learning experience? And if we can do that, then what exactly is the authoring tool for? Is it just a familiar interface? A publishing wrapper? A SCORM machine? A place to organize content? Maybe. But AI can increasingly do those things too. So, at what point does the AI tool stop being the assistant… nd start becoming the authoring environment itself? Well, that’s exactly what I talked about with Melissa Milloway in my new video. 🔗 Watch the full video here: https://lnkd.in/g4xf3rMi Otherwise, I'm curious where you land on this: Do you think traditional authoring tools still have a clear long-term role, or are we watching that category start to break apart? Let me know down in the comments! See ya around! —Tim #eLearning #InstructionalDesign #LearningAndDevelopment #VibeCoding #AI

163

94 Comments