Check out the blogs I wrote about using the QSPs, your project demonstrates the same issues I described.

If this is a non-responsive project, publish as rescalable HTML.

From pedagogical viewpoint: give more control to the learner. let them take decisions to skip things, to take a different way through the lesson. Do not impose a linear sequence. That will make the playbar totally superfluous. It is rather easy to add a custom buttons to mute the audio, to show/hide a TOC etc.

Since you plan to have several modules, do not forget to create a solid theme: font and color choice, master slides object styles and skin.  For free navigation choosing a TOC in overlay is a better choice than he playbar.

Greg, playbar is needed to start the project since it is paused On Enter of the first slide.  I didn’t dare to write a lot more… Project is based on a QSP, and hasn’t taken out what needs to be done when you add audio. Blogged about it:

http://blog.lilybiri.com/tips-adding-audio-to-qsp-slides-ready-to-go-slides

That is the reason for the Continue problem…

Naturally – you can expect a wide range of viewpoints on such things. Take these opinions as only that. Ultimately, you need to consider your own target audience.

A few thoughts from my angle…

1. Narration – not a fan of text to speech. As a learner, I tune out real fast when the robots and their lack of enthusiasm start talking to me. I think it is important to maintain a human element in eLearning whenever possible. Maybe take time to record yourself.
2. Narration – I would suggest an ‘option’ to enable/disable the narration. Like Lieve, I appreciate narration, but in the case of robot speech – I would rather not be forced to listen to it and would just as soon read for myself. Also on subsequent visits, a learner may not want to listen again. That would go for human speech as well.
3. Navigation – I think you could remove the playbar since you have your own navigation built-in. Agree with Lieve, that a pause of sorts is not needed. The learner has already clicked enough. I clicked the play button in this thread, the play button forced upon us, the play button on the play bar, and finally the begin button on your first slide.
4. Navigation – I would consider finding a consistent placement and look to your navigation. There was a lot of different button placements, sizes, and colors. It took me a while to notice the ‘Next’ button on the second to last slide. It sort of blended in with surroundings.
5. Related to both narration and navigation – at the end when I click on continue… That is what I expect to happen. Instead I was forced to listen to the robot. Clicking the continue button again did not help.
6. I appreciate the inclusion of interaction from the learner to click through the steps of the process. I think this is where you can get Captivate to truly shine.