Emulator Issues #12014
closed
Screen reader accessibility broken after QT 5.14.1 upgrade, making Dolphin unusable for blind users
0%
Description
What's the problem? Describe what went wrong.
The current development version of Dolphin doesn't seem to expose any accessibility information to the oS (Windows tested, unsure about Linux and Mac OS). This means that screen reading software doesn't work inside the app which makes it unusable for those who rely on it.
What steps will reproduce the problem?
- Download and start a screen reader. The one I recommend is NVDA, which is free and open-source, but Narrator which is built-into Windows 10 will also let you test for this problem (press CTRL+Windows+Enter to toggle it on and off)
- With the screen reader running, start up Dolphin, Press Alt+F to open the file menu and use the arrow keys to navigate.
With the latest version, when moving through the menus and also opening other windows IE for settings, nothing is spoken. With the latest good build listed below, both NVDA and Narrator speak the currently selected option.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Issue present in Dolphin 5.0-11719
Is the issue present in the latest stable version?
No, Dolphin 5.0 works.
If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)
The issue appears to have started with Dolphin 5.0-11655, which upgraded QT to a newer version. The build directly before the QT upgrade, Dolphin 5.0-11653, is read correctly by Screen Readers
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]
What are your PC specifications? (CPU, GPU, Operating System, more)
Windows 10 Version 1903 (OS Build 18362.719), NVDA Version 2019.3.1.
This issue was first reported on a forum for Blind Gamers in this thread:
https://forum.audiogames.net/post/508954/#p508954
Updated by leoetlino about 4 years ago
- Status changed from New to Accepted
- Regression changed from No to Yes
- Relates to usability changed from No to Yes
- Regression start set to 5.0-11655
Updated by MayImilae about 4 years ago
So this is a Qt issue, and not a Dolphin one. We could potentially fix this ourselves (it's all open source), but Qt's issue tracker has many reports of screen readers breaking in 5.14.1, so hopefully Qt will fix it soon! So instead of burning our limited resources on this, I think its best that we wait for the Qt experts to handle it, then bring in their fix. I mean, we're open source, if someone wants to submit a fix and its up to our standards, sure, but Qt is VERY complicated so... that's probably not going to happen.
Even though this is kind of not our bug, I'll leave this open as a "remember to check if Qt has fixed it" kind of issue, as it is definitely a problem that is affecting our users.
Updated by JosJuice over 3 years ago
- Status changed from Accepted to Fixed
- Fixed in set to 5.0-12462
Turns out that this wasn't actually a Qt upstream issue, but rather than issue with how the Dolphin submodule copy of Qt was built. But regardless, it should be fixed with the update to Qt 5.15.0: https://dolphin-emu.org/download/dev/800b2480ecb0d5d0285c6d560fb25f6b96c3b021/