WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Adobe Connect & accessibility

for

From: Mary Stores
Date: Oct 1, 2010 7:48AM

I am guessing the reason that blidn person had issues at sign-up would
be because of a CAPTCHA. The last time I listened to an Adobe Connect
conference there was no accessible CAPTCHA alternative, and I didn't
know about solona.net.

Mary

QuotiFWIW: does that stand for "for what it's worth?" I haven't
encountered that abbreviation, acronym, ro whatever it is until I
subscribed to this list. Eloquence prounces it funny. :)

Mary

ng "E.J. Zufelt" < <EMAIL REMOVED> >:

> FWIW, the use of Adobe Connect for yesterday's a11ySummit is, in
> part, the reason that I did not participate. Not being able to
> participate equitably in the discussion around the presentations
> seemed a little like discrimination (ok a lot like discrimination) to
> me.
>
> Being a lover of irony, and understanding that it is difficult
> (perhaps impossible) to find a robust and accessible web conferencing
> solution I am not as annoyed as I could otherwise be. But I've been
> working around the inaccessibility of Connect (formerly called
> Breeze) for nearly two years, so it is definitely a pet peeve of mine.
>
> Two thumbs down for Adobe Connect accessibility.
>
> HTH,
> Everett Zufelt
> http://zufelt.ca
>
> Follow me on Twitter
> http://twitter.com/ezufelt
>
> View my LinkedIn Profile
> http://www.linkedin.com/in/ezufelt
>
>
>
> On 2010-10-01, at 9:04 AM, <EMAIL REMOVED> wrote:
>
>> When I tested the keyboard/voice control accessibility of Adobe
>> connect for my employers two years ago, my report to them said,
>> "Adobe connect: no accessibility at all. This is somewhat
>> surprising, since Adobe tries hard to be decent with
>> accessibility, so I wonder if further communication with the
>> company would reveal more information. But the help files say
>> nothing."
>>
>> This obviously isn't helpful -- I don't know what it is about
>> Adobe connect that I couldn't use. My guess is that I probably
>> couldn't get into the base controls by voice at all, which
>> meant that I couldn't test to see if anything beyond that initial
>> startup was accessible. I know that my employers did some
>> outreach to Adobe about accessibility, and I'm pretty sure they
>> didn't hear anything.
>>
>> On the other hand, this was two years ago. I would be willing to
>> believe things have changed.
>>
>> -deborah
>>
>>