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 23:12:40 -0400 [thread overview]
Message-ID: <NEBBKMPKGLCOPILBKHEPGEEKIAAA.aasinger@idirect.ca> (raw)
In-Reply-To: <Pine.LNX.4.33.0109072249560.19408-100000@ns.shellworld.net>
Hi.
Small point. That two sites are inaccessible and that the sighted as well as
the blind have had trouble with them proves nothing about the language in
which they were written. I can't really think of a language that absolutely
prevents someone from making a disaster of a project, just as I can't think
of a car that prevents someone from crashing it due to inattention or
inability to drive.
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 10:56 PM
To: blinux-list@redhat.com
Subject: RE: The growing accessibility gap: was Ameritech.net
There are secured sites at work I have access to which because of problems
I ran into with them and because sighted people checked them out with
validators have been declared inaccessible. One of those two sites I
figured a workaround for another one is so broken it's probably going to
be scrapped. Neither was written by my employer but my employer bought
both of them from private contractors. Now, as for that site I figured a
workaround on one of the more competent computer users at my place of
employment who is sighted had so much trouble with that site it took him 2
days to get his work done on it for the first time. For me it only took a
week but I got it done.
Jude <jdashiel@shellworld.net>
_______________________________________________
Blinux-list mailing list
Blinux-list@redhat.com
https://listman.redhat.com/mailman/listinfo/blinux-list
next prev parent 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
` Jude DaShiell
` Aman Singer [this message]
` 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=NEBBKMPKGLCOPILBKHEPGEEKIAAA.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).