public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: "Aman Singer" <aasinger@idirect.ca>
To: <blinux-list@redhat.com>
Subject: RE: The growing accessibility gap:  was Ameritech.net
Date: Fri, 7 Sep 2001 22:29:10 -0400	[thread overview]
Message-ID: <NEBBKMPKGLCOPILBKHEPCEEEIAAA.aasinger@idirect.ca> (raw)
In-Reply-To: <Pine.LNX.4.33.0109072137530.17235-100000@ns.shellworld.net>

Hi.
Jude DaShiell said
"When a computer language is written so that it's possible for stupid
programmers to generate garbage with it and call that finished product the
inventors of the language in my book take full responsibility for having
enabled the garbage."

Following that logic, basic, c and c++, FORTRAN, as well as any and all
languages used in a GUI environment, and most used in a text environment
such as dos, are garbage and their manufacturers are responsible for
inaccessibility. Obviously, this is wild. When Mr. Smith makes a keyboard,
is he responsible for Mr. Davidson's lack of spelling ability?
He also said
"html on its face before Netscape and Microsoft came
in and added their innovations was lots more accessible just using lynx
than most of the world-wide wait is today."

Note that html is not, by itself, inaccessible. It's lazy people, both blind
users and sighted designers who make it so. I'm a trainer for blind users of
access tech, and I've stopped counting the number of times I've heard people
say that a site isn't accessible when it's they who don't know how to use
it.
Aman



Reading maketh a full man, conference a ready man, and writing an exact man.
           Francis Bacon

-----Original Message-----
From: blinux-list-admin@redhat.com
[mailto:blinux-list-admin@redhat.com]On Behalf Of Jude DaShiell
Sent: Friday, September 07, 2001 9:42 PM
To: blinux-list@redhat.com
Subject: Re: The growing accessibility gap: was Ameritech.net


When a computer language is written so that it's possible for stupid
programmers to generate garbage with it and call that finished product the
inventors of the language in my book take full responsibility for having
enabled the garbage.  html on its face before netscape and microsoft came
in and added their innovations was lots more accessible just using lynx
than most of the world-wide wait is today.

Jude <jdashiel@shellworld.net>

On Sat, 8 Sep 2001, Peter Toneby wrote:

> On Fri, Sep 07, 2001 at 05:36:26PM -0400, Jude DaShiell wrote:
> > The three companies primarily responsible for inaccessibility are sun
> > microsystems for having invented java in the first place.  Second
netscape
> > for having innovated html and java.  Third Microsoft for having
innovated
> > everything else.
>
> *beeep*
> Now this is pretty much plain wrong!!!!
> Java, in and on itself, is not inaccessible, it's stupid programmers
> that write stupid java-applets,. That should never have been possible.
> HTML is not netscapes fault, it w3c's, and netscape hasn't touched Java
> very much, IE and Netscape had java-support at the same time. And
> Microsoft haven't innovated shit. they have moslty bought their
> "innovations" and Windows is alot more accesible than linux when it
> comes to apps, In Linux you can't just start jaws and then pretty much
> any other app without problems, try and do that on linux with X (say to
> do something thee are no fileformat->text-app, You will fail miserably,
> but luckily this is seldom the case for most of you. And you can happily
> use Linux in console instead of X.
>
> oh, well time to stop rantin and start sleeping...
>
> /Peter
> --
> Alpha Test Version:  Too buggy to be released to the paying public.
> Beta Test Version:  Still too buggy to be released.
> Release Version:  Alternate pronunciation of "Beta Test Version".
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>



_______________________________________________
Blinux-list mailing list
Blinux-list@redhat.com
https://listman.redhat.com/mailman/listinfo/blinux-list




  reply	other threads:[~ UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Ameritech.net Karl Dahlke
 ` Ameritech.net Cheryl Homiak
 ` Ameritech.net Cheryl Homiak
 ` Ameritech.net Janina Sajka
   ` Ameritech.net John J. Boyer
     ` Ameritech.net Janina Sajka
   ` Ameritech.net S. Massy
     ` The growing accessibility gap: was Ameritech.net Cheryl Homiak
       ` Jude DaShiell
         ` Peter Toneby
           ` Jude DaShiell
             ` Aman Singer [this message]
               ` Jude DaShiell
                 ` Aman Singer
             ` Andor Demarteau
         ` Andor Demarteau
           ` Mike Gorse
             ` Andor Demarteau
     [not found]         ` <Pine.GSO.4.21.0109081949390.27801-100000@abeel.students.cs .uu.nl>
           ` simon
             ` Andor Demarteau
               ` Saqib Shaikh
 blindguy13
 ` Joseph Carter
 ` Jude DaShiell
   ` Jared
     ` Jude DaShiell
     ` Angelo Sonnesso
       ` Jared
     ` Rick Hayner
       ` Jude DaShiell
     ` Rafael Skodlar
       ` Andor Demarteau
         ` Ray Saldana III
     ` Ari Moisio
 ` Andor Demarteau
 Adam Bertram
 ` Joseph Carter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NEBBKMPKGLCOPILBKHEPCEEEIAAA.aasinger@idirect.ca \
    --to=aasinger@idirect.ca \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).