If you’re here, thanks for taking the time to read this.
It would be awesome to have more accessibility to visually impaired users.
Ideally, this would have two main features:
Ability to have moves read to you out loud, by coordinates
Ability to have feedback to the move you’re going to make. This one could be accomplished through many ways, from allowing people to type in moves to having the point you’re hovering over read out loud to you.
These features could help make this site more available to nearly blind users, and users who have trouble seeing things up close.
It could also provide a potential for setting up blind style games for non-impaired users as well.
Quite a few Twitch streamers use bots that convert chat text, including emotes, to voice audio. These text-to-speech bots seem to be “freely” available. OGS already has all the move information in text; what’s needed is an interface to connect the moves text to one of these bots.
I don’t think using a bot developed for Twitch chats just to get TTS is an efficient use of resources, and it sounds pretty difficult for a visually impaired user to set up as they’d have to sign up for more things or download them, then deal with piping stuff through twitch chat interface.
That said, when I went to work on a custom client to do this (both TTY and interfacing with OGS) I was hit with some logistic issues in that the API documentation is difficult to work with. Even starting with the basics of getting a user authenticated, the information is just incorrect.
Examples: " The OGS OAuth2 system uses password-based authentication but it does not work with a user’s traditional password. You will need to direct the user to generate an Application Specific Password" – False information, a path leading nowhere. If we do searches people seem to think sending the users password directly works (hope you’re encrypting it… at least use https in requests, and good luck getting users to trust 3rd party tools to not store their passwords)
But assuming you know that the password will work, the user will trust your application and you’re encrypting their data the resource listed to request an auth token is “http://online-go.com/oauth2/access_token” (or better than listed would be “httpS://online-go.com/oauth2/access_token”) – which does not exist on the server, or at least responds as if it does not exist. Whether or not you’re trying to use http or https.
Clearly I’ll need to delve the github repo to figure out the API but the docs so far have actually caused me to lose hours of time by referencing them which is not encouraging. Actually it’s even notable that both the documentation AND the browsable REST request at “https://online-go.com/api/” show the same resource that doesn’t appear to exist.
EDIT: Actually, they are not the same resource. One is /access_token (from docs) and the other is /token (from https://online-go.com/api/), but both do report 404 not found.
My github repo should help you to get access to the APIs. For specific requests, there are some named in there, but many are just not documented. Feel free to ask if you encounter some problems on the way.
People are just trying to be helpful, to brainstorm. Twitch is merely An Example.
Obviously, the goal is to make things better, not worse, for the user.
