Closed vadi2 closed 3 months ago
Thanks for reminding this issue!
How / where can blind users help this go forward?
I've updated the ticket with the items I know off the top of my head.
Here are some free screen reading softwares for those who want to help, but don't have any yet:
Um, how will our own text-to-speech efforts mesh/clash with anything done in this direction. Though I suppose that that is only part of any accessibility objectives...
Don't be confused just because both are called "text-to-speech" - they are completely seperate things.
Do you want Mudlet to read out some arbitrary text for you? Call Lua function readText("Test text here") and be done with it. That is a nice function, I just made up from my mind. Not what this issue discusses. I also see no clashes (other than the confusion from having the same name)
This issue is about people who can't read properly or at all, and need their computers to read any and all text out loud, so they can react accordingly. It starts with finding mudlet.org website and download, doing the installation, starting Mudlet the first time, choosing and connecting to games, etc. (Even though you may argue, they could get help for these one-time steps) Of course, also the game text (all game texts) will be read out to them.
This is not done by Mudlet and not with any special Lua command for each single line, but instead by sophisticated software, which will read out Mudlet texts just like texts from any other program these people would like to use.
What Mudlet needs to do, is make sure it can be read and used as expected. This is the scope here.
Yes, I am not saying it isn't a noble idea, {hell I've spent a few years a while back doing Braille transcription*, and in the long-term blindness is, sadly, not unlikely for me} so I'd like to see it done. I do wonder how the two separate TTS parts will cooperate but that was all I was commenting on. OTOH TinTin++ with a 40-cell braille-terminal may be a more comfortable option for those totally without sight; whereas high-contrast, large fonts/features and somewhat atypical colours can all help those with different visual impairments...
* ironically I can read Braille - but only by sight, not by touch...
OK, good. Not sure about the details of the other issue. Seems like #1188 tackles that and still gets upgrades regularly despite its age.
Here are a few related forum posts with additional info about the main issue here from recent years:
Here is current survey on screenreader userbase: https://webaim.org/projects/screenreadersurvey7/ edit: 2021 version available at https://webaim.org/projects/screenreadersurvey9/
I'll get the mentioned PR through at some point, promise :laughing:
Brief summary of issue / Description of requested feature:
Mudlet should support the Linux/macOS/Windows accessibility features for blind users.
Steps to reproduce the issue / Reasons for adding feature:
Mudlet is very popular in some games and blind users are locked out from the Mudlet communities there, which make great scripts offer support for other players.
Error output / Expected result of feature
* [ ] Mudlet's consoles should work with the popular screenreader applications for Linux/macOS/Windows - in practice this means reporting information to Qt's Accessibility framework which will in turns interface with audio engines for us. * [ ] tab order in all of Mudlets windows needs to be sane
Extra information, such as Mudlet version, operating system and ideas for how to solve / implement:
confirm all this. Additional to the tasks i would say
thats the three main issues i see for blind users.
@chrys87 Caret mode has since been added to the main window, would you like to check it out?
Brief summary of issue / Description of requested feature:
Mudlet should support the Linux/macOS/Windows accessibility features for blind users.
Steps to reproduce the issue / Reasons for adding feature:
Mudlet is very popular in some games and blind users are locked out from the Mudlet communities there, which make great scripts offer support for other players.
Error output / Expected result of feature
Extra information, such as Mudlet version, operating system and ideas for how to solve / implement:
Check Mudlet out with https://accessibilityinsights.io/docs/en/windows/overview