Accessibility in Adobe Captivate
Comments
(0)
Accessibility in Adobe Captivate
(0)

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 Accessibility. Here’s a handy comparison chart – at least for WCAG 2.0 Standards comparison. In a nutshell, the WCAG standards are more extensive.

I am often asked how accessibility works in Adobe Captivate.  You’ll find a number of great resources right here on the forum (Like this one & this one from justenuf2bdangerous) that can guide you through the process of adding Closed Captions, or adding names and descriptions for screen readers to content in Captivate.  If you’re looking for some more advanced options, check out this very cool walk through of a JavaScript based popup solution complete with custom accessibility enhancements from sdwarwick of eLearningOcean.

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?

 



Please log in and complete your profile to continue.
0 Comments
Add Comment