Re: Accessibility

I believe that the accessibility thread was begun by Raman.

I would imagine that audio-based HTML rendering would best be done by
calling an audio-based renderer to look at the output of a
fault-tolerant HTML parser.

Of course, if an entrance URL leads to

     <head><title>Cool Site</title></head>
     <p><a href="/exec/">
     <img ismap src="/index.gif" alt="Use Graphical Browser">

then audio renderers and cataloging robots are out of luck.  If the
provider does not care about that, fine.

However, the provider who is resourceful will find a way to have both
pictures and real anchors on the same robust page.  Less resourceful
providers attempt to size-up the caller and render accordingly.

Providers who do not want to validate their pages might at least
consider checking them in "lynx" as well as in a graphical browser.

Lynx is reasonably up-to-date, and there was progress with tables
between v 2.4 and v 2.5.

Benjamin Franz <> writes:

> To: Ka-Ping Yee <>
> Cc: Chris Serflek <>,,
>         "''" <>
> . . .
> Don't fool yourself. Lynx has been losing market share ever since Mosaic
> came out. My numbers currently put it at around one percent of the market
> - and still falling.
> . . .

Experimental design is a complicated subject.

I'd bet there are individuals working for NetScape who still have
occasion to use "lynx".

                                   -- Bill

Received on Tuesday, 2 July 1996 16:16:45 UTC