WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: questions about captivate

for

Number of posts in this thread: 4 (In chronological order)

From: Vy Pham
Date: Tue, Mar 20 2012 6:12PM
Subject: questions about captivate
No previous message | Next message →

Hello,

Does anybody know whom I should contact at Adobe regarding Captivate?
I have a friend who has some questions regarding Captivate and
accessibility.
Thank you so much.

From: John Foliot
Date: Tue, Mar 20 2012 6:36PM
Subject: Re: questions about captivate
← Previous message | Next message →

Hi Vy

I'm fairly certain Andrew Kirkpatrick will respond here, but should this slip his radar then ping me directly tomorrow and I will forward the request if you like

JF

Sent from my Samsung Epic™ 4G Touch

-------- Original message --------
Subject: [WebAIM] questions about captivate
From: Vy Pham < = EMAIL ADDRESS REMOVED = >
To: = EMAIL ADDRESS REMOVED =
CC:

Hello,

Does anybody know whom I should contact at Adobe regarding Captivate?
I have a friend who has some questions regarding Captivate and
accessibility.
Thank you so much.

From: John E Brandt
Date: Wed, Mar 21 2012 8:45AM
Subject: Re: questions about captivate
← Previous message | Next message →

Andrew Kirkpatrick is the Accessibility Guy at Adobe. He monitors this list,
but if you want to reach out to him first, his e-mail is = EMAIL ADDRESS REMOVED =


~j

John E. Brandt
www.jebswebs.com
= EMAIL ADDRESS REMOVED =
207-622-7937
Augusta, Maine, USA

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Vy Pham
Sent: Tuesday, March 20, 2012 8:13 PM
To: = EMAIL ADDRESS REMOVED =
Subject: [WebAIM] questions about captivate

Hello,

Does anybody know whom I should contact at Adobe regarding Captivate?
I have a friend who has some questions regarding Captivate and
accessibility.
Thank you so much.

From: Vy Pham
Date: Wed, Mar 21 2012 10:48AM
Subject: Re: questions about captivate
← Previous message | No next message

John,

Thank you. My friend had already tried to contact Andrew couple weeks
ago with her questions, but never got a response. I am pasting the
questions here, could you please help us to bring to Andrew's
attention?
Your help is greatly appreciated.
***: Andrew,
Thank you for your help with this tabbing issue in Adobe Captivate
5.5. The fix was a huge help.

I have a few additional questions about Captivate 5.5, and I am hoping
you can help me, or direct me to someone I can contact directly. We
are trying our best to make our Captivate Presentation Section 508
Accessible, but we have run into some challenges after adding the TOC.
More specifically:

1. I am able to tab to each item in the TOC, but my contact at the VA
office cannot. She is forced to use the up and down arrow to navigate
the TOC items.
2. When navigating the TOC, we are required to Down Arrow twice to
move to the next item.
3. If you use the Down Arrow to Navigate the TOC, focus does not stay
in the TOC, but picks up text from the slides, then skips back and
forth between slide content and the TOC.
4. When I Tab through items in the TOC, I hear the slide name, then a
blank tab. This blank tab is the bookmark for that slide. Is there a
way to add a descriptive label to that Bookmark?
5. Is there a way to label the “Unlabeled button” in the top left hand
corner of TOC? This is the little yellow star.
6. I am required to tab all the way through the TOC to get to the
bottom navigation bar. Is there a work around for this? Our AT users
need access to that bar right away, and get to it easily. Moving the
navigation to the top did not help, because they still had to go all
the way through the TOC to get back to it. Perhaps there is a
keystroke to access the navigation?
7. The Navigation has blank tabs as I tab through. Can these be
eliminated these extra tabs, or properly label them?
8. Is there a way to apply JAWS keystrokes to Captivate functions?
Like a Hot Key to access the Navigation?
9. I cannot access links located on the slide without tabbing all the
way through the TOC first. This is not logical reading order.
10. The way we navigate to read each slide is as follows: 1) choose
the item from the TOC, 2) Select ENTER, 3) Select CTRL+HOME to access
the slide content, 4) use the down arrow to read the slide. Is this
the correct process? Is there another process for Screen Readers that
we should be using?
a. After going through this process (above) to read slide content,
JAWS first reads: “Unlabeled button”, “Slide Title”, First slide
title, “Duration”, “Status” before it starts to read the Slide
Content. How can I eliminate all of this extra content being read by
JAWS, and focus right on the slide content?
11. Is there a way to apply a Skip Navigation to my TOC?
12. Can I manually adjust the tab order to my preference? (I heard
there is a third party widget for this, is that correct?)
13. When Captivate asks me if I want to resume where I left off, that
menu is not accessible with JAWS. Is there anything I can do about
that?

With all of these Accessibility issues, we are trying to figure out if
this is due to the way we programmed it, or if this is the way
Captivate operates? Is the TOC itself not Accessible? We have not had
this kind of trouble when we eliminate the TOC.

If it is easier to set up a meeting, that would be helpful to me as well.


On 3/21/12, John E Brandt < = EMAIL ADDRESS REMOVED = > wrote:
> Andrew Kirkpatrick is the Accessibility Guy at Adobe. He monitors this list,
> but if you want to reach out to him first, his e-mail is = EMAIL ADDRESS REMOVED =
>
>
> ~j
>
> John E. Brandt
> www.jebswebs.com
> = EMAIL ADDRESS REMOVED =
> 207-622-7937
> Augusta, Maine, USA
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Vy Pham
> Sent: Tuesday, March 20, 2012 8:13 PM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [WebAIM] questions about captivate
>
> Hello,
>
> Does anybody know whom I should contact at Adobe regarding Captivate?
> I have a friend who has some questions regarding Captivate and
> accessibility.
> Thank you so much.
>