[RWP] ReaAccess 2.0? Some thoughts

[Indigo]

There is a Cockos forum where users list their wanted features, and if 
enough ask for the same thing, in time their wants get addressed.
There are all kinds of features that were added from the feature wanted 
list already, so I think the answer is to make ourselves heard on those 
forums.
You know, when you ask for improved screenreader access, these guys 
don't know what a screenreader does, other than the idea it somehow 
reads the words on the screen.
You need to explain that it's not just words that you want to hear, but 
to be able to read what you need to navigate, for the author to insert 
tool tips into graphic icons, for standard menus to open, for edit 
values to appear at the arrow keys, where new values can be typed in, 
specific changes  like that, instead of just pleasse increase 
screenreader access.
I had the experience of writing to the author, Robert Walker,  of the 
Fractal Tunesmithy program, that generates fractal clusters of notes, 
kinda pretty stuff, and mentioned that some parts of that program 
weren't accessible to Wineyes, so he got a demo copy of Wineyes to take 
a look.
He closed his eyes and found out for himself what was missing, and fixed it.
He put every parameter in a vertical column at the tab key, and an edit 
box for each parameter at the arrow keys, and made sure the enter key 
was always recognized, for total access.
Okay, he was unusual, but that is the direction to proceed, to express 
clearly what a screenreader can't get at, and suggest ways to get there.
It might not even require a rewriting of Reaper, since codes like STS 
penetrate deeply into Reaper's structure  and can add almost any feature.
I'm not a programmer myself, but when I wrote to the author of .sts 
extension, at www.standingwatersstudio.com or maybe it's .org; he was 
friendly and said he'd help in any way he could.
I'm currently deeply into learning to run Reason 6, and probably will 
rewire Reason to Reaper; to get a friendlier recording and editing 
environment, but  I'm satisfied with the access I get to Reaper 3.77 on 
32 bit XP, so I don't feel such pressure to get to ReaAccess version 2.
I came out of sequencing on midi hardware of ye olden days, where we had 
practically no editing capability, so I learned to play and record a 
passage again and again until it satisfied me, or, at most, punch in and 
replace a note or two, but, for me, there's already enough midi 
capability now in 32 bit Reaper to make any music I can imagine.
If you work a different way, or you are determined to use Win7 64 for 
its advantages, be the squeaky henge that gets the oil, get known on the 
Reaper forums, express exactly what the screenreader can't get at in 
terms understandable by anyone; and, the changes might get incorporated 
into future versions of Reaper.
Jason reads the forums, and often chats with users about their needs; 
you'll not likely get that close to the program authors in larger 
corporations, or get their support team to have a clue as to how to 
increase access.
Just some thoughts,
Indigo L

On 1/11/2012 9:28 AM, Roland wrote:
> Hello,
> I guess we may have to put up with no further ReaAccess versions, at
> least this is what I learn from recent discussions on this list.
> I sent an email to Cockos a couple of months ago asking for their plans
> on direct accessibility support. They indicated that they have
> screenreader support on their list but - like with so many SW projects -
> this list may be long.
> Nevertheless, I think the only way to support accessibility in the long
> run will be to integrate it directly into the Reaper code.
> On Windows systems there are many ways to do it, Microsoft UI Automation
> beeing probably the most promissing at the moment.
> Exposing all UI elements to UIA would allow all modern screenreaders to
> work without any extra plugins or auxiliary technology.
> Reaper already allows all important actions to be bound to key strokes
> and so this should not create a problem.
> I wonder if a feature request signed by as many active visually impaired
> Reaper users as possible could help in bringing this task a bit closer
> to the top of Cockos's todo list.
> Their reply to my email left me with the impression that they were not
> even aware of ReaAccess and what it does.
> On the other hand screenreader compatibility could help them boost their
> sales, especially for public institutions who are bound to provide
> accessible solutions.
>
> What do you guys think?
> /Roland
>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com