[August 6th: Oh, I found the original tab I had open with the issue I started writing weeks ago! :) (Continuing on from here. )]
Hi!
Was happy to discover this project because I'd had concerns about the negative impact of Godot using non-system UI components had on the editor's accessibility & the accessibility of the games built with it. So it's cool to find a project that aims to improve the situation. :)
I am a be-spectacled developer :) who has become more informed about issues around accessibility in games thanks to people like https://twitter.com/ianhamilton_/ on Twitter.
You mentioned a few things in the README that I thought I might be able to give you some pointers about, so created this issue in the hopes it might be useful.
(Aside: I found the "Why?" section of the README informative & helpful context at both the technical & human level--appreciate you including it.)
[ This is where I got up to last time, what follows are some quotes from the README that I hope to get back to responding to. Also, in one of the Godot issues you mentioned about it potentially being useful having a screen-sharing call with a sighted developer to talk through some of the issues you had encountered, while I can't promise to be able to do this I'd be interested in having a conversation about how we might be able arrange it, because I think what you're working is really important. ]
The interface isn't accessible enough to create games entirely from within the editor
File navigation is confusing.
Yeah it is, and I'm not immediately sure of a fix. This is where I need a sighted person to help me understand the layout of some of these dialogs, along with the behavior of the controls they contain.
This interface was designed for mouse users. I can probably add a hotkey for jumping between major UI elements, but as a blind developer, I don't know the boundaries of these major UI areas. Help with this would be greatly appreciated.
You can also arrow around the UI, though arrow navigation isn't quite as deterministic as tab/shift-tab navigation.
How do I bind an action to a key?
A better workflow for this is welcome, but it took so long to figure out how to reach this dialog
Note that right-clicks are currently a bit broken. I have to manually position the mouse and inject the correct events, but I seem to be picking the wrong coordinates. Sometimes it works, others it doesn't. Help welcome.
[August 6th: Oh, I found the original tab I had open with the issue I started writing weeks ago! :) (Continuing on from here. )]
Hi!
Was happy to discover this project because I'd had concerns about the negative impact of Godot using non-system UI components had on the editor's accessibility & the accessibility of the games built with it. So it's cool to find a project that aims to improve the situation. :)
I am a be-spectacled developer :) who has become more informed about issues around accessibility in games thanks to people like https://twitter.com/ianhamilton_/ on Twitter.
You mentioned a few things in the README that I thought I might be able to give you some pointers about, so created this issue in the hopes it might be useful.
(Aside: I found the "Why?" section of the README informative & helpful context at both the technical & human level--appreciate you including it.)
[ This is where I got up to last time, what follows are some quotes from the README that I hope to get back to responding to. Also, in one of the Godot issues you mentioned about it potentially being useful having a screen-sharing call with a sighted developer to talk through some of the issues you had encountered, while I can't promise to be able to do this I'd be interested in having a conversation about how we might be able arrange it, because I think what you're working is really important. ]