I am trying to create accessible e-Learning. Also, I am required to output my course file in HTML format. HOWEVER, it seems like the auto label feature for accessibility is only applicable for SWF output (FLASH?). Is that TRUE? Will it change eventually in 2017 or 2019 version?
The post Captivate: if I output to HTML, I have to un-check “Auto Label” box in “Item Accessibility” and enter my own text? appeared first on eLearning.
It’s a big day today in the world of accessibility, as the W3C today introduced the latest update to WCAG Standards. These are the guidelines used to ensure that content and software accommodates the needs of diverse audiences. The new standard augments the previous set (version 2.0) and is given the new version number (2.1.) You can read all about it in this fantastic overview from Andrew Kirkpatrick, Adobe’s Group Product Manager for Accessibly.
You may at this point find yourself wondering, what’s the difference between WCAG Standards and 508 Standards for Accessiblity. Here’s a handy comparison chart – at least for WCAG 2.0 Standards comparison. In a nutshell, the WCAG standards are more extensive.
Here is the Captivate overview that I find the most useful. You’ll notice that the linked overview includes both information about how Captivate meets Accessibility standards, and how to setup / configure accessibility within your projects.
How are you using accessibility standards in Captivate? Which articles have you found the most useful as you implement your solutions?
The post Accessibly in Adobe Captivate appeared first on eLearning.
Adding closed captions to your eLearning courses is a basic requirement to meet accessibility standards like Section 508 and Web Content Accessibility Guidelines 2.0. You can easily do so for your audio-based courses by adding narration to your screen, adding slide notes, and then converting those slide notes to closed captions. But a little known […]