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
e-learning
I’ve had a number of people ask me about extending my SCORM helpers (the JavaScript-based SCORM API wrapper and the two ActionScript classes) in order to completely remove the need to know any of the “cmi” calls. For instance, being able to do something like this: scorm.bookmark = "
ActionScript
There is a newer list of variables available, which includes new Captivate 4 variables. A recent post (link no longer available) in the elearning development forum (link no longer available) reminded me that I forgot to post some unpublished Captivate variables I dug up a while back. These were gathered
e-learning
The SCORM API wrapper (v1.1.7) has been updated to automatically set the initial course status and the exit status. The point of my SCORM API wrapper is to make working with SCORM easier. These two new functions are intended to ensure you follow best practices with your SCORM
e-learning
Ok, I just had to write a quick blurb about this one: in about 3.5 years of using SCORM in my own course code, I had never used cmi.core.exit (SCORM 1.2) or cmi.exit (SCORM 2004). Seems incredibly daft of me now that I’ve taken
Tutorials
In my previous post, I briefly explained how to add SCORM code to an existing Flash file by using the pipwerks SCORM wrapper and SCORM ActionScript class. Today, I’m going to explain how to add SCORM code to a plain HTML file. This example uses SCORM 1.2 syntax,
SCORM actionscript class
Update 10/2011: The Planets example has been updated (almost completely rewritten) and no longer strictly adheres to the steps and screenshots in this tutorial. The general concepts are the same, but the project files have been substantially refined. To prevent confusion about which files to use, I have removed
Microsoft
In case you hadn’t already heard: The “click to activate” behavior, formerly required for ActiveX controls embedded in some webpages, is now permanently removed from Internet Explorer. You’ll need to get the April 2008 Internet Explorer Cumulative Update. I believe the proper response is “woot!” [ Read the full
Project Updates
Here’s a bunch of news updates regarding the pipwerks SCORM JavaScript wrapper. Time for class? A big fad these days is object-oriented JavaScript; libraries such as jQuery and MooTools make it really easy to create JavaScript “classes” (in quotes because from what I can gather, they’re really JavaScript
Adobe Captivate
Many of us use a Flash-based course interface (a.k.a. ‘player’) to load Captivate SWFs and other content. A well-known stumbling block for this kind of ‘loaded SWF’ approach has been Captivate’s lack of ActionScript support — Captivate won’t allow a user to add a simple line of
ActionScript
A few months ago I wrote about the dilemma of trying to load Captivate SWFs into an ActionScript 3-based parent SWF. Dilemma solved! I present to you the ActionScript 3 class LegacyCaptivateLoader. This class utilizes ExternalInterface and a proxy SWF to facilitate sending commands to and querying data from an
Blackboard v Desire2Learn
Alfred Essa posted this tidbit today: An Important Correction to the Blackboard Patent Story A number of us, including this blog, have gotten this story wrong. It’s time for a correction. The USPTO has NOT invalidated the Blackboard patent. Instead the USPTO is proposing to invalidate the patent and