@fluffy @cinerion Basically, it's intended as a fully audio-centric desktop interface built on top of #Emacs, and since people have spent decades integrating everything they can into Emacs... it can do a lot.

https://emacspeak.sourceforge.net/

For listening to music Speechd-el (https://github.com/brailcom/speechd-el) would probably be better as it can be used braille-only... but I don't know braille and quickest turnaround would be achieved via simply shifting to audio.

#Emacspeak #Accessibility #SpeechdEl

@astrid @a @tiskaan @starshine And #accessibility.

A lot of #GUI frameworks don't include anything for accessibility and even for those that do, how pleasant it is to use varies wildly.

Even a shitty #CLI can be adapted for use in #Emacs, which has actually-decent accessibility through projects like #Emacspeak & #SpeechdEl.

Providing an #RPC interface also works for that.

@dekkzz76 @wolf480pl @nytpu Not that much, once you've got the UI design skills you're most of the way there.

It just requires that you actually care about differing needs & preferences.

Which brings me to another annoyance. Anything other than the major #GUI frameworks like #Gtk, #Qt & its derivatives? No #accessibility built-in whatsoever.

The next best thing is #Emacs because #Emacspeak & #SpeechdEl mean your Emacs UI can be made accessible (at least to some folks) for free.

@devinprater Failing #GUI, #Emacs might provide a usable interface through #Emacspeak (https://emacspeak.sourceforge.net/) or #SpeechdEl (https://github.com/brailcom/speechd-el), the latter which claims to actively support braille displays whereas the former intends to be an "audio desktop" per its own self-description.