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

[Scott Chesworth]

Aha, the context menus being accessible is a really good sign. I
should have some working eyes around tomorrow to get through that
authorization window. I've got to get some focus stuff checked for
OSARA, but that shouldn't take long, and this is next on the list.

On 2/4/15, Hadi Rezaee via RWP <rwp at bluegrasspals.com> wrote:
> Hi scott
> Here's the link for his website:
> http://www.scuffhamamps.com/
> His software is free for 15 days, and a small problem is the licensing
> window at the start, which cannot be read by jaws at least.
> After you get rid of that screen, the whole plugin is not accessible,
> with some exceptions!
> first of all, all elements of the app is recognizable by jaws, because
> If you check the virtual cursor, graphics are all over your screen.
> Second, you can use your arrow keys to switch presets, though you need
> to enable the bridging of the reaper, so you get a different window for
> the plugin.
> third, you can kind of right click on the elements  of the app and get
> accessible pop up menus, but since you have no idea what rack in which
> part of the chain you are clicked on, It's hard to do things.
>
> The app has like 5 amps, which are amazingly designed. the high gain
> ones need some tse808 behind them to be able to get that  heavy metal
> sound.
> On 2/4/2015 10:28 PM, Scott Chesworth via RWP wrote:
>> Ok, well I'd say that coming up with a user experience that doesn't
>> involve 500 parameters would be a good start while you're waiting for
>> someone with development knowledge to chime in.
>>
>> I'll download the plug and take a look to see if there's any
>> suggestions I can make. It's a really cool start that this chap is
>> receptive to the idea and that you've got an ongoing dialog.
>>
>> On 2/4/15, Hadi Rezaee via RWP <rwp at bluegrasspals.com> wrote:
>>> Hi Scott
>>> Yeah, you can edit the current amp parameters, their EQ switches and
>>> some other settings with shift+P.
>>> But since the app has a single chain which racks are put on it, other
>>> rack's parameters are scattered around 500 parameters.
>>> but amp parameters are always at a cirtain number!
>>> I do not even know what shall i suggest to him in regards to
>>> accessibility. his plugin is a big one, full of controls and dynamic
>>> racks along a chain. We came in a conclusion for a nice keyboard layout
>>> at least. and it is awesome that he's willing to give this a try;
>>> though, It'd be awesome if some more experience users could help us.
>>>
>>> On 2/4/2015 10:06 PM, Scott Chesworth via RWP wrote:
>>>> Yep, definitely ask him. You might want to hold that thought for a bit
>>>> though in case you get better responses here with other questions to
>>>> ask.
>>>>
>>>> Question for you this time, where's the plugin currently at with
>>>> automation parameters? Can you hit Shift+P on a track with his plugin
>>>> inserted and get at any of the controls that way? If not, that should
>>>> probably be his starting point, as it'll also benefit anybody who uses
>>>> a control surface. That's a way bigger bunch of people than screen
>>>> reader users.
>>>>
>>>> Scott
>>>>
>>>> On 2/4/15, Hadi Rezaee via RWP <rwp at bluegrasspals.com> 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.
>>>>>
>>>>> On 2/4/2015 9:34 PM, Scott Chesworth via RWP wrote:
>>>>>> Is he using any frameworks or libraries? So far as I understand it,
>>>>>> that'll have quite an impact on the approach.
>>>>>>
>>>>>> On 2/4/15, Hadi Rezaee via RWP <rwp at bluegrasspals.com> wrote:
>>>>>>> Hi guys!
>>>>>>>
>>>>>>> There is a developer, who has developed a cross platform plugin,
>>>>>>> (windows and mac), and now he wants to make it accessible to Screen
>>>>>>> Readers. beside keyboard navigation, he wants to know how he could
>>>>>>> expose elements and text to Screen Readers.
>>>>>>> and, His app is in c++.
>>>>>>> If you got any tips or suggestions, or any links. can you please
>>>>>>> contribute, so i forward the mail to him?
>>>>>>>
>>>>>>> If you need more info, let me know.
>>>>>>> Cheers
>>>>>>> Hadi
>>>>>>> _______________________________________________
>>>>>>> RWP mailing list
>>>>>>> RWP at bluegrasspals.com
>>>>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>>>>>
>>>>>> _______________________________________________
>>>>>> RWP mailing list
>>>>>> RWP at bluegrasspals.com
>>>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>>> _______________________________________________
>>>>> RWP mailing list
>>>>> RWP at bluegrasspals.com
>>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>>>
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at bluegrasspals.com
>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at bluegrasspals.com
>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp
>