The limitations of browsers and the HTML5 spec mean you can’t expect a fully 1:1 conversion from Flash to HTML, regardless of libraries like CreateJS.
I’m currently working on a new quiz system at work, and decided I’d incorporate Filament’s wonderful stylized checkboxes and radio buttons into my project, which meant it was time to roll up my sleeves and code me some Moo.
Eventually someone in the e-learning field is going to get slapped with a lawsuit just like Target did. If that’s what it takes to wake people up, I’m hoping it’s sooner rather than later!
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.
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.
The WCAG Samurai Errata for Web Content Accessibility Guidelines (WCAG) 1.0 were published this week by the WCAG Samurai group.
There are a great set links for free development tools (validation services, browser toolbars and plugins) posted on the Web Access Centre Blog today:
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.
I’m 100% positive I’ve missed a few things, and I’m pretty sure not everyone will agree with my statements. Why not join in and add your two cents?