100 Screen Reader Support resources for MUD players

Implement a 'SET MAP OFF' command that replaces visual ASCII maps with a text-based list of exits and nearby landmarks to prevent screen reader gibberish.

Create a combat toggle that removes flavor text (e.g., 'The sword whistles through the air') and only outputs essential data like 'You hit the orc for 10 damage'.

Use Generic Mud Communication Protocol (GMCP) to send health, mana, and stamina updates out-of-band so clients can process them without interrupting the main text flow.

Format room descriptions to always place the Room Title first, followed by Exits, then the Description, and finally Mobs/Items to allow quick navigation.

Modify the inventory command to group identical items (e.g., 'a stack of 20 arrows') rather than listing each item on a new line.

Ensure every communication channel uses a unique, consistent bracketed prefix like [Auction] or [Guild] at the very start of the line for easy regex filtering.

Ensure every discrete message or prompt ends with a newline character (\n) to force screen readers to process the buffer and speak the line immediately.

Allow players to define their own prompt strings, including the ability to remove visual separators like pipes (|) or brackets that clutter speech.

Provide a command to display only the current target's health status, reducing the need to scan the entire room for combat progress.

Include a setting to disable the echoing of player commands back to the terminal, preventing the screen reader from speaking the command the user just typed.

Utilize the 'Speak' plugin for MUSHclient which uses SAPI or screen reader APIs (NVDA/JAWS) to read incoming text without manual window focus.

Enable the 'Screen Reader' option in Mudlet preferences to improve how the main console buffer exposes text to assistive technology.

Write regex triggers to gag (hide) common environmental spam like 'The wind howls' or 'A bird chirps' to keep the speech buffer clear for vital info.

Script the redirection of chat channels to a hidden buffer or secondary window that the screen reader only accesses on a specific keybind.

Set up high-priority triggers for critical events like 'You are stunned!' to interrupt the current speech queue and alert the player immediately.

Use Lua or VBScript to scrape health and mana from the prompt and store them as variables for use in custom audio alerts.

Create aliases for common paths (e.g., 'run to bank') to minimize the number of manual directional commands the user must hear read back.

Configure client hotkeys to scroll through command history without the screen reader re-reading the entire input line every time a key is pressed.

Hardcode connection strings and passwords into the client to bypass the login prompts which are often formatted with non-accessible ASCII art.

For low-vision users, use high-contrast color triggers (e.g., bright yellow text on black background) for keywords like 'Exits' or 'Enemy'.

Implement server-side MSP triggers that tell the client to play specific WAV or MP3 files for combat hits, misses, and spell effects.

Script a series of beeps that increase in frequency or pitch as a player's health drops below 50%, 25%, and 10%.

Use stereo panning in soundpacks to play exit sounds in the left, right, or center channels based on the direction (West, East, North/South).

Play a distinct 'ding' or mechanical sound when a combat skill or spell cooldown has finished, removing the need to check 'score' or 'skills'.

Trigger a sharp, jarring sound effect when an aggressive mob enters the room to provide an immediate tactical warning.

Use a subtle 'click' sound for successful item pickups or gold loots to confirm the action without reading the text line.

Loop low-volume background sounds (e.g., rain, tavern chatter) that change based on room sector type to provide spatial awareness.

Assign a 'thud' or error sound to common failures like 'You can't go that way' or 'You don't have enough mana'.

Implement a unique, high-quality audio file for leveling up to provide emotional reward that isn't lost in the text stream.

Use the standard PC speaker beep (\a) or a specific notification sound for incoming private messages to ensure they aren't missed.