Adobe Captivate
Adobe Captivate
Welcome to the Adobe Captivate feedback page. Submit feature requests and bug reports to the Captivate team via this UserVoice page.
Please follow below steps while posting your enhancements & bugs
- Type your enhancements/bugs into the search field or choose from the categories in the sidebar.
- Check if enhancements or bugs submitted by others / upvote if you find similar to yours.
- If your feature idea or issue is not listed, post it.
- Upvote the ideas if you like.
The UserVoice feedback pages are for feature requests and bug reports only. Upload only content that you have permission to use and refrain from posting personal information (e.g. address, phone number, email, or credit card) or abusive content (spam, phishing links, vulgar language, etc.). Tips for submitting useful feedback
UserVoice is a third-party platform for product feedback. Please note that feedback is voluntary, and you give Adobe a right, to use feedback you provide without restrictions.
851 results found
-
Ability to add custom company specific training videos
It would be nice to add company specific video links to the Learn panel on the Welcome screen.
2 votes -
Fixing Quiz continue with "J" in german version.
In the german version of Captivate 12.0.0.2892 continue in Quiz after submit with "J" don't work, but with "Y".
2 votes -
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…
1 vote -
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 -
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 -
[Feature] Extended styling options for buttons in designOption.json
Problem:
Currently, not all styles available in the Captivate GUI can be set via the button’sdesignOption.json.
Examples: gradient inshapeData, inner/outer shadows including position, and certain icon settings do not apply.Suggestion:
Extend the button’sdesignOption.json, so that all styles available in the GUI can be applied.
Additionally, as withcontent_blocksandsmart_widgets, the JSON for buttons should be extended withcustomStyles.1 vote -
[Feature] Filter for custom Design Options
Problem:
The GUI currently displays all stored Design Options.Suggestion:
Add a filter in the Design Options menu to show only custom Design Options, for example.1 vote -
[Feature] Control visibility of Design Options in the GUI
Problem:
All Design Options currently appear automatically in the menu, including those that are only used within other Design Options.Suggestion:
Add a property indesignOption.json(e.g.,visible: false) to control the visibility of a Design Option, so internal options are not shown in the menu.1 vote -
[Bug] Selected tab loses highlight when widget loses focus
When the Tabs widget loses focus, the selected tab is no longer highlighted. The active state should remain visible so users don’t lose orientation.
1 vote -
SCORM Integrity Checks
Publishing to SCORM can be tricky, and sometimes it can be difficult to figure out why a SCORM course is having issues. I propose adding integrity tools that check your project for common setup issues when SCORM is enabled. For example, if you set the setting so that a completion is getting a 90 on the quiz, and your total score does not add up to 90 points within your project, there is a problem. Perhaps you have 3 retries set, but you did not provide a button, set a setting, or have a path for them to retake the…
1 vote -
[Feature] Custom placeholder text and images in `designOption.json`
Problem:
Currently, placeholder text and images in Design Options are fixed. When placing a design option, a default image and Lorem Ipsum text appear.Suggestion:
Allow defining custom placeholder text and images directly in thedesignOption.jsonfor each widget or slide element.{ "tag": "slide-item-image", "placeholder": "placeholder.png", "customStyles": { "all": { "imageContainerStyles": {} } } }Benefit:
- Designers immediately see the expected image size and proportions.
- Placeholder text can indicate the function of the text (“Headline”, “Subtext”, etc.).
- Increases consistency and standardization across slides and projects.1 vote -
Images to States not working
You cant add an image to different states, it allows you to open the upload box then nothing happens when you press load. This means you are left with a solid colour for hover and visited states which doesnt work.
1 vote -
Images to States not working
You cant add an image to different states, it allows you to open the upload box then nothing happens when you press load. This means you are left with a solid colour for hover and visited states which doesnt work.
1 vote -
[Bug] Margin in Tabs widget prevents styling via `designOption.json`
In the Tabs widget, Captivate applies the following CSS rule to an inner container:
.cp-tabs-widget .cp-tabs-container .cp-widget-content-container > div { width: 100%; height: 100%; margin: 10px 0px; }The
margin: 10px 0pxcannot be controlled viadesignOptions.json. Visual styling such as margin or padding should be configurable.1 vote -
[Bug] Inline margin in Tabs widget (cp-content-image)
In the Tabs widget, Captivate injects an inline margin (
margin: 0px 2% 0px 0px) into thecp-content-imageelement at page generation:<div class="cp-content-image" style="box-sizing: border-box; margin: 0px 2% 0px 0px; padding: 0px; flex: 0 1 40%;">...</div>This behavior overrides any margin settings defined in
designOption.json.1 vote -
Improve documentation for design options
The design options concept is the most powerful feature in Captivate 12 and the key to building custom layouts. However, documentation is very limited. It is often unclear which JSON properties are actually supported for each widget, and many entries defined in the JSON are not transformed by Captivate.
Suggested improvement:
- Provide an example.json file for every widget, showing all possible properties (“grammar”) of the design options.
- Especially for more complex widgets (accordion, tabs, carousel, etc.), this would help developers understand what can be customized.
- Include notes for properties that are not yet transformed but are planned…1 vote -
[Feature] Allow renaming of user-defined variables
Currently, user-defined variables can only be renamed in the variable manager if they are not referenced in the project. Variables that are already in use cannot be renamed, which limits flexibility.
Suggested improvement:
Allow renaming of user-defined variables directly in the variable manager, with all references in the project being updated automatically.1 vote -
[Feature] Additional content wrapper for all design objects
Problem:
Currently,div.cp-widget-containerdirectly contains the widget elements.Suggestion:
It is recommended to introduce an additional content wrapper element belowdiv.cp-widget-containerfor all widgets (videos, text, images, quizzes, etc.). This new wrapper should hold the actual content and control its maximum width, while the outer container can still be used for full-width background styling.Benefits:
1. The existingdiv.cp-widget-containercan continue to provide full-width background styling (color, image, etc.), stretching across the entire slide.
2. The new inner wrapper (e.g.,div.cp-widget-container__inner) should hold the actual content and define a maximum content width to center and structure the layout consistently.…1 vote -
[Feature] Wrap VideoCaption and VideoBody in their own container
Caption and Body should be nested in their own parent element for flexible layout, e.g.:
<container-video-grid> <container-video-grid-card> <video></video> <videoText> <videoCaption></videoCaption> <videoBody></videoBody> </videoText> </container-video-grid-card> </container-video-grid>Benefit: Easier layout control, consistent spacing, flexible arrangement of video and text.
1 vote -
[Bug] Remove inline height on page generation
Captivate currently injects a fixed inline height (220px) into Video Grid containers at page generation:
<div id="videoContainer_si78699" class="videoContainer" data-desktop-height="220" automation-id="slidevideo:::container_aspectratio" style="height: 220px; width: 100%;">This prevents proper responsive behavior and overrides custom CSS.
Expected behavior: No fixed inline height should be injected. Instead, the container should default to
height: 100%, so that its size can be fully controlled by parent elements defined in thedesignOption.json.1 vote
- Don't see your idea?