We have four multi-state buttons on a page that the learner must select one to hear a story. I named each button in the accessibility option for the initial state and the visited. After all four buttons have been clicked and all four stories heard, the learner then can click next to advance to the next section of the project. To give an example the first multi-state button is described: Liang Incomplete in the Accessibility tab. Then in the visited state, it is described as Liang Complete. Liang Incomplete is read by the screen reader (Chrome Vox) and then when the user returns to that page and the button has turned to its visited state color, if clicked it still is read as Liang Incomplete. We need this to work,
Is there a way to include a sidecar file such as .dfxp to automate closed caption timing into a video in captivate? I have access to .dfxp files of my script and would love to implement that rather than time every block of cc text.
When publishing to Flash, tab navigation highlights the in-focus item with a yellow highlighted box.
When publishing to HTML5 only, there is no highlight box by default. After unchecking “Hide selection rectangle for slide items in HTML5” in the publishing settings, you get a box, but is a very faint blue. and if your object is a rectangle with a dark border, you cannot determine if you are on that item or not. Even the highlights on the Captivate playbar are quite muted.
1) can the highlight thickness and color be configured to match the Flash implementation?
I’ve got a pretty straight-forward Captivate file with about 140 slides. I have TTS on almost all of the slides. I have closed captioning turned on. I’ve exported it 3 times and on my Mac, I can literally watch it fill in the Word file it creates. It makes about 95 pages of content. Then when it’s “done” the attached is what I get. I have no idea what to do- I really need this file from my Captivate file. Honestly, if I could JUST get the closed captioning part, that would meet my immediate needs. Help is appreciated!
In Captivate 2019, I’m working on my first interactive video project. I have added some overlays and bookmarks. It seems to be working great on the desktop and even iPad. My issue is that it does not seem to be working on the Android platform. The main issue is that the video does not play. I click on the red default play button on the embedded YouTube video and it does not start. It does not play the video at all, however the first overlay appears after the 15 second interval. So the Captivate timeline is starting after clicking on the initial project play button (large grey one), but I can’t get the YouTube to play.
In the browser and iPad seem to work well. Click the larger project play button, then the YouTube video button and the overlays and bookmarks work great.
Is there anything I’m missing or does this new Captivate feature not work on Android tablets?
Please share any insights,
The post Interactive Video in Captivate 2019 not working on Android Tablet appeared first on eLearning.
I started work for an international company, and I’ve been given a project to create a course in 19 languages. I can change the keyboard through Windows, but when I try to import into Captivate I got some boxes and some ? marks.
This is going to be a frequent request here, and if Captivate can’t support, I need to start looking for something that will.
Any help is appreciated!
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.
Recently the University of Colorado Boulder’s Accessibility and Usability Lab (AUL) identified several issues with our online courses created using Adobe Captivate 2019 (126.96.36.1996). 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 (10.0.1.285) 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)
- 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.
- 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)
- 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.
- 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.
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.
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.
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.
I created the custom options using Smart Shapes as buttons. Each option has only two states: Normal and Visited.
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.
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.
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.
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.