| ▲ | ryao 2 days ago |
| I wonder to what extent visually disabled internet users are affected by this, since I can imagine at least some of them using lynx with an on-screen reader for a terminal emulator. |
|
| ▲ | duskwuff 16 hours ago | parent | next [-] |
| Not to any meaningful degree. Lynx (or other terminal-based browsers) would be an extraordinarily poor choice of browser for a non-sighted user, as it lays text out visually in the terminal (e.g. using color and indentation to distinguish between types of text) and does not provide accessibility cues. Those users are much better served by standard GUI web browsers. |
|
| ▲ | bitpush a day ago | parent | prev [-] |
| What's the advantage of using lynx as opposed to Chrome/Safari and using the read aloud features? |
| |
| ▲ | ryao a day ago | parent [-] | | Ask someone who is visually impaired. I know that they historically use browsers that do not support JavaScript. I also am acquainted with one developer who uses software for reading his terminal outloud, although I never asked the specifics of what he uses for web browsing or IRC for that matter. I do know that he loves the iPhone. That said, I just found this post by a blind person who uses Lynx and complained about it the last time Google broke Lynx support: https://blind.guru/blog/2019-11-25-endofgoogle.html | | |
| ▲ | tdeck 19 hours ago | parent [-] | | That may have been true decades ago but I think this is pretty marginal these days. All the Blind people I have talked to use mainstream browsers. GUI browsers actually provide more metadata to screen readers than something like Lynx can, and they actually work with websites people need to access. |
|
|