Lynx, Links, and ELinks

Do you have a question? Post it now! No Registration Necessary.  Now with pictures!

Threaded View
I sometimes find my self needing to use a text based browser to perform
work on remote servers.  It seems as though certain websites make
extensive use of javascript in order for me to download files.  Because
of this, updating 3rd party drivers (Nvidia in this case) using a text
based browser was nearly impossible due to javascript.

How many of the web developers here make their sites accessible through
text based browsers, or even know if their websites can be traversed
with a text based browser?

Re: Lynx, Links, and ELinks

On 2008-10-16, Carl wrote:
Quoted text here. Click to load it

   All my sites are usable with a text browser.

   Chris F.A. Johnson              <
   Shell Scripting Recipes: A Problem-Solution Approach (2005, Apress)

Re: Lynx, Links, and ELinks

Quoted text here. Click to load it

Mine is accessible[1], not hard to do -- presenting information and using
markup for presentation effects.  

[1] One page uses javascript, form not really usable in lynx unless one
really knows what it's about.

I don't get many hits from text browsers though, and this is likely why
people don't bother these days?

What really annoys me is my ADSL modem's web interface requires a browser
with frames -- how, pray tell, does one access the thing with a text-only
linux box?  One doesn't :(  


Re: Lynx, Links, and ELinks

Quoted text here. Click to load it

  A web sites is accessible to /any/ web client
  (otherwise it is not a web site).

  When some people create sites that are only accessible with a
  subset of web clients, they usually make an /extra effort/
  (by not only using HTML, but additiional languages and plug-ins).

  Web sites are not /made/ accessible.

  Web sites /are/ accessible.

  Web sites sometimes are /made inaccessible/ by extra effort
  when they are turned into HTTP-based applications. Often
  this does not provide any benefit to their users, but results
  in all kind of security risks.

  So, the question should be

      »How many of the web developers here do not make
      their sites inaccessible for text based browsers?«


Re: Lynx, Links, and ELinks

On 16 Oct 2008 21:55:42 GMT, (Stefan Ram) wrote:

Quoted text here. Click to load it

Crap, you've obviously not visited a site that renders as "[plug-in]"

..not accessible at all.


Re: Lynx, Links, and ELinks

Grant wrote:
Quoted text here. Click to load it

Grant is correct.  Stefan should have specified that he was only
talking about that subset of websites that are written in HTML.

Guy Macon

Re: Lynx, Links, and ELinks (Stefan Ram) writes:
Quoted text here. Click to load it

  OK, then let me put it this way:

  - An HTML document that renders texts, links and images
    in the following way probably is /not/ what TBL had in mind
    when he made up the World Wide Web:

        »Please activate JavaScript and install the Shockwave plugin.«

  - Usually, creating a web site that has reduced visibility,
    readability and usability due to the use of various
    scripting languages and binary data formats or the lock-in
    of data or media within web applications is /more effort/
    than just using HTML and linking to media using HTML.

    Insofar, web sites with plain HTML and media links are little
    effort for the producer and accessible to most clients.
    The more effort is spend to create fancy effects using
    scripting and plugins, the less accessible the page usually
    will become. And in this sense web sites /are made/ inaccessible.

Site Timeline