MUDLET  [client]
Cross-platform, Lua-scripted, and the client with the most thoroughly documented
screen-reader support in this section.
https://www.mudlet.org/
Runs on: Windows, macOS, Linux

Capabilities
  Read off each project's own documentation, not measured by us — a client has
  no handshake for us to observe. "unknown" means we looked and did not
  establish it. It never means no.

  screen reader    yes
      https://wiki.mudlet.org/w/Manual:Screen_Readers
  TLS              yes
      https://wiki.mudlet.org/w/Manual:Supported_Protocols
  UTF-8            yes
      https://wiki.mudlet.org/w/Manual:Supported_Protocols
  MCCP             unknown
  GMCP             yes
      https://wiki.mudlet.org/w/Manual:Supported_Protocols
  MSDP             yes
      https://wiki.mudlet.org/w/Manual:Supported_Protocols
  ATCP             yes
      https://wiki.mudlet.org/w/Manual:Supported_Protocols
  MXP              yes
      https://wiki.mudlet.org/w/Manual:Supported_Protocols
  MSP              yes
      https://wiki.mudlet.org/w/Manual:Supported_Protocols
  scripting        yes
      https://github.com/Mudlet/Mudlet

  1 of 10 rows is unknown: we did not find the project's own documentation
  saying either way. A short honest table beats a long guessed one.

Mudlet is a graphical client with a mapper, a package system and a Lua API that
most of its own feature set is written against. It is GPL, actively released,
and the usual recommendation for someone starting on a modern combat MUD.

ACCESSIBILITY

This is the client with the strongest documented case in this section, and it is
worth spelling out what "documented" means here, because it is unusual.

Mudlet has a manual chapter on screen readers, per-operating-system pages naming
Narrator, NVDA and JAWS on Windows, Orca on Linux and VoiceOver on macOS, an
in-client mudlet access on command, and an option to announce incoming game text
through the reader. It also has a setting that advertises screen-reader use to
the server over MTTS, so a game can adapt if it wants to.

It is also candid about where it does not work well: its own Windows page says
JAWS does not read the output window the way other readers do, and recommends
Narrator or NVDA instead. A project that publishes the case where its
accessibility support is impractical is giving you better information than one
that publishes a tick.

WHERE THE TABLE SAYS UNKNOWN

MCCP. Mudlet's source implements MCCP v1 and v2, but the manual's
supported-protocols page does not list it, and this section's rule is that a
capability claim cites the project's own documentation. Reading a constant out
of a header is not the same act, so the cell says unknown.

NOTE ON ENCODING

Mudlet's default server-data encoding is ASCII rather than UTF-8, and CHARSET
negotiation arrived in 4.10. If a game's text comes out wrong on a fresh
profile, that setting is the first place to look.

See also
  Blightmud — /reference/clients/blightmud
  TinTin++ — /reference/clients/tintin
  GMCP — /reference/protocols/gmcp
  How to connect — /reference/connecting