Text-to-Speech
April 1, 2026
Text-to-Speech
April 1, 2026
Followers: 0 people

I am using the text-to-speech component for an eLearning course and have noticed that some words are mispronounced. When I adjust the spelling phonetically to correct the pronunciation, the changes also appear in the closed captions. Is there a workaround for this?

For example, the word ‘Workqueue’ is mispronounced by the English text-to-speech agent. I’ve attached an image for reference.

All Comments
Sort by:  Most Recent
2026-05-20 18:57:08
2026-05-20 18:57:08

That’s a great question, and you’re not alone in running into this with the new Adobe Captivate. What you’re seeing is expected behavior at the moment. When you use the built-in text-to-speech, Captivate relies on the exact same text source for both the generated audio and the closed captions. So if you adjust a word phonetically to improve pronunciation, that change will also appear in the captions. As of now, there isn’t a built-in way to separate the spoken text from the caption text within the tool. A practical and reliable workaround is to keep the correctly spelled text on your slide so your captions remain accurate, and then handle the audio separately. For example, you could generate or edit the narration outside of Captivate and import it as slide audio. This gives you full control over pronunciation without affecting what learners see in the captions. In some cases, small tweaks like adding spacing or slight punctuation can help the text-to-speech engine pronounce terms more naturally, but that tends to be inconsistent. For now, using custom audio is the safest approach if caption quality is important. Hope this helps. Take care.

Like
()