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.
124 results found
-
Add 360 image/video support to the new Captivate
360 image/video capabilities have become increasingly more important for me to create 360 tour walkthroughs for team members that are not near physical locations. It is the next best thing to being there.
1 vote -
Integration of fonts.adobe.com for font selection
Please integrate the font selection of adobe fonts. As in CPC the fonts from font.adobe.com shall be usable in the font selection.
So the company CI must be fully applicable.
Of course when publishing a SCORM it needs to be implemented in the user view too, without the need to have the font installed at clients devices.
1 vote -
Multiple failure captions
Give back the multiple Failure captions for questions with multiple attempts. It used to be 3 in all older versions, but I wouldn't mind more than 3.
Since the captions are now states in a multistate object. But is impossible to add states to this object and even if that was possible, there is no way to address that object with an interaction, since it is an embedded object without ID.
Look at this workflow which I recently demonstrated for a user. The workflow with the failure captions works also in a responsive project with Fluid Boxes, but not in…1 vote -
Don't gray-out buttons when not disabled
When a UI button has grayed-out text, the assumption is that the button is disabled and not able to be clicked. The states button is grayed out by default and yet it's still clickable. This does not conform to the expected use of this UI design. Don't gray out a button that is clickable.
1 vote
- Don't see your idea?