Links can be made to work accessibly; elinks cannot. Last version of
elinks I used I couldn't find any setting in it to number links.
w3m runs stuff a bit differently but can be blocked by javascript on
sites. The creator of the web is frustrated with the way it turned out
and specifically for accessibility reasons. He wasn't blind from birth
either.
On Thu, 15 Sep 2016, Andre Majorel wrote:
Date: Thu, 15 Sep 2016 04:47:55
From: Andre Majorel <aym-nai...@teaser.fr>
To: debian-user@lists.debian.org
Subject: Re: lynx - not all sites readable
Resent-Date: Thu, 15 Sep 2016 08:48:30 +0000 (UTC)
Resent-From: debian-user@lists.debian.org
On 2016-09-14 17:46 -0400, Henning Follmann wrote:
On Wed, Sep 14, 2016 at 05:06:29PM -0400, Jude DaShiell wrote:
One of these days, I'd like to put a website up and permit only text
browsers like links and lynx and edbrowse full access and either
block all of the graphical browsers or simply cause all of them to
crash.
That is stupid, petty and pretty much a waste of time.
Yes, isn't it wonderful ?
To the OP : both sites (and the links under "Drivers") work with
Elinks as far as I can see.
I must say, it baffles me that Lynx continues to get more
mentions than Elinks, Links and W3m together even though they
render HTML at least as well and usually better that Lynx. Or
have things changed in recent years ?
--
