@Mayana After mulling it over, I think I'll let this one sit rather than clogging up mailboxes (will definitely apologise if there's further correspondence though).

These things happen, and based on my own experiences on that side of the press/dev relationship, it's a lot easier to laugh than take offence at this sort of stuff.

Just sent a Spanish news site an email thanking them for their article because Italian audiences are hard for me to reach and am now feeling like a toolbag.

I'd personalised everything *except* the part mentioning foreign language stuff >_<

@Mayana No rush! It's very late here and I'm about to disappear and get some sleep. If it runs and is playable for you, I hope you find it interesting!

@Mayana Not really. For mechanics that are more or less equivalent to a single verb point and click adventure, one button and two axes are all you really need. For VR, it's nice to just have one button to press when you want to do something and to control everything else with the orientation of your head. That means it can be controlled with old one button joysticks, foot pedals, etc. etc. etc.

@Mayana It's intentionally a very simple and minimalist presentation. I'd imagine that most games have graphics and UI cluttering things up in a way that makes it harder for screen readers to parse.

@Mayana
Interesting. I'm not sure what tools people saying "just put it on the clipboard" were using - I discounted it immediately because it wasn't compatible with my needs.
If you want to try OCR, a typical object description screenshot looks like this image

@Mayana There are a lot of little whys that individually don't mean much, but together add up to this constraint being specifically interesting, compelling, and worthwhile to me. Broadly speaking though, simple controls are good controls, and fewer inputs means it can run in more places with less fiddling.

Two buttons is a concession I made very begrudgingly. Two axis + one button was the original intention :D

@Mayana Currently, the on-screen text shows a title and a description. Both of those change when you are facing an object, with the title fading in first, followed by the description.

A shortcut to skip text breaks my two axis + two button design constraint, but it's definitely something I'm willing to consider.

@Mayana Right now, the engine has support for mouse, keyboard, and joystick input for turning. There's no walking, just interacting with doors or paths to move to a new scene. The game has a compass and a vertical orientation indicator. No typing - input is limited to two axes, an interact button, and a button for displaying inventory.

@Mayana That's the one I care most about (and from my research sounds like the one who'd benefit most from being targeted) ^_^

@Mayana No I'm making my own engine :)

Look like that plugin doesn't have support for any Linux screen readers, so that'd immediately rule it out for me.

@Mayana I've read this one, and my own experiences agree with the takeaway that working with these concerns in mind from the outset means less effort than trying to retrofit new input/output systems later in a project.

@Mayana Thanks! I'll add that to my list of links.

The thing I'm working on is a text-based experience with analogue controls. There's a 3D world around you that you can turn around in, but instead of seeing it, you are given descriptive text of what's in front of you.

My current plan is to find or write a cross platform F/OSS library that I can use to communicate with existing screen readers on users computers (installed screen readers will be set up how users like them).