![]() ![]() An error window which you don't see unless you select it specifically. For instance, it splits everything up into multiple windows, an input window, an output windo. However some of the things which was set were good ideas. It has many limitations mostly because it appears it's creator only made a version enough so that it would work and then abandoned it with no updates or improvements. It was a mud client made especially with blind and partially sighted users in mind. There is a client out there made for the blind called V.I.P mud. If I can make a suggestion if it is possible. Like i'd do jaws curser then move up and down and all it would say over and over is "graphic 471, graphic 512, graphic 225" this is all it reads to me. After that all jaws picks up is a bunch of random graphics that I don't understand. It all was only announced as it was scrolled up. ![]() ![]() However once more I was not able to use any jaws methods to read this page again. Again my screen reader began reading the initial welcome screen to the achaea mud giving the options at the bottom to type 1 to make a new character and so on. When it did work I was able to re-read the instructions and type out what was told to connect to achaea. I couldn't read anything on the screen with invisible curser because it was fixing itself on my applications running behind it. In fact this is what happened when I opened mudlet later after closing it. when navigating with it going off into other applications that are on your screen is very common. It's boundries are more anything that's visible on the screen. This is not a good way to rely on however as invisible curser isn't bound to one application on the screen. I had to use "invisible curser" to read anything. However simple navigation didn't work neither did jaws curser. That it's mudlet for screen readers and the version.Įverything is read on the screen but I tried to read back on what it said to begin using mudlet. AT the moment I have jaws read to me the titles at the top. ![]() I have installed it onto my laptop with a vista operating system using jaws version 12.0. I hope my input will help you to fine tune it easier. I'm a blind user trying out this new screen reader accessible mudlet.įirst can I say I appreciate all your efforts to even think of making this possible and I thank you very much. Mudlet GUI will not need to be used except for the options dialogues. Triggers, aliases and keys will be fully editable via the command console. (jaws aware text editor opens to write the trigger script) New trigger "bar", regex, "^asdf$", lineDelta=2, filter=true (jaws aware text editor opens to write the alias script) (jaws aware text editor opens to edit and save the script) You get a screen reader readable command console and a game text console. This can be done quickly and it's got most value for power users. I'm thinking about adding a console interface. I was trying to use something to the effect of: ^.(? it gives me the every occurance of the capital letters everywhere not just in my prompt.I'll add this after Christmas in order to get it into 2.0 final if I get enough support from the blind community. Valid upper letters are N E S W U D (cardinal indicators) and the valid lowercase letters are e w only (diagonal indicators) What I want to capture is the list of directions where each direction begins with an uppercase letter and may or may not contain a lower case letter (in case of diagonals only). I'm hoping to come up with an elegant solution to The thing is it seems really hard to do without being overly repetitive in my search. I play a mud using mudlet and wish to use Perl regex to capture some input from my prompt. ![]()
0 Comments
Leave a Reply. |