If a learner has an assistive device and not a 'keyboard' then how do you address the default captivate instruction of clicking anywhere or pressing y?

I'm interested in what type of e device is being used as well. If it isn't based on keyboard accessibility shortcuts, then, as Rod stated, it should use the mouse related interface instead, and if so - it should work through the button interface.

I agree with Rob on the second statement as well. If your audience is severely restricted in their ability to interact with the project, then it may be in their best interest to investigate a different delivery system for the content. Accessibility is not meant to create problems for the designer and developer, it is meant to ensure the earner gets the content in a manner that best meets their needs.

Could you please explain a little more about what types of devices you are dealing with here?

If the device is a pointing device that works similar to a mouse but designed for use with people that cannot manipulate a mouse, then you should be able to just ensure your content could be completed by a mouse-driven user.

However, when dealing with limitations imposed by disabilities, at some point you may simply have to admit that perhaps a multimedia e-learning course is not going to be the best medium to deliver the information for some learners.