I've played with it some. If the control is a standard OS X control VoiceOver and other OS X assistive technologies will automatically interact with it and be able to read it. If your control is a non-standard control (and I don't know how all of RB's controls are seen by OS X - as standard or non-standard) you have to make some API calls to define how your control interacts with the accessibility features of OS X. Depending on the complexity of your control, the task can be easy to extremely difficult. There's quite a bit of documentation on it at Apple's Developer site.
The short answer is that if your control is not working with VoiceOver, you are going to have to program additional functionality into your control. I've looked at making a more robust set of accessible controls within RB, but time has eluded me thus far. Maybe soon though... Greg --- Sam DeVore <[EMAIL PROTECTED]> wrote: > So I recently was working with some blind clients > and some existing > realbasic apps and I was having some issues with > getting VoiceOver to > give meaningful communication to the user for some > controls. Has > anyone had any experience with getting this stuff > working and are > there any resources that anyone could point me to. > Or am I walking > down a new road (which I have a hard time believing) > > Sam D > _______________________________________________ > Unsubscribe or switch delivery mode: > <http://www.realsoftware.com/support/listmanager/> > > Search the archives: > <http://support.realsoftware.com/listarchives/lists.html> > _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives: <http://support.realsoftware.com/listarchives/lists.html>
