From: "Jared" <stofflej@yahoo.com>
To: <blinux-list@redhat.com>
Subject: Re: The growing accessibility gap: was Ameritech.net
Date: Fri, 7 Sep 2001 22:04:22 -0400 [thread overview]
Message-ID: <002e01c1380a$9aac5c20$0f4949cf@oemcomputer> (raw)
In-Reply-To: <Pine.LNX.4.33.0109072128290.17235-100000@ns.shellworld.net>
If the command line is so grate write me or help write me a mass market
application that cells to millions of coppies. You can't because you can't
use the g u i interface in linux like you can in windows. So you will have
to write in general smaller market programs if you wish to do that for a
job. I on the other hand because I'm not thick headed can write G U I
applications with vb or any number of other tools. As for your comment to
Mr. Toneby what about the people who tryed to make linux a more user
friendly opperaiting system generated a G U I so they generated code that
turned to inaccessible garbige for you so they are just as mutch at fault as
sun. A large part of microsoft is that the windows 3.1 was not around for a
long enough time for standerds to devolipe. They may have been responcible
for the inaccessibility in the past but now they are making an effort to
change that tell me is there anyone trying in the linux community cort or no
cort trying to make a screen reader for the G U I part of linux? If so
please send me email so I can try and help but don't complain about
microsoft when people arn't working to help your beloved oh so accessible
linux.
----- Original Message -----
From: "Jude DaShiell" <jdashiel@shellworld.net>
To: <blinux-list@redhat.com>
Sent: Friday, September 07, 2001 9:35 PM
Subject: Re: The growing accessibility gap: was Ameritech.net
> The command line interface does not cause me any problems, it's that other
> junk that makes life hell. So far as bitching is concerned, you haven't
> yet heard me bitch. All I did was to state some widely known and accepted
> axioms which are axiomatic since they're so easily proven. Were you
> correct in your statements, the Council Of Agencies Serving the blind
> would not have contemplated taking Microsoft to court in January of 1995.
> As it was, certain agreements were reached that seemingly alleviated the
> necessity for litigation.
>
> Jude <jdashiel@shellworld.net>
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
blindguy13
` Joseph Carter
` Jude DaShiell
` Jared [this message]
` Jude DaShiell
` Angelo Sonnesso
` Jared
` Rick Hayner
` Jude DaShiell
` The growing accessibility gap: Jared
` Rick Hayner
` The growing accessibility gap: was Ameritech.net Rafael Skodlar
` Andor Demarteau
` Ray Saldana III
` Ari Moisio
` Andor Demarteau
-- strict thread matches above, loose matches on Subject: below --
Adam Bertram
` Joseph Carter
Ameritech.net S. Massy
` The growing accessibility gap: was Ameritech.net Cheryl Homiak
` Jude DaShiell
` Peter Toneby
` Jude DaShiell
` Aman Singer
` 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
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='002e01c1380a$9aac5c20$0f4949cf@oemcomputer' \
--to=stofflej@yahoo.com \
--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).