I don’t have access to my GitHub account right now, so this will do. What I’ve written below applies to both Hugor and QTads. Luckily, QT has a built-in accessibility API, which works on Windows and Linux. I haven’t tested these interpreters on Linux, as I’m running Windows, but I may end up spinning up a virtual machine to do so.
What Works?
The file dialogue boxes (open, save, and restore) all work well with screen readers. No issues whatsoever. The menu bar is accessible once you know the hotkeys, or can navigate to it using the NVDA screen reader’s object navigation. Pressing alt, which would normally give access to the top layer of the menu bar, does nothing. The preferences and about dialogue boxes are also accessible with screen readers.
What Doesn’t work?
Text input and output are completely unavailable for screen reader users. NVDA’s “speak typed characters” and “speak typed words” settings allow me to know what I’m typing, but unlike Frotz, for example, (which requires an add-on for NVDA, but is nonetheless accessible), I do not know what commands I’m switching between in the command history when using the arrow keys. As for output, there is no way to read the outgoing text from a game, even using NVDA’s object navigation. The elements on-screen are described as “grouping” and “unknown”, with no other information given.