lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lynx-dev LYNX: my email to newspaper re javascript & lynx


From: David Combs
Subject: lynx-dev LYNX: my email to newspaper re javascript & lynx
Date: Tue, 15 Jun 1999 23:19:01 -0700 (PDT)

Here's what I sent to the Christian Science Monitor (you can
get on their mailing-list for free, and then read their
stuff for free -- until you see an article you are REALLY
interested in, and oops, it's in javascript.

Here's my email to them:

------------------------------------------------------------------

I use LYNX as a browser, a text-only browser.

One of your more interesting articles is unaccessable to
me or to anyone else using LYNX.  (Your web/unix/internet guru
will know about LYNX).

I myself am not blind, but LOTS of blind people use LYNX,
because their text-->sound software works far better with
pure text, rather than pictures, etc, via the usual web
browsers, eg netscape and M$'s IE.

So by using things like javascript (or the unrelated
java-language, too) you are BLOCKING OUT ALL BLIND PEOPLE
from some of your articles, seemingly, in this case, one
of the better articles.

---

By the way, I tried your "text only" link, I found that
it had not only fewer articles, but OLDER ones as well.

Here is where I was when I could not get to that
article done via javascript (at the bottom of the thing
I insert here, now):



Information about the current document

Lynx 2.8.2pre.9 (29 May 1999) ([1]development version) - [2]compile time options

File that you are currently viewing
   
   Linkname: The Christian Science Monitor Electronic Edition
        URL: http://www.csmonitor.com/contents.html
    Charset: iso-8859-1 (assumed)
     Server: Netscape-Enterprise/3.5.1
       Date: Wed, 16 Jun 1999 05:51:54 GMT
   Owner(s): None
       size: 107 lines
       mode: normal
   
Link that you currently have selected
   
   Linkname: The Russian-Serb connection
        URL: javascript:OpenWindow();
   


reply via email to

[Prev in Thread] Current Thread [Next in Thread]