7 ms·
> 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
by krageon 5y ago
> 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 5y agoIt'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 5y agoI 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 https://news.ycombinator.com/item?id=17683719