I’m really, really sorry but I still don’t quite understand what you mean here. Could you explain in a bit more detail what you’re doing and how it’s working.
How is the voice over system reading the log output? Do you highlight it and get it to read everything? Does it do this automatically? Is it just the case that the log output is just too large and there’s too much text for the voice reader to keep up with? It’s certainly the case that for anything beyond super trivial and slow code, the log prints out too fast to read, so it just flows past quickly like a river of text.
How might we get the voice over system to stop speaking? What do other systems with long fast flowing log systems do? Do you have any advice on what we could specifically do to make things better when working with a screen reader with respect to the logs?
I’m unable to reproduce this here. Visually the button is dimmed until a file is selected, then it becomes activated. How might I reproduce this with a screen reader?
This is unfortunately out of my control. The voice over functionality is provided by the GUI system (Qt) and so it’s not something I have any real ability to fix. Has it always been sluggish with voice over or did a previous version work fine? If so, could you point me to which version worked well?