MUSHclient: for an accessible, stable and powerful MUDding experience

1. An introduction to MUSHclient and accessibility2. JAWS: primary speech Plugin3. Window Eyes: primary speech Plugin

JAWS is the screen reader I use on a daily basis, and the first plugin to allow JAWS to speak within MUSHclient was written by Tyler from AllInAccess.com. I’d like to thank him for his efforts, my plugin wouldn’t be what it is without his groundwork.

You can Download the tts_jfw plugin here. to install it, follow the instructions on the previous page.

If you get an error during installation saying that the JAWS com API could not be initialised, you’ll need to manually register the DLL file that allows communication between JAWS and MUSHclient. TO do this on Windows XP:

  • navigate to your JAWS “program files” directory, from your start menu’s Programs, Jaws, Explore JAWS submenu.
  • Find the file called “jfwapi.dll” in this folder. it is present from at least Jaws 7.0 onward.
  • You need to register this dll file with windows: Right-click and choose “open with”. If “Microsoft C register server” is not in the list of programs, click “browse”. You’re looking for the file called “RegSvr32.exe” - in Windows Xp, it is located in %windir%\system32.
  • If you have registered the file successfully, you should now be able to use the JAWS plugin successfully within MUSHclient.

If you have any questions, comments, critiques, complaints or queries about the Plugin, please leave a comment. Any updates will be reflected here, and although I don’t MUD all that often I will try to implement any suggestions.

Jump to:

This entry was posted on Saturday, March 7th, 2009 at 11:59 pm and is filed under software. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

One Response to “MUSHclient: for an accessible, stable and powerful MUDding experience”

  1. alex Says:
    May 7th, 2010 at 8:05 pm

    in mush client if you set a trigger for * and put the output to tts_stop /n then you can have a VERY functional reader for MUDS without using a screenreader like jaws or even nvda…however because you will sometimes miss a tell from friends etc. while playing like this, it is important to have a channel history (standard) so you can replay messages sent by friends.etc.

    So to clarify what I am saying is that the TTS_sapi plugin works fine alone, ive been playing mushs like this for awhile now…but you need that trigger to make the output non-spammy. Make sure you set the output to command though and NOT world…or the trigger will crash the client with spammed commands. Also only the first 3 checkboxes should be checked, leave the others all blank.

    I am currently (after completing the simple * trigger) in the process of making/discovering a trigger than now eliminates all the silly characters you dont need read like brackets and vertical lines…please look forward to these fully functional mush 4.51 clients with TTS plugins for full functionality MUDS without the use of ANY screenreader (and still plays less spammy than them anyways)…also now working with Dragon to get muds into the abilities of those who cannot type for various reasons.

    Have a good One!!!

    PS the trigger doesnt work yet on any input from the num-pad, but this also will be solved soon!

Leave a Reply