Web clients can be made accessible, but no one's actually done this yet, except for Bedlam's which works only with windows 8 narrator. If you provide telnet access, you're probably at least marginally accessible. I personally only use one: it assigns a prompt (the most recent line to begin with status: ) to a variable, hiding it from normal output, and making it readable with a hotkey. Depending on skill level, aliases and triggers can be involved. Recording myself mudding is on my to do list, so that I can point at just how fast it really is. I've not heard of anyone using braille for mudding. The bridging API, built into VipMud and accessed via a plugin in Mushclient, fixes this. The screen readers have no way of telling that the mud output window is special and don't automatically read it. The mud clients are calling the screen readers directly via a bridge, which is different for each screen reader. NVDA works only with Mushclient atm, without some groundwork, and the plugin is called Mushreader. Screen reader doesn't matter to the mud designer, except that someone could test using NVDA because it's, like, free. NVDA is gaining in popularity, and I recently switched from Jaws after 10 years. There are 4 windows screen readers that are prominent: Jaws, Window-Eyes, Hal, and NVDA. Mushclient is 100% accessible but most blind people have trouble with it for some reason. Vipmud is becoming the most popular client for the blind, is non-free, and I hate it. Did someone remove my post? Lol, I wrote a miniature essay on this subject, but I guess it failed to post or something.
0 kommentar(er)
