Hello, thanks again for creating this project. I'm a blind gamer interested in playing various non-Steam games on my Steam Deck, and I expect this driver will be invaluable in that regard.
One fairly immediate problem I noticed is that items in lists don't have correct accessible names. IOW, when running the NVDA screen reader and arrowing through the list containing driver status, settings, etc. along with the lists of axis and buttons, what gets spoken seems to be the class name of the page model rather than the label text.
This is a fairly common problem in UWP/XAML apps. I'd rather not set up a VS dev environment on my Steam Deck, but I did a bit of research hoping to make fixing this easier. And if it's possible to test the XAML UI without having to compile/run it on the Steam Deck itself, I'm happy to try a few things out here. This page makes it seem like the key is the AutomationProperties.Name property.
I think that if you set it to the text of each list item label, including text descriptions of buttons/axis where graphics are used, that might be enough. I'm happy to test any PRs to confirm that it does in fact work and no other changes are needed.
Hello, thanks again for creating this project. I'm a blind gamer interested in playing various non-Steam games on my Steam Deck, and I expect this driver will be invaluable in that regard.
One fairly immediate problem I noticed is that items in lists don't have correct accessible names. IOW, when running the NVDA screen reader and arrowing through the list containing driver status, settings, etc. along with the lists of axis and buttons, what gets spoken seems to be the class name of the page model rather than the label text.
This is a fairly common problem in UWP/XAML apps. I'd rather not set up a VS dev environment on my Steam Deck, but I did a bit of research hoping to make fixing this easier. And if it's possible to test the XAML UI without having to compile/run it on the Steam Deck itself, I'm happy to try a few things out here. This page makes it seem like the key is the
AutomationProperties.Name
property.I think that if you set it to the text of each list item label, including text descriptions of buttons/axis where graphics are used, that might be enough. I'm happy to test any PRs to confirm that it does in fact work and no other changes are needed.
Thanks again.