ramblings
I received a question from Bob (no, really), who wrote: I have a question about the newest version of Flash and its HTML publishing option using CreateJS. What do you think of that approach going forward? I started to write an email response but figured I should probably post it
ramblings
At DevLearn 2010, Ben Clark and I presented a session named SOAP for SCORM on behalf of LETSI. The topic was the LETSI Run-Time Web Service (RTWS), a proposed modification of SCORM to use SOAP for communication rather than the current JavaScript model. I presented the first half of the
accessibility
Introducing EasyCaptions: A simple system for adding captions and an interactive transcript to online videos. EasyCaptions uses progressive enhancement to provide the best possible experience for all visitors, regardless of their browser’s JavaScript, HTML5 or Flash support. Demonstration Background I don’t produce much video these days, but as
web design and development
I’m a big fan of the Filament Group’s UI work. They put a lot of thought into their work, and ensure everything they make is not only beautiful, but as accessible and as semantic as possible. One of my favorite pieces of work by the Filament Group is
learning management systems
Think accessibility isn’t a big deal, and is only one of those issues “the other guy” has to deal with? So did Target. And now they’ve lost $6,000,000 because of it. In case you hadn’t heard, Target was sued by the National Federation for the
accessibility
The talented Cameron Moll has posted a link to a Web Accessibility Checklist prepared by Aaron Cannon, a (blind) member of his web development team. Aaron’s checklist is an easy-to-understand list of accessibility _do_s and _don’t_s. Most of these are so simple and easy to implement
accessibility
Adobe has a short but useful article detailing how to make your Adobe Captivate movies more accessible. These are pretty simple (borderline “no-brainer”) steps a Captivate author can easily implement: * Add a description to an Adobe Captivate movie * Add a description to an individual slide * Limit quiz questions to multiple
accessibility
There are a great set links for free development tools (validation services, browser toolbars and plugins) posted on the Web Access Centre Blog today: Looking for alternatives to Bobby and WebXact? Try these! Anyone familiar with accessibility should already know about Cynthia Says and a few of the web-based validation
Industry News
The WCAG Samurai Errata for Web Content Accessibility Guidelines (WCAG) 1.0 (link no longer available) were published this week by the WCAG Samurai group. They don’t contain anything I’d consider Earth-shattering, but there are some very solid guidelines that bring the 1999 WCAG 1.0 specs a
best practices
Understanding that we should be using standards and best practices throughout e-learning development, the question becomes “what standards and best practices should we follow?” Here’s my attempt at outlining some basics. Please feel free to suggest additional items in the comments section. Follow established “web” best practices. Separate presentation
ramblings
Question: Why don’t more e-learning developers use standards? I don’t know for sure, but I have a number of guesses. Here’s a quick list off the top of my head: * Lack of knowledge about standards * Confusing or obtuse documentation * Competing standards * Misconceptions about cost effectiveness * Difficulty / Lack
ramblings
This post was triggered by BJ Schone’s question “How do you build e-learning courses?“ So, here’s my question: How do you build your e-learning courses? Do you build them from scratch (ex. HTML, JavaScript, etc.)? Do you use an authoring tool for the whole course structure? This is