Skip to main content
Known Participant
February 1, 2016
Question

Keyboard focus hijacked by PowerPoint background

  • February 1, 2016
  • 3 replies
  • 219 views

When I test my project for keyboard accessibility, the focus is overridden by elements in the PowerPoint that was imported.  The PowerPoint was only meant to serve as the background for the Captivate project  and I don't want to be able to tab to all of those elements buried in the graphics.  It seems that the PowerPoint is interfering in that I cannot tab to important objects like rollover areas and buttons.  Is there a way to navigate through and have the PowerPoint ignored?

    This topic has been closed for replies.

    3 replies

    Dart4444Author
    Known Participant
    February 1, 2016

    Thanks Lilibiri and Erik. The problem with just copying the ppt slides in as flat backgrounds is that I would lose the animation and the ability to edit relatively easily. (and it's also the 11th hour)  I have set tab order where necessary except where it is not possible. If the keyboard focus won't go to the object at all, it doesn't matter what order I put them in.  If anyone knows a way to "unlink keyboard focus" for PPT, I would love to know how...

    Erik Lord
    Inspiring
    February 1, 2016

    These may help:

    Captivate 9 Tab Order - Error #2046

    (a little old but may be helpful)

    I Came, I Saw, I Learned...: Adobe Captivate 7: Tab Order

    Otherwise, you could not import the PPT...and just copy all the PPT screen elements and paste them into the project itself...which breaks the need for a PPT connection...which could be good or bad depending on whether you prefer to not edit the PPT itself for future updates.

    Lilybiri
    Legend
    February 1, 2016

    Interesting, didn't know that. I never use an imported PPT as start for an eLearning project, too much limitations. I can only suggest to use indeed graphics from the PPT as backgrounds, not let CP convert each PPT-slide into a movie slide. If there are animations you would have issues with HTML output as well, just FYI.