I’m working on a new OGS client (not meant to be a promo, but Tenuki: a new iOS OGS client ), and I’m starting to think about what it would mean to better serve blind and visually impaired players.
I already understand best practices around generally making software accessible to screen readers (and I’m already hard at work on supporting iOS-level dynamic text sizing for folks with visual impairments who still have some sight). I imagine the main Go-specific input mechanism needed is supporting plaintext input for typing moves as coordinates (as OGS does), but I’m mostly curious what a maximally-accessible audio interface to ‘reading’ the goban itself would be, as a game-specific problem.
In addition to reading out individual moves as your opponent makes them, do you want the ability to have the whole move history read out to you (and if so, would that include captured stones as well, or just placements)? A line-by-line reading of each stone that’s currently on the board? A different audio format entirely? I imagine requirements may also be somewhat different for live games vs correspondence, since in correspondence games you’re less likely to already have the whole boardstate in your head.
Generally curious for any thoughts people have for whom this is directly relevant — I know what you think would be helpful is far more impactful than me as a random sighted person.
Ironically, I had difficulty pulling up anything in forum history via official search, but some useful threads I ended up finding via reddit:
The GH issue has by far the most detailed technical info, to the point that (while I’d absolutely love to hear more opinions if people have them!) I’m also more than satisfied that gives me most of what I need.
Was just about to share this one! I am not visually impaired myself, but I thought Kujiu’s ideas of keyboard navigation and making the color/position screen-readable were well thought out.