[RWP] Reaper accessibility in general [was changing tempo in reaper.]

[clarence griffin]

so at this point, reaper still doesn't work on the mac? is that what I am understanding?

Thanks.

GF
On May 24, 2010, at 8:05 PM, Scott Chesworth wrote:

> Jamie, to my knowledge the VO API is the only way to talk to it, think
> you're right.
> 
> Re your earlier points about Reaper having an equal starting point of
> accessibility, I'd still say that the access is more consistent on the
> Mac. The FX window for starters seems to be neater, with aplicable
> labels being announced as soon as you land in an edit area, plus the
> layout of that window in particular is more apparent for those who
> care to learn such things with VO's navigation. Quite a few dialogs
> behave more consistently too, there's less extraneous jabbering going
> on when navigating down the table in bigger dialogs like preferences.
> In any case, it all means nothing if nobody can figure out a way to
> apply the ReaAccess setup to VO. Another slightly hazy possibility
> might be to output to the system voice for announcements in the way
> that the QuicKeys Logic scripts do that are making the rounds at the
> moment, but in my experience that method turns out to be clunky at
> best for the end user.
> 
> Scott
> 
> On 5/24/10, James Teh <jamie at jantrid.net> wrote:
>> On 25/05/2010 8:28 AM, Jayson Smith wrote:
>>> I have no idea if this is worth anything in the current circumstances,
>>> but the developer of the Qwitter Twitter client developed a Python
>>> module called Accessible Output. It is designed to communicate with a
>>> screen reader, I think it supports JFW, Wineyes, NVDA, probably SA, and
>>> if it can't find any screen reader it will speak using SAPI. Not sure
>>> how Braille works.
>> Braille works the same way in Accessible Output. ReaAccess already does
>> this using its own code; i.e. it "speaks" to each of the different
>> screen readers using the API provided by each screen reader. ReaAccess
>> could in theory do the same thing for Braille. However, my point was
>> that doing this means that any new screen reader has to be specifically
>> supported, whereas using accessibility APIs allows for a standard
>> implementation. Also, I think this is the only way on Mac, as I don't
>> think there is a way to "speak" to VoiceOver, though I could well be wrong.
>> 
>> Jamie
>> 
>> --
>> James Teh
>> Email/MSN Messenger/Jabber: jamie at jantrid.net
>> Web site: http://www.jantrid.net/
>> Twitter: jcsteh
>> 
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>> 
> 
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com