Actually at this point I'm only worried about just the built in
controls and it seems that the only control that is really giving me
a problem is the editfields (the first app I am working on is really
simple) I wonder if the issue is that controls with no 'labels' are
going to be problematic. I'll have to dig into the UA docs on the
apple site and see what I might need to do. Probably I should look
for tickets in the feedback system or make some.
Thanks
Sam D
On Feb 21, 2007, at 12:08 PM, Greg Kraus wrote:
> 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...
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
