933 results found

1. Allow content creators to import .doc or .pdf text to populate a template.

   If there were tags that could be placed into a word document that could call for a slide option in a project template, then the program could auto-populate text and images into predetermined slide options. This would allow for a rapid conversion to Captivate files when receiving only text, image and link content from authors.

   Many of our authors are accustomed to a particular set of procedures for content development. We need a simple method to take the content provided and convert it to a Captivate project.

   If there were <tag>s of some sort that could identify sections of text and their associated images and links to videos or other online content and then populate an appropriate slide template, that would be ideal. Tags could identify other design options as well, for example font style or shape colors or corner radius for buttons. Have a simple library of available tags. Then content creators who do not use Captivate can put in tags that would reduce the amount of time needed for the Captivate content team to fine tune the imported project.

   Ideally, they would also be able to tag specific variables and object names as well. Some of our LMS integration is dependent on button object names and custom variables. These variables could mostly be handled by a custom template though, if that were an option, which it absolutely should be. Then it would just be making sure that the doc or pdf had the appropriate tag for the custom slide template with the appropriate custom variable options.

   If there were tags that could be placed into a word document that could call for a slide option in a project template, then the program could auto-populate text and images into predetermined slide options. This would allow for a rapid conversion to Captivate files when receiving only text, image and link content from authors.

   Many of our authors are accustomed to a particular set of procedures for content development. We need a simple method to take the content provided and convert it to a Captivate project.

   If there were <tag>s of some sort that could identify sections of text… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  1 comment  ·  Import/Export  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Variables and Design Options

   We all understand that Captivate 12 is "built around a template-based authoring approach, designed to streamline project creation with minimal effort." that's just great. And we all want a simple user interface for our content creators who are less technically savvy, which Captivate provides. That does not mean that the content administrators don't still need the ability to have custom templates with variables to integrate properly with their LMS (and in our case LRS). We have government mandated variable time requirements for slide dwell time and total lesson duration. We also have varying pass percentage requirements.

   There are a large number of exchanges that have to happen to make sure that a given user / registration is launched with the appropriate injected values. That means that the variable must be accurate. Those variable should not have to be recreated ever, they should be selectable, custom variables that are options for any new project if they are in the options folder.

   Currently, you have to copy a slide from a 'template project' somewhere on your computer. When you do that, with no apparent specific reason, Captivate creates a new variable. This, of course, breaks the logic and you must go through every slide with variables and make sure that a numerical suffix has not been added when pasting. There is no way to turn this off. Further, you cannot delete these ghost variables that end up being sometimes 50-100 randomly generated variables. You try to delete them, and even though those variables are used NOWHERE in the project, Captivate does not allow you to delete them. It is genuinely frustrating.

   The entire variable and design option architecture is pretty broken. It is 'clunky' at best. I dont even want to think about how many hours I have had to waste fixing logic errors in a program that is supposed to be "designed to streamline project creation with minimal effort."

   In our case, it has been anything but 'streamlined'

   Our dev team is throttled by the Captivate teams decision making process, it is not good.

   We want the simple interface and template, yes.

   We MUST have the ability to create our own custom templates complete with custom variables that do not create a 1000 ghosts.

   We all understand that Captivate 12 is "built around a template-based authoring approach, designed to streamline project creation with minimal effort." that's just great. And we all want a simple user interface for our content creators who are less technically savvy, which Captivate provides. That does not mean that the content administrators don't still need the ability to have custom templates with variables to integrate properly with their LMS (and in our case LRS). We have government mandated variable time requirements for slide dwell time and total lesson duration. We also have varying pass percentage requirements.

   There are a large… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Variables  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. [Feature] Option for automatic display of timeline events (without click)

   Problem:
   In the current Timeline widget, each event must be clicked manually for its associated content (text/image) to appear.
   This interaction pattern is not ideal for all learning scenarios — especially in linear or narrative timelines, repeated clicking can be distracting and offers little didactic value.

   Suggestion:
   Add an option in the Captivate GUI and in the designOption.json to control the behavior:
   - Manual (current behavior): The user clicks each event to reveal its content.
   - Automatic: The content is always visible.
   - For better user experience: The content appears with a smooth fade-in or motion animation when the event enters the viewport.

   Problem:
   In the current Timeline widget, each event must be clicked manually for its associated content (text/image) to appear.
   This interaction pattern is not ideal for all learning scenarios — especially in linear or narrative timelines, repeated clicking can be distracting and offers little didactic value.

   Suggestion:
   Add an option in the Captivate GUI and in the designOption.json to control the behavior:
   - Manual (current behavior): The user clicks each event to reveal its content.
   - Automatic: The content is always visible.
   - For better user experience: The content appears with a smooth fade-in or motion animation when the event… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  1 comment  ·  Timeline Widget  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. [Feature] New Widget for Expandable Single Sections (Disclosure / Details)

   Background:
   On longpages or compact content layouts, there is often a need for expandable single sections for supplementary content such as transcripts, glossaries, or additional information. An accordion widget is overkill for this purpose, as it requires multiple tabs and semantically implies a group behavior.

   Problem:
   - The Accordion widget cannot currently be reduced to a single tab.
   - Using a "pseudo-accordion" with only one panel is semantically incorrect and may negatively impact accessibility and user orientation.
   - There is no dedicated widget to toggle individual content sections, making implementation cumbersome.

   Suggestion:
   A dedicated widget based on the established HTML5 <details>/<summary> pattern or a disclosure element. It should:
   - Toggle a single content block open/closed
   - Optionally scroll automatically
   - Optionally support state persistence
   - Clearly indicate visual states
   - Be configurable via GUI and designOption.json

   Background:
   On longpages or compact content layouts, there is often a need for expandable single sections for supplementary content such as transcripts, glossaries, or additional information. An accordion widget is overkill for this purpose, as it requires multiple tabs and semantically implies a group behavior.

   Problem:
   - The Accordion widget cannot currently be reduced to a single tab.
   - Using a "pseudo-accordion" with only one panel is semantically incorrect and may negatively impact accessibility and user orientation.
   - There is no dedicated widget to toggle individual content sections, making implementation cumbersome.

   Suggestion:
   A dedicated widget based on the established HTML5 … more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  1 comment  ·  Interaction  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. ragesh.c@gds.ey.com

   The new Adobe Captivate version does not allow placing objects in a custom order. It only supports drag-and-drop using predefined templates. For example, if we need to position titles, images, icons, or buttons freely on the slide, this flexibility is missing. Currently, all custom design options are limited, forcing us to use only what Captivate provides.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  1 comment  ·  Design Options   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add checkboxes with Select All or Deselect All when editing Table of Contents

   When creating courses in Captivate, we often have over 100 slides, but we only want our users to have access to maybe 10 in the Table of Contents. In Captivate 12.6, I have to deselect each slide which is obnoxiously time consuming. The "eye" icon action should be replaced with check boxes with "Select All" or "Deselect All" options at the top.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  1 comment  ·  TOC/Playbar   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Bug- Mac Users Have Different Text

   When I create trainings, they work just as expected on Windows but if someone on a Mac opens it the text turns into a different font and is not matching my company branding as I designed it to.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   NeedMoreInfo  ·  3 comments  ·  Application   ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Text Drag and Drop

   I don't use the drag and drop because currently it is only for pictures. Would be nice to have the ability to have learners drag and drop text to other text.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Feature_In_Backlog  ·  2 comments  ·  Drag and Drop Widget  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. [Feature/Bug] Cards Widget: Perspective and mouseover overlay customization

   Problem:
   - The .flip-card-container in the global stylesheet uses the perspective property. This value cannot be adjusted via the GUI or the designOption.json.
   - If no image is set on the front side, a gray mouseover overlay appears. Its color and visibility cannot currently be changed in the GUI or the designOption.json.

   Suggestion:
   - Make the perspective value adjustable in both the GUI and the designOption.json.
   - Allow configuring the color and behavior (show/hide) of the mouseover overlay in the GUI and designOption.json.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Cards Widget  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. [Bug] Quote Widget ignores styling and lacks clear component references

    Problem:
    The Quote Widget does not fully respond to styles defined in designOption.json.

    Details:
    - The containers container-quotes-text, slide-item-quotes-icon-container-1, and slide-item-quotes-icon-container-2 ignore custom style definitions and seem to have structural inconsistencies.
    - In container-quotes-card, there are no documented or discoverable component names (e.g., quoteText, quoteIcon1, quoteIcon2), making it impossible to target, enable, or disable these elements within designOption.json.
    - Several layout properties in the global stylesheet cannot be overridden locally within designOption.json.

    Suggestion:
    Document all component names and ensure that each element of the Quote Widget can be fully styled and controlled directly from designOption.json.

    The internal structure could follow the example of the SVG widget, which allows flexible layout control using either flex or grid, depending on the design intent.

    Problem:
    The Quote Widget does not fully respond to styles defined in designOption.json.

    Details:
    - The containers container-quotes-text, slide-item-quotes-icon-container-1, and slide-item-quotes-icon-container-2 ignore custom style definitions and seem to have structural inconsistencies.
    - In container-quotes-card, there are no documented or discoverable component names (e.g., quoteText, quoteIcon1, quoteIcon2), making it impossible to target, enable, or disable these elements within designOption.json.
    - Several layout properties in the global stylesheet cannot be overridden locally within designOption.json.

    Suggestion:
    Document all component names and ensure that each element of the Quote Widget can be fully styled and… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Quotes    ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. [Feature] Custom CSS as a first step toward an open widget architecture

    Problem:
    Widget styles can currently only be customized via designOptions.json. Many widget structure elements cannot be targeted or modified globally.

    Suggestion:
    Add the ability to include a custom CSS file at the project or theme level. This stylesheet should allow global adjustments and overrides of Captivate’s core CSS.

    In the long term, Captivate could – similar to the Adapt Framework – offer an open widget system, where custom or modified widgets are possible. Custom CSS would be a useful, practical intermediate step that provides immediate benefits and paves the way toward a fully modular architecture.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Design Options   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. [Feature] Extended background image options

    Problem:
    Current background image settings in Captivate are rather limited and don’t fully reflect the flexibility of CSS.

    Suggestion:
    Add support for the following additional background-related properties and options:

    • Background attachment — Currently only scroll is available. Adding fixed would enable simple parallax effects.
    • Background position — Currently only horizontal alignment is supported. Vertical alignment (top, center, bottom) and relative or absolute positioning (percent, pixels) should be possible.
    • Background repeat — Only repeat is currently available. Separate control for repeat-x and repeat-y would be useful.
    • Background size — Currently only contain and cover, as well as Stretch and Original Size are available. Instead of Stretch and Original Size, free scaling via percent or pixel values would be desirable.
    • Background image — Only one image can be defined. Support for multiple layered background images would enable more complex designs.
    • Combined backgrounds — Allow combining background colors, gradients, and images within the same element.

    Additionally:
    Documentation for all supported background-related properties in designOption.json would be very helpful.

    Problem:
    Current background image settings in Captivate are rather limited and don’t fully reflect the flexibility of CSS.

    Suggestion:
    Add support for the following additional background-related properties and options:

    • Background attachment — Currently only scroll is available. Adding fixed would enable simple parallax effects.
    • Background position — Currently only horizontal alignment is supported. Vertical alignment (top, center, bottom) and relative or absolute positioning (percent, pixels) should be possible.
    • Background repeat — Only repeat is currently available. Separate control for repeat-x and repeat-y would be useful.
    • Background size — Currently only contain and cover, as well… more
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Image   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Reply Interaction

    Need a reply interaction to add to custom button instead of using playbar - will use for slide videos added to ppt import projects

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  4 comments  ·  Interaction  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. 13.1 bug

    13.1 bug - Captivate turns black after locking my computer (CTRL + L on Windows). Does not reload or open. Sometimes data is lost due to lack of save prior to blackout.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  1 comment  ·  Application   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. provide better support for xAPI

    When I publish to xAPI using Adobe Captivate (modern and classic), I cannot get it to generate POST statements to my Learning Record Store when I run the content. Spent a lot of time working with my friend Claude to troubleshoot, but no success.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Preview/Publish  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. feedback caption missing

    I have a MCQ slide with multiple answers. If I do not select enough answers, but the ones that I do select are correct, there is no feedback caption shown. It moves straight to the next slide.
    eg.
    my MCQ has 5 possible answers
    of those 5 answers, 3 are correct
    when answering the question, if i only select 1 or 2 correct answers and nothing else, the feedback caption does not show.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  1 comment  ·  Quiz  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Allow you to mute project audio on specific slides

    When I add background audio to the entire project I cannot stop it from playing on slides that have a video or video grid so you get the music and the video audio. The only way to get around this is to remove the background audio completely. Would be nice to add a feature in the audio tab on the slide to stop the music from playing entirely just on that slide.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Feature_In_Backlog  ·  2 comments  ·  Audio  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. ragesh.c@gds.ey.com

    The new Adobe Captivate version lacks the ability to restrict the video seekbar—a key feature for ensuring learner engagement and compliance in eLearning. In many training scenarios, it's important to prevent users from skipping ahead or fast-forwarding through video content. Ideally, the seekbar should be locked until the video has been watched completely. Once the video is fully viewed, users can then be allowed to fast-forward or rewind for review purposes. This functionality was available in Adobe Captivate Classic and is essential for maintaining the integrity of learning paths. Please consider adding this feature to the new version to support structured and effective video-based learning.

    The new Adobe Captivate version lacks the ability to restrict the video seekbar—a key feature for ensuring learner engagement and compliance in eLearning. In many training scenarios, it's important to prevent users from skipping ahead or fast-forwarding through video content. Ideally, the seekbar should be locked until the video has been watched completely. Once the video is fully viewed, users can then be allowed to fast-forward or rewind for review purposes. This functionality was available in Adobe Captivate Classic and is essential for maintaining the integrity of learning paths. Please consider adding this feature to the new version to support… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  2 comments  ·  Video  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. ragesh.c@gds.ey.com

    The new Adobe Captivate version does not support adding custom navigation elements like in the Classic version. Currently, the header and footer only allow limited customization—such as displaying the course name, page number, and TOC. There is no option to globally add essential navigation buttons like Back, Next, Glossary, or Resources across the course design. This limitation significantly impacts the flexibility and user experience of eLearning modules. Please consider reintroducing the ability to create and apply custom navigation players, as available in Adobe Captivate Classic.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Feature_In_Backlog  ·  1 comment  ·  Design Options   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. ragesh.c@gds.ey.com

    The new Adobe Captivate version lacks a critical feature for eLearning: the ability to restrict the Table of Contents (TOC) and Playbar navigation. In effective eLearning design, it's essential to control access to the TOC and the Next button to ensure learners fully complete each slide before progressing. This functionality was available in Adobe Captivate Classic and is a must-have for tracking learner engagement and completion. Please consider reintroducing this restriction feature in future updates.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    NeedMoreInfo  ·  5 comments  ·  TOC/Playbar   ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating