Skip to main content
D
defaultl4x7czd73snz
Participant
April 20, 2022
Question

Keyboard Accessibility for Captivate Course

  • April 20, 2022
  • 2 replies
  • 285 views

Hello,

I ensured that a course had the accessibility function turned on in the settings when publishing, and when I inspect the buttons with the dev tools, the dev tools say it is focusable. However when trying to use the tab key to tab to a button, nothing happens. Tab key just stays up in the url bar.

This course was originally produced in 2017.

We're on 2019 v. 11.5.553

Has anyone else had this issue?

    This topic has been closed for replies.

    2 replies

    J
    Joseph24124122neai
    Participant
    April 20, 2022

    I am sorry that I  don't have a specific solution to the issue you mention.  However, I have a fundamental question about accessiblity which may play a part in the issue you noted.  My qeustion rises from this senetnece (empasis added).

     

    "Output generated with the Enable Accessibility option is displayed by all supported browsers. However, your output may not be Section 508-compliant unless it is viewed with Internet Explorer. Internet Explorer is the only browser with support for MSAA (Microsoft Active Accessibility)."

     

    From here: https://helpx.adobe.com/captivate/using/creating-accessible-projects.html

    which was last updated January 13th,  2022

     

    What browser are you using?  Has anyone out there tested accessibility of a Captivate module using Edge or Chrome?    Is the sentence above saying one must  to use Internet Explorer for the "enabled accessiblity" elements to be "accessible"? 

     

    Sorry again to ask more questions than provide answers but I hope maybe answering some of these qeustions will be a help. 

     

     

    D
    defaultl4x7czd73snzAuthor
    Participant
    April 20, 2022

    Thanks for the reply. I did not use IE11 because well, it's IE11 lolz. I used Chrome and Edge, but I could try IE11 and see.

    J
    Joseph24124122neai
    Participant
    April 20, 2022

    Gotcha.  You mentioned usign a screen reader which one?  What I am trying to understand is how/if all of the accessiblity pieces (e.g. alt-text, names of buttons, etc.) are accessible to the screen reader when using Chrome and/or Edge with say the JAWS screen reader.

    D
    defaultl4x7czd73snzAuthor
    Participant
    April 20, 2022

    Additionally, I tested with screen reader and the screen reader is able to to access the button. Just doesn't seem to work with the keyboard only. 

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