FlorianI've been a little quiet about this for the last week or two but I'm currently in a place where I'm relatively certain I can actually pull it off.
Last year, the #Ableton Live 12 software became ... pretty accessible. First-party #accessibility, particularly in a tool like this, is practically unheard of, so that made a bunch of Waves. (pun somewhat intended).
One of the big gaps that existed, and still exists, is working with so-called Max4Live devices, as well as VST plugins that have a large amount of parameters. Ableton doesn't currently expose these properly to screen readers, and hasn't for over a year now. I'm sure they'll get around to it one day, but I think I can get there faster.
One of my current Patreon projects is a tool I'm calling Enableton, which fixes both of these issues as well as I can fix them.
If this'd be of use to you, have a look over at https://patreon.com/zersiax at this and other projects I'm working on :)
Last year, the #Ableton Live 12 software became ... pretty accessible. First-party #accessibility, particularly in a tool like this, is practically unheard of, so that made a bunch of Waves. (pun somewhat intended).
One of the big gaps that existed, and still exists, is working with so-called Max4Live devices, as well as VST plugins that have a large amount of parameters. Ableton doesn't currently expose these properly to screen readers, and hasn't for over a year now. I'm sure they'll get around to it one day, but I think I can get there faster.
One of my current Patreon projects is a tool I'm calling Enableton, which fixes both of these issues as well as I can fix them.
If this'd be of use to you, have a look over at https://patreon.com/zersiax at this and other projects I'm working on :)