“"I've always been a bit mystified by the popularity of TUIs. To me, the power of the terminal is the streaming model." — acjohnson55, Hacker News”
You know that feeling when a terminal tool looks clean on your screen, but it keeps blinking, moving the cursor, and updating tiny status widgets while you type. If you use a screen reader, that behavior can turn the terminal from a linear conversation into a scrambled mess of timer updates, random history fragments, and lost input focus. The article argues that a lot of terminal teams mistake "text on screen" for accessibility and never test what redraw-heavy UIs actually sound like.
The article splits terminal software into two buckets. First, you have a stream app: it prints text in order, like a receipt printer, so your screen reader can follow time and sequence. Second, you have a grid app: it treats the terminal like a board of cells and keeps repainting pieces of that board wherever state changes. The argument is that screen readers track cursor position and text flow, so when a tool redraws spinners, timers, and history across the board, it scrambles speech, input, and focus. The gemini-cli case study shows that pattern through Ink, which reconciles a React tree into terminal cells instead of just printing lines.
If you build terminal apps, terminal emulators, coding agents, or TUI frameworks, you should read this because it gives you a direct test for accessibility debt in your render loop. If you choose tools for your team, it also helps you ask sharper questions than "does it run in a terminal." It is less useful if you want a code-level fix list or an accessibility standard to implement line by line, because the article is a critique, not a spec.
Yes, if you ship terminal interfaces or depend on them. The critique looks stable enough to take seriously because the article, the Hacker News thread, and opened gemini-cli issues all point to the same failure pattern. Treat it as a design review checklist, not as a finished fix plan, because the strongest rebuttal says the terminal emulator layer also needs work.
Deep-dive insight, Easy and Pro modes, plus action playbooks — the full breakdown is one tap away.