Requesting accessibility implementation, expose GUI controls to platform specific APIs about vstgui HOT 7 OPEN

Hi @ScottChesworth

Before I ported Surge from VSTGUI to JUCE I took a look at doing this. We decided to port off of VSTGUI for a variety of reasons, but I still have the diffs around I started when I thought I would fork this in myself. I was able to at least get the navigation accessibility tool showing me some basic locations. Didn't get it working though and then we moved off of VSTGUI so didn't invest in finishing it.

surge-synthesizer/vstgui@surge...baconpaul:vstgui:accessibility

I don't know if that's of any help to the team here but didn't want to not mention it.

from vstgui.

Hi @ScottChesworth,
VSTGUI is open source software, in contrast to the JUCE library no one is paid to implement features in the VSTGUI library. Maybe software companies making money with VSTGUI can fund a developer to integrate accessibility into VSTGUI. Best would be to write to these companies and make them aware that they have users requesting this.

from vstgui.

I could do a whip round, try to hustle up some financial support. If anyone can suggest specific companies with commercial products built on VSTGUI as starting points, leads would be much appreciated. So far, I think all of the products I've encountered firsthand have been from indie devs.

from vstgui.

Many (all?) of the Steinberg plugins are built on VSTGUI, and Serum is also still I think, if that helps.

from vstgui.

Gotcha, thanks. If I can find some sponsorship, would you be open to putting more work into that fork you started @baconpaul? Zero pressure of course, just figured it's worth asking seeing as we're here exploring options.

from vstgui.

I'm happy for anyone to take that code and do whatever they want with it but I'm not working on VSTGUI myself in 2023. I have a bunch of other synths to work on (including making them accessible :) )

from vstgui.

Also that fork may be junk. Like I said it was just an initial poke at it.

from vstgui.