The text mode lie: why modern TUIs are a nightmare for accessibility

📝 Discussion Summary (Click to expand)

Key Themes from the discussion

Accessibility gaps in TUIs

"The reality is different. Most modern Text User Interfaces (TUIs) are often more hostile to accessibility than poorly coded graphical interfaces." — gopalv
Utility for remote work and containers

"They are very useful when working on remote servers, VMs and containers. Much much more convenient and robust than, say, X forwarding." — sudosysgen
Criticism of modern, bloated TUIs

"They’re attempts at pretending to have Windows (etc.) GUIs in a terminal." — MBCook

🚀 Project Ideas

Closes the gap highlighted by multiple HN comments about missing accessibility in modern terminal UI frameworks.

Key	Value
Target Audience	TUI developers and maintainers of dev‑tools, IDE agents, and remote CLI apps
Core Feature	Declarative components with built‑in OSC133/ARIA‑style annotations and focus tracking
Tech Stack	TypeScript, Ink (React), Node.js, OSC133 terminal spec
Difficulty	Medium
Monetization	Revenue-ready: Subscription for premium component library & consulting

HN users repeatedly note that “TUIs were supposed to be the simple option. now they're just web apps wearing a terminal costume” and that “the article mentions several TUI programs that rendering in an accessible way for screen readers.” This tool directly addresses that unmet need.
Provides ready‑to‑use accessibility hooks that would let commenters like “Spooky23” see real‑world braille‑compatible TUIs, turning their nostalgia into a practical solution.

A SaaS‑backed remote terminal that streams AI‑assisted coding agents with full clipboard, cursor, and focus accessibility over SSH/Wayland.
Solves the “remote GUI is abysmal” frustration voiced by users who want usable accessibility on headless machines.

Key	Value
Target Audience	Remote developers, especially those using screen readers or braille devices
Core Feature	Integrated clipboard bridge, cursor‑focus sync, and screen‑reader‑friendly output streams
Tech Stack	Rust (Tokio), WebGPU‑enabled web client, WebGL‑free remote rendering, OAuth2 auth
Difficulty	High
Monetization	Revenue-ready: Tiered SaaS (Free tier, Pro $15/mo)

Commenters such as “ulrikrasmussen” expressed “the terminal is just fundamentally the wrong basic abstraction … remote Wayland is not ready” but also saw promise in “waypipe ssh” – this platform would make that workflow accessible.
Aligns with “I’m slowly working on this, trying to figure out what works as I add accessibility to TUIs” – a hosted service removes the friction for hobbyists.

A lightweight rendering engine that attaches structured semantic tags to every UI cell, enabling screen readers to announce changes without extra code.
Gives developers a way to build “reader‑mode” TUIs that output plain‑text descriptors, addressing the accessibility concerns raised by “lynx97”.

Key	Value
Target Audience	Power users and accessibility advocates building TUIs for data‑intensive tools
Core Feature	Automatic emission of ARIA‑style cell annotations and optional plain‑text mode
Tech Stack	Go, Kitty graphics protocol, JSON‑LD schema, CLI wrapper
Difficulty	Medium
Monetization	Hobby

Directly responds to “If you want to improve TUI accessibility, there is really one magic trick… Use the terminal cursor to indicate focus” – the renderer makes that focus explicit and communicable.
HN participants like “gopalv” noted the “Ink Terminal implementation of React” feels like old word‑processor UIs; this project modernizes that approach with semantic intent, making it attractive for both legacy fans and newcomers.