WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [Athen]Accessibility of Adobe Connect player/pods

for

From: Howard Kramer
Date: Dec 10, 2012 1:07PM

Hi Andrew,

I tried JAWS with a few different browsers. I'll try the tips you mentioned
below and let you know what happens.

Thanks,
Howard

On Mon, Dec 10, 2012 at 1:02 PM, Andrew Kirkpatrick < <EMAIL REMOVED> >wrote:

> Howard,
> The first question that I have is what browser you're using to view the
> recordings. The player is Flash-based and there are challenges getting
> focus into the player on some browsers. That still works best with IE.
> Once you have focus in the Connect recording player window, then you can
> use the keyboard shortcuts.
>
> It seems like there may be an issue with the new Event Overlay area - it
> isn't responding as the other pods are, so appears to be blocking the use
> of the Ctrl+F6 shortcut. If you tab a couple of times to get the focus
> past this item then Ctrl+F6 works as expected (at least it does for me).
> You mentioned Ctrl+F8 also, which doesn't do much in a recording because
> there are no context menus in the recording interface's pods for this
> shortcut to open.
>
> I wasn't able to reproduce an issue with the "p" shortcut not correctly
> toggling the play/pause button, except when the focus was on a text input
> area and in that case the "p" was entered into the control, which I believe
> is the correct behavior. Can you provide steps to reproduce?
>
> The slider to the right of the play/pause button operates with the
> right/left arrow and home/end keys. Like the "p" key, these shortcuts may
> run into difficulties with JAWS grabbing the keystrokes (e.g. for next
> paragraph or next/previous character). If you can provide steps to
> reproduce what you are finding, that would help us. It is worth knowing
> that at least for JAWS the keyboard pass-through is insert+3 so if "p"
> isn't working and then you hit "insert+3" followed by "p" and it does, then
> we at least know why it is happening.
>
> I saw one other comment that the closed captioning wasn't able to be read
> by a JAWS user, and that is true. The captions are hidden from AT, but the
> caption pod does allow you to export a transcript of the event's
> captioning, which may be easier to read for a deaf-blind user.
>
> We'll follow up with the Connect team to make sure that we have bugs
> logged for any reproducible issues, and will add more if other issues are
> identified/clarified.
>
> Thanks,
> AWK
>
> Andrew Kirkpatrick
> Group Product Manager, Accessibility
> Adobe Systems
>
> <EMAIL REMOVED>
> http://twitter.com/awkawk
> http://blogs.adobe.com/accessibility
>
>
>