Skip to main content
Known Participant
March 15, 2021
Answered

Tab and Shift-Tab in Captivate 2019

  • March 15, 2021
  • 1 reply
  • 1271 views

Hello. I'm struggling with a problem with keyboard accessibility. I'm publishing the project as html5. There are several smartforms used as buttons that I can focus with the tab key on my slide. When i'm on the last smartform the shift-tab should bring me to the smartform before last. But focus jumps out of the slide to focus buttons in the browser (in my case it's Firefox or Chrome).

This last smartform is faded out two seconds bofore the slide ends. Can this be the cause for this strange behaviour?

    This topic has been closed for replies.
    Correct answer RodWard

    Lilybiri is right. It is a form (I've got the german version of Captivate and didn't know the english name). In my case there are several rectangles, that are used as buttons.

    In the settings I checked something like 'keybord tabulator restricted to slide elements' in 'File' - 'Project-informations' - 'Category - Project - Settings for Publishing' (I think that should restrict the tab-Key to the slide). Perhaps there's a similar setting for the shift-tab-Key, that I didn't found yet?

     


    That is the only setting of that type.

    Your issue may be that you are using Shift + Tab and not just the Tab key.

    You may need to provide another way for the learner to reach the next slide, e.g. a Next button for that purpose.

    1 reply

    RodWard
    Community Expert
    Community Expert
    March 15, 2021

    It should be simple to test whether that is the issue.  Just remove the fade out and retest.

    HaijopaiAuthor
    Known Participant
    March 15, 2021

    Thank for the quick response.

    I tested it when the smartform is shown until the end of the slide, but there is no difference. When on the last smartform of the slide the shift-tab activates a button in the browser window, the tab key will jump to the first object in the tab order.

    HaijopaiAuthor
    Known Participant
    March 22, 2021

    Then it's certainly a bug in Captivate!?