WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Lectora and accessibility

for

From: Lisa Morgan
Date: May 29, 2009 3:35PM


Joe, thanks for the info. I hadn't found the Forum up to now; appreciate that tip and hearing your experience w/Lectora. ~Lisa

-----Original Message-----
From: Rothschild, Joseph T. (CDC/CCHIS/NCHM) (CTR) [mailto: <EMAIL REMOVED> ]
Sent: Friday, May 29, 2009 6:54 AM
To: WebAIM Discussion List; <EMAIL REMOVED>
Subject: Re: [WebAIM] Lectora and accessibility

Lisa,

I've worked with Lectora and accessibility for the last 4 years, and I can tell you that if you do things correctly, your resulting course can be very accessible and Section 508 compliant. It does, however require a lot of foresight and a few hacks and workarounds. The resulting html I seriously doubt is W3C compliant, but often that doesn't matter as long as it's 508 compliant.

Anyhow, yes, you can add alt tags to images, we often hide descriptive text that just screen reader users will hear under images and multimedia files, etc.

My suggestion is that you go to the Lectora Forum (now an cruddy wannabe web 2.0 portal - yuck!) and go to the screen readers section and poke around there. You'll be able to find a wealth of info there.

Hope that helps-

Joe
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

.:: Joseph Rothschild ::.
.:: Pixels Misshapen, Not Stirred ::.
.:: 508 Accessibility Specialist / New Media Developer ::.
.:: Contractor with Northrop Grumman ::.
.:: CDC National Center for Health Marketing ::.
.:: Division of eHealth Marketing - New Media Group ::.
.:: Office. 404.498.1140 ::.
.:: Mobile. 858.204.8105 ::.
.:: SL. Fender Soderstrom ::.






-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Lisa Morgan
Sent: Thursday, May 28, 2009 4:32 PM
To: <EMAIL REMOVED> ; WebAIM Discussion List
Subject: Re: [WebAIM] Lectora and accessibility

Tom, thanks for the info. I had already found the Lectora accessibility fact sheet, and I do realize that the person developing the Web resource plays a large role. My question was kind of two-pronged: What do people think of the HTML that Lectora outputs (my understanding at this point is that it doesn't conform to Web standards)? And, could anyone who's used the tool share what their experience with implementing accessibility features has been? In my experience thus far, for example, although the Lectora fact sheet indicates that the criteria for adding alt text to images is "fully met" and is "course developer controlled," I don't see any way to add alt text.

Thanks again,

Lisa

-----Original Message-----
From: Tom Babinszki [mailto: <EMAIL REMOVED> ]
Sent: Wednesday, May 27, 2009 10:19 AM
To: WebAIM Discussion List
Cc: Lisa Morgan
Subject: Re: [WebAIM] (no subject)

Hi Lisa,
 
Lectora claims to be totally Section 508 compliant, they actually put out a VPAT several years ago:
http://www.trivantis.com/support/downloads/508%20statement_0.pdf
 
In the VPAT the way they describe accessibility is developer controlled. And when you put out electronic materials, accessibility does not only depend on the authoring tool, the accessibility knowledge of the developer is just as important.
 
I don't have an extensive experience with the product, but a pointer to give you is that they work with some government agencies and companies which are very unlikely to accept a solution which is not Section 508 compliant.
 
Tom
 
Tom Babinszki, PMP
Even Grounds
Accessibility Consulting
E-mail: <EMAIL REMOVED>
Phone: +1 (703) 853-2990
http://www.evengrounds.com 



--- On Wed, 5/27/09, Lisa Morgan < <EMAIL REMOVED> > wrote:


From: Lisa Morgan < <EMAIL REMOVED> >
Subject: [WebAIM] (no subject)
To: <EMAIL REMOVED>
Date: Wednesday, May 27, 2009, 10:49 AM


Greetings, all -

The e-learning unit at the company I work for has adopted Lectora to use in creating online courses. I'm going to be talking to our course production team about the accessibility ramifications of using Lectora, in terms of the content that it outputs, so I've been searching for information (and I haven't found much).

If anyone has had experience using this tool or has knowledge about its potential for producing accessible content that conforms to Web standards, I would appreciate your input. Or, if you could point me to any articles addressing the issue, that would be great, too.

Thanks,

Lisa Morgan