The lack of accessibility of TUIs is not great in general.

I'd much rather terminals emulator provide a webview directly, and maybe use https://webtui.ironclad.sh/ if you really want the look.

I think it makes more sense for a cli to offer a mini webserver instead.

Think `fish_config`, but opened in the terminal directly [0].

[0]: like https://iterm2.com/browser-plugin.html

▲

xwiz 7 hours ago | parent [-]

> The lack of accessibility of TUIs is not great in general.

Interesting. In what ways? I haven't heard anyone express this concern before.

▲

jiehong 6 hours ago | parent [-]

Depending on how the TUI is made, it can be very visual, but lacks structure for a screen reader (unless you stay in the very simple "input field: value" kind of prompt, but even then auto completion is tricky).

Web browsers offer the DOM to tools such as screen readers (OSs offer their own accessibility sdks). Someday perhaps the TUI application could talk to the terminal emulator that would itself talk to the accessibility sdk of the OS and that info would somehow then be accessible.

There was a beginning of discussion at bubble tea[0] about this for example.

[0]: https://github.com/charmbracelet/bubbletea/issues/780

	▲	duskdozer 6 hours ago \| parent \| next [-]
		TUIs seem like they should be well-suited to screen readers, but yeah accessibility is often unfortunately far down the list on average project priorities.
	▲	BoredomIsFun 4 hours ago \| parent \| prev [-]
		TUIs sadly have become niche tech, and accessibility is rarely a concern for niche things.