Hey folks, sorry for the recent radio silence. I decided that if I was going to work on games, then I really needed to run Windows as my primary OS. So I bought and installed a second hard drive, installed Windows, and have been slowly migrating over. Don’t worry, the Linux version isn’t going anywhere.

I’ve tracked down what’s going on, and it is a bit hairy. Essentially, strings of 325 characters and fewer speak fine under NVDA, while anything larger doesn’t. This issue is further complicated by the fact that Onslaught is the tip of a larger ecosystem–godot-tts, godot-accessibility and tts-rs–so I can’t just fix the issue in Onslaught and call it a day.

I have today earmarked to install the other screen readers Tolk supports and see if this bug happens there. I’ll probably end up slicing larger strings into 300-character strings and submitting them to Tolk separately, but what remains to be determined is whether I only need to do this for NVDA, or for all screen readers.

Thanks for your patience.

So the speech for the tutorial works well in the newest build, including direction announcing. The string limit problem might be apparent in the tutorial string that mentions hyperjumps, it cuts off.

dialog: Asteroids only explode if they're small. Larger asteroids fragment into 2 medium asteroids. Each medium asteroid fragments into 2 small asteroids. This asteroid will break into pieces when shot. Look out for flying fragments! Use T to learn how many targets are left. Use a hyperjump, Downto...

Thanks!

Aww, crap. Tolk is just giving me lots of grief for such a simple library. Maybe I’ll look into how to talk to the screen readers directly, though that’ll take some work. In the meantime, I’ll keep digging. Maybe there’s another workaround.

OK, think I have a fix for this. Unfortunately it’s in an upstream library, so I’ll have to wait for them to merge my changes. Hopefully that’ll be quick.

Thanks a bunch for the report.