[Rwp] seeking advice: general tips and suggestions for a c++ developer who wants to make an accessible plugin

[Hadi Rezaee]

Thank you Jamie, I just forwarded your mail to him, I don't think his 
app has any edit boxes,  but it has lots of sliders and knobs

On 2/5/2015 3:02 AM, James Teh via RWP wrote:
> If it's that inaccessible out of the box, he's using some sort of 
> totally custom GUI toolkit. That means he's going to have to implement 
> accessibility from the ground up himself. This, btw, is one reason 
> it's a really good idea to use standard toolkits. Anyway...
>
> On Windows, he can implement either MSAA or UI Automation. (There's 
> also IAccessible2, but that's not a Microfost standard.) If there are 
> editable text fields that are currently inaccessible, it'll need to be 
> UI Automation (or IAccessible2). You can find Microsoft's 
> accessibility documentation here:
> http://msdn.microsoft.com/accessibility
> On Mac, there's only one accessibility API to choose from 
> (thankfully). Apple's documentation should be pretty easy to find.
>
> Jamie
>
> On 5/02/2015 4:20 AM, Hadi Rezaee via RWP wrote:
>> Well, He didn't mention any of those. should i ask him about that?
>> The plugin is S-Gear, the guitar amp suite. I've tried it and it is 
>> completely inaccessible, but the quality of the software is far more 
>> than guitar rig, or kuassa.
>> It's been months that i'm in contact with the developer, and he's 
>> willing to make his plugin accessible.
>> We started with a keyboard layout, and i suggested something to him, 
>> though It is really hard to suggest a keyboard layout for a guitar 
>> amp suite, since all those things with chain, racks and devices and 
>> such!
>> Now if he manages to implement the keyboard navigation, he needs to 
>> do something so the app talks to the screen readers when the keyboard 
>> focus is on the controls.
>