[RWP] Help make Reaper accessible out of the box

[Scott Chesworth]

Hi Simon,

Thanks for the reminder nudge. That link did the rounds here a while
ago, but hasn't been posted in some time. Checking in on the
discussion thread and number of up votes now, I can say that the
amount of feedback and votes there is pretty good going based on the
amount of active ReaAccess users.

While I don't want to come over as overly negative, a winer, or
anything of the sort, I do question whether a few more votes (which I
suspect is about all you're likely to get at this point) will tip the
balance here. Take a read of what Vic has been posting. It's one of
the best attempts to engage a developer that I've seen in a long, long
time. Everything they need is there (information, motivation, a few
searching questions that drill down to the crux of what the stumbling
blocks might be), yet nada in terms of results. I'm not ungrateful for
the work that has gone into native accessibility so far, and I've no
doubt that the Reaper developers are good guys who just have a lot on
their plate, but equally I'm convinced that it's gonna take more than
a forum thread to spark them into future action. As with Vic, I've had
several ideas on that front, but my emails have largely gone
unanswered.

To be clear, I'm not saying the forum threads should be abandoned, or
that native accessibility is a pointless pursuit, and I'm certainly
not claiming that ReaAccess is the future for anyone, I'm just musing
out loud and wondering what else can realistically be done.

Let's get the discussion flowing. How can we bring ourselves to the
attention of the Reaper developers that accessibility is worthy of
their time and effort in a positive way? I wonder, could a larger
proportion of the mainstream Reaper user base be motivated to make
noise about this somehow? It's a technique I haven't seen used before.
That could be because it's impossible lol.

Have yourselves a badass boxing day...

Scott


On 12/26/14, Simon Jaeger <simon at simonj.me> wrote:
> Hi all,
> There's a forum post up that talks about implementing accessibility into
> Reaper. The link is at the bottom, if you want to skip this preamble. We
> could really use some up votes, some discussion, and possibly some
> developer input about how to better make this happen. If this is
> something you're interested to see, please join the discussion and
> spread the word.
> To be clear, if you use reaper, you should care about this because it
> means native accessibility on Windows and possibly Mac OS, without an
> abandonware plugin, or a plugin at all for that matter. The keyboard
> commands are basically already in place, all we need is for Reaper to
> communicate with screen readers and allow us to better manipulate
> controls from the keyboard.
>
> Here is the link:
> http://forum.cockos.com/project.php?issueid=3888
>
>
> _______________________________________________
> Cavi-discuss mailing list
> Manage your own subscription:
> Cavi-discuss at ciscovision.org
> http://www.ciscovision.org/mailman/listinfo/cavi-discuss
>