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
Here’s a simple example of how the SCORM AS3 class can be utilized. (This example uses SCORM 2004 calls.) import pipwerks.SCORM; import flash.external.ExternalInterface; //Declare variables var success:Boolean = false, completion_status:String; //Initialize a new SCORM object! var scorm:SCORM = new SCORM(); //Initialize SCORM connection success
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
Small but important edits: * Added snippet of code to double-check API connection is active before returning a ‘true’ boolean value. * Fixed a typo for evaluating whether an error code has been returned from the LMS Also added some code from the Firebug folks that allows Firebug’s “console” functions to
I just saw something interesting I thought I’d pass along. In the new HTML 5 proposal, the strong element is being modified to represent “importance rather than strong emphasis.” The WHATWG gives the following example: <strong>Warning.</strong> This dungeon is dangerous. <strong>