It's #saturday, so I'm back at it again, working on this last critical bit of #accessibility for #signet.
Today I started by using my screen reader with the file manager. It has a tree view. What does it say as you navigate throughout the tree or expand/collapse items? Now I know.
Of course my file manager is #OpenSource but unfortunately it uses GTK, not QT. So the code probably won't be very useful to peruse.
If anyone knows anyone who has done QT accessibility work, please connect us. 🙏
I found a QT tree demo app, but I'm not sure if it is compatible with screen readers. Still, it might be a reasonable code base to start tinkering with to better understand how things fit together. Plus, I might be able to ask the author questions.
I'll probably spend at least a little time exploring this to see if it might help.
Hopefully they don't force me to use some weird IDE and build toolchain. It's really nice to be able to just use vim and Make.
Crap. The demo app uses some propritary IDE which defines the UI in an XML file. 🤮
I can't even get a demo with a privacy email address like sharklasers.com
I guess I can just manually dig through the code to try to match up XML elements with CPP classes, but I have a feeling this is going nowhere fast!
Well, I emailed the author. They have not touched the repo in 5 years, but hopefully they still have access to that email address and will be willing to respond.
In the meantime... once more into the fray
Derp. Turns out the company trying to get my personal info was just going to let me download an open source program with some of their extras bundled with it. Haha, fuck no.
I got the #FOSS version and it compiled the demo just fine and it works acceptably well with a #ScreenReader.
Now to figure out how their code works and determine how it's different from mine. I feel like I have a chance at being able to complete this task someday!
#motivation #programming #GrowNostr
Another tiny step in the right direction: I'm seeing requests to my code come through with the Role AccessibleText, but only when I have the screen reader turned on. And this is being requested of the items in the tree, not the tree itself.
This is good news. The punchline is that it was not returning the correct value for AccessibleText previously and now it is.
The screen reader still isn't reading off the entries of the selected item, but I know I fixed one problem with the code.
