i found out a way to activate the cheats.
I'll chime in and say that you don't necessarily have to start a new game each time, but you can also load in a current save and go through the same process to activate the cheat menu. So long as a game has started, the cheat menu can be accessed.
In terms of the minigame interface: I am glad that you've brought this issue to my attention as I have always had accessibility as a lingering thought in my mind when working on the user-interface for the game, especially when we migrated from the ActionScript of the Flash version to the JavaScript version we have now. Both
@Gedan and
@Leykoss have done great work on making the UI function and I've just been adding bits and bobs and a lot of polish along the way.
So far, my main focus in the interface work is to make sure everything looks pretty, functions properly, and is easy to understand and use for the player. We've had some hiccups through the process, but I think the UI is currently in a good spot, with plenty of customizable options for the player to change to meet their own personal needs. There are options to change the layout, adjust the visibility for certain elements, toggle animations and changing the interface color scheme. There have been considerations for keyboard-only players with the assigned keybinds, as well as a couple options for touchscreen-device players, and there may be more options for other control configurations in the future, where necessary.
With respect to screen readers, I know there have been a few mentions of this, even in the Flash days (past topics can be found
here,
here and
here), so it has always been a concern of mine. I think now we can confidently say that the "JS port is done," we can move on to taking suggestions for a better screen reader experience. I would recommend starting a new topic either in this forum, the
Ideas forum, or the
Bug Reports forum, and title it appropriately. In that topic, just list any grievances you may have with how TiTS works with the screen reader; what doesn't work or is impossible to decipher, what works well, what needs work, what is confusing or unnecessary, and any suggestions for a better playing experience. Hopefully, over time, those issues can be addressed.
I remember that when I initially conceptualized the JS interface, I wanted it to easily navigate around using the Tab key like the usual controls for the web browser, but I think once button tooltips were implemented, then full-on keyboard keybinds, that functionality was phased out in favor of it performing other actions. So tabbing between different elements might be the only no-go at the moment.
Currently, I have other priorities to focus on, and I think we have a couple more UI components planned to implement, but once those are addressed, I think I'll try to do a comprehensive accessibility pass over the UI and see how compatible I can make it for screen readers. It will take some time, but hopefully in the near future, you'll get something that is a lot more comfortable to play. In the meantime, topics like this will definitely help!