Skip to main content
N
Nickels55
Known Participant
September 15, 2011
Question

Captivate 4 - playback control via keyboard

  • September 15, 2011
  • 1 reply
  • 1126 views

I am looking for a solution to make my Captivate tutorial accessible, which includes the ability to control the playback of the Captivate swf file using the keyboard. The tutorial also contains captions to help our hearing impaired viewers. Is there a way to make the keyboard control the playback on the webpage containing the final swf file?

Any help is greatly appreciated.

    This topic has been closed for replies.

    1 reply

    B
    brightonjon
    Inspiring
    September 18, 2011

    The TAB key should allow users to select all the interactive elements in the browser window, including the playback controls.

    In addition, if you have additional navigation elements (buttons, click boxes) you can set a shortcut key for those in the Properties panel.

    N
    Nickels55Author
    Known Participant
    September 18, 2011

    The issue is actually in the HTML code. The tab key doesn't work on firefox until you are focused on the flash object by clicking on it. This defeats the purpose of keyboard accessibility. In order for the tab key to work when the page loads you need to change the code to window mode of opaque. Then on firefox the flash object is fully accessible. Thanks!

    B
    brightonjon
    Inspiring
    September 18, 2011

    Interesting, it always just works for me, including with Firefox.

    Indeed, I think one of the common moans about Flash objects is that it sometimes steals the TAB focus and won't give it back. There's an article here about that which may help albeit in reverse:

    http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100708/FLASH17

    Have you tried using CTRL-TAB to cycle around the open tabs to see if the Captivate objects picks up the focus next time around?

    Alternatively, have a look at the Javascript focus method. Though a quick look at the default html that Cp produces shows it's already including the focus method, so it sounds like a Firefox bug.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices