Re: Survey about digital accessibility evaluation and monitoring practices

On 06/05/2023 22:45, Guy Hickling wrote:
> Karen, if we are right in thinking you are using the Lynx browser, then
> that will be the source of your troubles - it is a very old tool and was
> never updated to take on JavaScript, which so many websites use today. Many
> websites cannot be used at all without that enabled! I understand the
> eLinks text browser can use JavaScript, but I've heard that not all
> JavaScript scripts work with it, in which case there will still be a
> problem. If you confirm what tools you are using, and why, we may be able
> to suggest options.
> 

Lynx renders on the fly and doesn't create a standard document object 
model.  I think that elinks may be the same, but it uses some heuristics 
to cope with common document/browser object manipulation idioms. I've 
only used lynx, not elinks.

I believe quite a lot of blind users, especially those not in a 
corporate environment where someone else is paying for JAWS, use lynx, 
although I don't have any detailed statistics.

I used Lynx for a long time, although I am sighted.  It used to work 
fast and well with pages that were actually worth reading, but 
eventually too many sites broke on it.  It does require that the page be 
structured as a document, preferably with good structural markup, not as 
a report generator program that reads the actual content as JSON, as is 
the case for many sites these days. (I'd assume the same is true of elinks.)

(I think Lynx was the first W3C browser.)

Received on Saturday, 6 May 2023 22:34:58 UTC