“Live preview on Devices” using QR code

Do you have issue with preview using QR code? Is your QR code not giving preview ? No mobile preview using QR code ?

Hey, if you have problem getting “Live preview on Devices” using QR code, Kindly understand this.

Many face problem that their QR got generated and is scanned and even read by mobile BUT no preview!! The reason is explained below.

When you create “Live preview on devices”, the output is created(generated) in your local PC only. Your setup may be such that your mobile can no-way connect to your local PC even thought both (your mobile device as well as PC with captivate) are having internet connection working.

Because your PC is having ip address something like “192.168.1.XYZ” or “192.168.0.xyz” or similar. These address are for intranet, means for local network and can not be accessed directly from internet. Same story is with your mobile. So your mobile can not access your PC output through internet(even though both are having internet connection.)

These both can talk to each other only if they are on the same network (to be exactly: on same local area network).

Consequently, if you want your mobile should show preview by reading QR code, then both should be accessing same router and there by they come on same LAN.

Note: Captivate does give clear message that both PC and mobile device should be on the same intranet, but often we ignore what software says or many could not interpret this message properly.

The post “Live preview on Devices” using QR code appeared first on eLearning.

Two Significant Accessibility Issues with Captivate 2019

Recently the University of Colorado Boulder’s Accessibility and Usability Lab (AUL) identified several issues with our online courses created using Adobe Captivate 2019 ( Though the Instructional Designer (ID), using accessibility best practices with Captivate, can address many of the issues, two significant issues however, were identified that appear to be inherent in Captivate 2019 but were not seen in Captivate 2017 ( projects.  (View a 10 minute YouTube demonstration of the issues)

First Issue: “graphic” repetition

First, when previewing or publishing Captivate 2019 projects as HTML5 using the NVDA or JAWS screen-readers, the word “graphic” continually announces each text or image content layer and/or every 125 characters of the layer.

Not only is this very annoying to screen-reader users it can also lead to misunderstanding the lesson context. During my testing, this occurs in both the JAWS and NVDA screen-readers in IE, FF, and Chrome. When previewing or publishing in CP 2017 as HTML5 the screen content reads as expected.

Second Issue: Repetition of Text Surrounding Links

The second significant issue revolves around the linking feature of captivate when using the Modify Hyperlink Dialog to apply a link to a URL, file, advanced action or other feature. (I’ve only tested URL, and Advanced Actions but the issue was present in both cases)

Captivate 2019

  1. With NVDA and FF the link is announced only at the very end, and more importantly, after the associated text block(s) are repeated multiple times (at least 5 or more times depending on the text and how many links are on the page: the more links, the more times the text blocks are randomly repeated.)

I’ve only identified one practical work-around thus far: break the text apart and define each link as a button with the accessibility name defined as “web link”, for instance. Even then, careful attention must be applied to the layer stacking order.

  1. NVDA and IE11 or NVDA and Chrome do not report the link at all and do not appear in the accessibility tree (Insert plus F7)
  2. U key works for unvisited link, if at the top of the page. If past the link then user can use Shift + U presuming they know a link exists.
  3. V key (visited link) does not work in any browser / screen reader combination.

The post Two Significant Accessibility Issues with Captivate 2019 appeared first on eLearning.

Custom, Accessible Quiz: Development Highlights

I recently posted a showcase – a Custom, Accessible Quiz. This was a shorter, rewritten and rebranded version of a fully customized, yet accessible quiz I created for a client.
In this article I want to share some highlights of the development process. If you haven’t tried it already, it will help to understand the rest of this article if you try out the quiz before reading further. It’s at: elearning.adobe.com/2019/01/custom-accessible-quiz.

Multiple Introductions

Multiple text for introductions overlaid on a single slide.

In the course, there are two possible scenarios in which a learner may start the quiz:

  • A first attempt;
  • Re-taking after a failed attempt.

For both scenarios, I used a single slide to communicate the introduction to the quiz. Structurally, this means that the quiz always starts from a single location. Through experience, I have learned that this simple decision will help to simplify any debugging that might be necessary later as it reduces the number of non-essential branches in the course.

Advanced action showing how cpQuizInfoAttempts is used to determine which text to display.

For both scenarios, I used a single slide to communicate the introduction to the quiz. Structurally, this means that the quiz always starts from a single location. Through experience, I have learned that this simple decision will help to simplify any debugging that might be necessary later as it reduces the number of non-essential branches in the course. To determine which scenario was in play, I used Captivate’s cpQuizInfoAttempts system variable to track whether the quiz had previously been attempted. cpQuizInfoAttempts reports the number of times a quiz has been attempted; If the quiz has not yet been taken, its default value is zero.

Learn more about Captivate’s system variables at: helpx.adobe.com/captivate/using/captivate-variables-list.html.

Custom Options

I created the custom options using Smart Shapes as buttons. Each option has only two states: Normal and Visited.

The highlighted True button for question 1 with its Smart Shape properties visible in the Property Inspector.

In terms of accessibility, this was perhaps one of the trickier areas of the quiz because unlike regular buttons, smart shapes are not automatically accessible. It was therefore necessary to add Accessibility Names to each state.

Quizzing Logic

The quiz contains only accessible question-types: true or false, multiple-choice (pick one, and select all that apply) and fill-in-the-blanks.
I created separate advanced actions to implement the logic for each of these question types, and then saved them as shared actions so that I could reuse the same advanced action for multiple questions containing similar objects.

A shared action
In each question, every option has an advanced action associated with it which defines the following:

  • The score to assign to the option – 10 for the correct answer, 0 otherwise (in most cases. Select all that apply works a little differently).
  • Any options that must be deselected once this specific option is selected (for true or false and pick one question types).
  • The specific variable that should be updated when at least one option has been selected –to indicate that it is time to enable the Submit button.

It’s also worth mentioning that every question slide also has an On Enter advanced action that resets all the options to their Normal state and clears the score from the Submit button before the slide is displayed –-if the quiz is being retaken.

A Little Branching

As I mentioned earlier, through experience, I have learned that it is generally best to limit branching to only when necessary to achieve pedagogical objectives i.e. when distinct structural paths need to be defined. This situation fits that definition in that after the learner has completed the quiz, they are automatically directed along one of two distinct paths:

  • Pass the quiz and go to the course conclusion;
  • Fail the quiz and go back to the beginning of the quiz (to retake it).

So, this was a perfect situation to implement a little branching by creating a conditional advanced action which determined where to direct the learner based on the outcome of the quiz. It did this by determining which Next button and message group to display to the learner on the Quiz results slide.

The Branching View showing the branches from the Test Results slide.

Similar to the introduction, I used On Enter to attach the advanced action to the slide. This is the branch you can see in the image.

The post Custom, Accessible Quiz: Development Highlights appeared first on eLearning.

Close Captioning Tab “box”

Hi everyone,

we have a few keyboard users that would like to be able to more easily see the element that they have tabbed to. They are not visually impaired; this is just a learner preference. I’ve tried a few things but I cannot seem to change the thickness or color of the highlight box. I am using Captivate 2017. Please advise if anyone has any suggestions.

Thank you,


The post Close Captioning Tab “box” appeared first on eLearning.

Converting courses from 2019 back to 2017

I am on a project and we created our eLearning content in Captivate 2019. The client installed 2017 on their machines. How do I move the file from my 2019 version to my 2017 version? We can not reproduce these entire training’s!!

Please help!!

The post Converting courses from 2019 back to 2017 appeared first on eLearning.

High Contrast and 508 Accessiblity

I’m having a problem when my courses are tested for 508 Accessibility in that they are failing the “High Contrast” test.  This is apparently a function built into at least Windows that inverts the colors on the screen (i.e. this page, for example, the white would change to black and the black test would change to white).

Does anyone know if there are settings within Captivate itself that are necessary to make this feature function properly?


The post High Contrast and 508 Accessiblity appeared first on eLearning.

Captivate: if I output to HTML, I have to un-check “Auto Label” box in “Item Accessibility” and enter my own text?

I am trying to create accessible e-Learning. Also, I am required to output my course file in HTML format. HOWEVER, it seems like the auto label feature for accessibility is only applicable for SWF output (FLASH?). Is that TRUE? Will it change eventually in 2017 or 2019 version?


The post Captivate: if I output to HTML, I have to un-check “Auto Label” box in “Item Accessibility” and enter my own text? appeared first on eLearning.

The 360 slide cannot be displayed when I opened the published html file


I love the new 360 slide and VR project features, which can provide an immersive training for my learners, so I start a trial on using the Captivate 2019 and create a blankslide and vr project to have a try on the new feature.

And they worked in the browser tab opened when I clicked the YES to preview after publishing the project into html. However, when I closed the preview window and tried to reopen the index.html, the 360 slide cannot be displayed while the normal slide is functioning (see the below screenshots)

the cannot be displayed 360 slide

the functioning normal slide

Can anyone help in this?

Thanks a million,


The post The 360 slide cannot be displayed when I opened the published html file appeared first on eLearning.