Screen Reader Support checklist for MUDs

Verify that players can toggle off the prompt or switch to a 'brief' version to prevent screen readers from re-reading HP/Mana/Stamina values after every command.

Ensure vital statistics are sent via GMCP (Generic Mud Communication Protocol) so screen reader users can monitor health through client-side overlays rather than main-buffer text.

Check that visual progress bars (e.g., [#####-----]) are replaced with numeric percentages or text when accessibility mode is enabled.

Confirm the server can force a newline after the prompt to ensure screen readers recognize it as a distinct line of text.

Verify that prompts do not appear on the same line as incoming game text, which causes screen readers to skip the prompt or the text.

Implement a mode that compresses combat output into single-line summaries (e.g., 'You hit the goblin for 10 damage' instead of three lines of flavor text).

Ensure every status effect change (stun, poison, haste) generates a unique, searchable text string for client-side audio triggers.

Verify that different types of damage (fire, cold, physical) are explicitly named in text rather than relying on color codes alone.

Provide a command to toggle a round-end summary that aggregates all damage dealt and received into one line.

Ensure the target's health condition (e.g., 'The orc is badly wounded') is sent as a text string at the end of a round.

Verify that visual ASCII maps can be disabled globally or replaced with text-based cardinal direction exits.

Ensure room exits are listed clearly at the end of a room description, formatted as a comma-separated list or vertical list.

Check that items on the ground and NPCs in the room are listed on separate lines rather than in a single paragraph block.

Verify that room titles are distinct and consistently formatted to allow screen reader users to quickly identify their location.

Ensure that decorative borders (e.g., lines of asterisks or dashes) can be disabled via a 'brief' or 'accessible' command.

Ensure every message sent to a chat channel begins with a clear bracketed prefix (e.g., [Global] or [Auction]).

Verify that lists (inventory, score, who) do not rely on multi-column ASCII tables which are unreadable by screen readers.

Check that help files use standard headers and avoid ASCII art diagrams for explaining game mechanics.

Ensure all in-game menus (shops, trainers) allow selection via numeric input rather than requiring visual cursor positioning.

Provide a setting to disable timestamps on communication channels to reduce redundant text for the screen reader.

Create a 'SET ACCESSIBILITY ON' command that automatically applies all screen-reader friendly settings in one step.

Verify that the connection screen and character selection process are purely text-based and free of ASCII art splash screens.

Provide a 'HELP ACCESSIBILITY' file detailing all commands and client-side recommendations for blind players.

Ensure that timing-critical events (e.g., a craft finishing or a cooldown ending) have a unique text string that is never shared with other messages.

Implement an 'ACCBUG' command to allow players to specifically report output that is difficult for screen readers to parse.