[azeirah]

I do think so. Terminal applications tend to be really accessible.

[maccard]

You said accessible, so would you expect terminal applications to work with screen readers for example? What about localisation?

[azeirah]

I did not mean that kind of accessible. I mean easy to get, easy to install, easy to manage, easy to distribute.

[maccard]

apologies then! i dont understand how a tui app is necessarily get-able or installable or distributable. system package managers are more than capable of managing GUI apps, and a GUI can be distributed by uploading a zip to gh releases, just as a TUI app can be.

[krageon]

> would you expect terminal applications to work with screen readers for example

Can you explain to me any way in which they might not, bearing in mind they're basically text.

[riquito]

It's not automatic, any sufficiently complex interface will need to offer some kind of support. E.g. if your widget library offer dialogs, using e.g. ncurses, then TAB shouldn't allow you to flow out of such dialog. If you render graphic elements with special characters (dots, dashes or unusual glyphs), you would need to offer some hints to the screen reader to skip or identify differently that stuff. Just "read them out loud because is text" wouldn't work. It's been a long time since my last complex TUI so I don't know what's there today for accessibility

[maccard]

I did a quick Google for examples, and found this comment [0] on HN which gives some examples.

It being "basically text" doesn't matter; a pdf can be mostly just text but that doesn't mean in any shape or form that it's searchable.

[0] https://news.ycombinator.com/item?id=17683719