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.
- or
926 results found
-
[Feature/Bug] Cards Widget: Perspective and mouseover overlay customization
Problem:
- The.flip-card-containerin the global stylesheet uses theperspectiveproperty. This value cannot be adjusted via the GUI or thedesignOption.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 thedesignOption.json.Suggestion:
- Make theperspectivevalue adjustable in both the GUI and thedesignOption.json.
- Allow configuring the color and behavior (show/hide) of the mouseover overlay in the GUI anddesignOption.json.1 vote -
[Bug] Quote Widget ignores styling and lacks clear component references
Problem:
The Quote Widget does not fully respond to styles defined indesignOption.json.Details:
- The containerscontainer-quotes-text,slide-item-quotes-icon-container-1, andslide-item-quotes-icon-container-2ignore custom style definitions and seem to have structural inconsistencies.
- Incontainer-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 withindesignOption.json.
- Several layout properties in the global stylesheet cannot be overridden locally withindesignOption.json.Suggestion:
Document all component names and ensure that each element of the Quote Widget can be fully styled and controlled directly fromdesignOption.json.The internal structure could follow the example of the SVG widget, which allows flexible layout control using either
flexorgrid, depending on the design intent.Problem:
The Quote Widget does not fully respond to styles defined indesignOption.json.Details:
- The containerscontainer-quotes-text,slide-item-quotes-icon-container-1, andslide-item-quotes-icon-container-2ignore custom style definitions and seem to have structural inconsistencies.
- Incontainer-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 withindesignOption.json.
- Several layout properties in the global stylesheet cannot be overridden locally withindesignOption.json.Suggestion:
Document all component names and ensure that each element of the Quote Widget can be fully styled and…1 vote -
[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 -
[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
scrollis available. Addingfixedwould 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
repeatis currently available. Separate control forrepeat-xandrepeat-ywould be useful. -
Background size — Currently only
containandcover, 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 indesignOption.jsonwould 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
scrollis available. Addingfixedwould 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
repeatis currently available. Separate control forrepeat-xandrepeat-ywould be useful. -
Background size — Currently only
containandcover, as well…
1 vote -
Background attachment — Currently only
-
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 -
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 -
Add Slide Video to PPT imported project
Currently cannot add slide video to powerpoint imported project == can add video media but there is playbar built into the video this way, unlike when adding a slide video.
1 vote -
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 -
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 -
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 -
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…
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 -
[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 -
[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
- Don't see your idea?