[accessibility-MacOS] sliders no longer work with VoiceOver (FIXED)

[vtsaran]

Sstarting from Reaper 5.0 track sliders, such as Volume, Pan, etc, no longer work with VoiceOver. They are identified as sliders, however, it is no longer possible to change their value.
This is clearly a regression since they used to work in prior versions of Reaper.

Steps to reproduce:
1. Launch VoiceOver screen reader on Mac OS with CMD+F5.
2. Open Reaper 5.0 or higher and insert a few tracks.
3. Using VO navigation keystrokes, CTRL+OPT+arrows, move to one of the tracks and navigate to any of the sliders on it, eg "volume", "pan", etc.
4. Interact with the slider by pressing CTRL+OPT+SHIFT+DownArrow and attempt to change their values with CTRL+OPT+up and down arrows.

Observed result:
VoiceOver reports the same value.

Expected result:
VoiceOver should change the value and report the update to the user.

[Ollie]

The one thing that changed in this regard is probably the new default theme. Does switching to the "Default_4.0" theme fix the issue?

[orgelpfeife]

Originally Posted by Ollie

The one thing that changed in this regard is probably the new default theme. Does switching to the "Default_4.0" theme fix the issue?

unfortunately not. Just switched through all 3 themes, coming with reaper 5. Moving sliders with voice-over is impossible. Hopefully this bug can be fixed soon, because propper mixing without hardware-Controller is nearly impossible right now.

[Justin]

Aha, there was a change in the default mousewheel behavior options, in Preferences / Editing Behavior / Mousewheel. This was an intentional change however we didn't intend for it to break VoiceOver support.

The options to "ignore mousewheel on all faders", "ignore mousewheel on track panel faders", etc, should all be disabled for voiceover compatibility.

We'll fix this workaround requirement for 5.02.

[davideagle]

Excellent, thanks Justin. It is very gratifying to know that Reaper developers seem keen to interact with accessibility related topics. I'm a blind Reaper user on both windows and Mac, having previous used Sonar (until accessibility broke more or less completely a few years ago) and ProTools (which I still use but is nowhere near as flexible as Reaper). Perhaps you are aware of the open source development that is taking place to create better Reaper accessibility through Osara. https://github.com/nvaccess/osara
I look forward to an even more accessible Reaper experience as things progress. Thanks again.