I'm surprised elinks doesn't get more mention whenever text browsers comes up and I wonder why. I prefer it over the others.

It doesn't work for me for quite a while now (for up to a year), even with recent versions from git [0]. My preliminary guess is that's because Google renders each result with <div> (block element) inside an <a> tag. I didn't have any extra spare time to test that further (and report) though, so I simply ditched Google and just went with duck.com from that point.

[0] https://github.com/tats/w3m

Also works with elinks.

Indeed.

What? w3m is resulting in the same thing for me. No actual links to what pops up. Sometimes links to some videos.

Compatibility with screen readers that blind people use.

Moreover, fuck Google and non standard practices in general.

Lynx is not a screen reader. (In fact, it's considerably less accessible to blind users than a typical desktop browser -- as a console application, it has no way to provide accessibility data to a screen reader.)

A screen reader is a tool like JAWS or VoiceOver which interacts with desktop software (including web browsers like Chrome or Safari) to provide information about what the user is interacting with.

>as a console application, it has no way to provide accessibility data to a screen reader.)

FFS, you had console screen readers in Linux since forever.

And even OpenbSD, with yasr. It works fine with speech-dispatcher.

Less accesible? Maybe in your limited world, but this is "Hacker" "News".

Well, I guess the new IT generations are even less aware of TTS systems since 1998 or so.