Two-Value Slider and screen reader accessibility

We’re working on ensuring accessibility in a plugin.

We have a few two-value sliders. It seems that they are inaccessible to the screen reader, testing with VoiceOver on Mac.

VoiceOver reports:

Two-value slider to set minimum and maximum MIDI note range, You are currently on a slider, inside a group. To start interacting with the slider, press Control-Option-Shift-Down Arrow

I can then get to the Slider but when I try and interact with it, I hit the following assertion in juce_Slider.cpp:
// for a two-value style slider, you should use the getMinValue() and getMaxValue() // methods to get the two values. jassert (style != TwoValueHorizontal && style != TwoValueVertical);

Stack trace:

juce::Slider::Pimpl::getValue() const juce_Slider.cpp:196 juce::Slider::Pimpl::keyPressed(const juce::KeyPress &) juce_Slider.cpp:1057 juce::Slider::keyPressed(const juce::KeyPress &) juce_Slider.cpp:1742 juce::ComponentPeer::handleKeyPress(const juce::KeyPress &) juce_ComponentPeer.cpp:217 juce::ComponentPeer::handleKeyPress(int, wchar_t) juce_ComponentPeer.cpp:191 juce::NSViewComponentPeer::handleKeyEvent(NSEvent *, bool) juce_NSViewComponentPeer_mac.mm:913 juce::NSViewComponentPeer::redirectKeyDown(NSEvent *) juce_NSViewComponentPeer_mac.mm:933 juce::NSViewComponentPeer::sendEventToInputContextOrComponent(NSEvent *) juce_NSViewComponentPeer_mac.mm:1668 juce::JuceNSViewClass::JuceNSViewClass()::'lambda8'(objc_object*, objc_selector*, NSEvent*)::operator()(objc_object*, objc_selector*, NSEvent*) const juce_NSViewComponentPeer_mac.mm:2368 juce::JuceNSViewClass::JuceNSViewClass()::'lambda8'(objc_object*, objc_selector*, NSEvent*)::__invoke(objc_object*, objc_selector*, NSEvent*) juce_NSViewComponentPeer_mac.mm:2355 juce::MessageManager::runDispatchLoop() juce_MessageManager_mac.mm:347 juce::JUCEApplicationBase::main() juce_ApplicationBase.cpp:277 juce::JUCEApplicationBase::main(int, const char **) juce_ApplicationBase.cpp:255 main juce_audio_plugin_client_Standalone.cpp:234

It seems that the issue is that the slider is not aware of it being a two-value slider when navigating with the keyboard and screen reader. It should then contain two controls within the group.

We’re tried hacking it by linking two separate invisible sliders within a group but’s not working well. The slider is already within a group containing an associated label.

Is this a known issue, or are we missing something?

Bump - would be great to get another perspective on this before doing some custom accessibility hackery.