From: Janina Sajka <janina@afb.net>
To: blinux-list@redhat.com
Subject: Re: help please
Date: Thu, 15 Aug 2002 09:14:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0208150912030.3268-100000@TekRD.grg.afb.net> (raw)
In-Reply-To: <Pine.BSF.4.44.0208142302440.97435-100000@server1.shellworld.net>
I don't understand why inaccessible installation holds up any hw or sw
under 508. The only way that could come under 508 is if there is an
accessible option, and then the installed system still has to get
evaluated against the competition. As we both know, machines spend more
time working than getting installed.
As for deploying Win--or anything else, I used to use Ghost (before Norton
bought it). Nowadays, I just use Linux and dd. Cheaper, more reliable, and
much more accessible--and it works like a charm.
On Wed, 14 Aug 2002, Jude
DaShiell wrote:
> Well, I suppose I've been working in a production environment for a bit
> too long. In that kind of environment it doesn't pay to try something and
> then find out you have something on the screen three days later which
> needed to be answered with yes rather than y and you didn't know that
> because the documentation no longer matched the actual software output or
> you hadn't been able to get into the documentation because that was on the
> disk too which still isn't installed. If someone had a project due in
> part of that time, that's a great way to get unemployed real fast and for
> cause at that. Whenever I've done dos installations in my more recent
> years I've tried to always have a talking installation disk and computer.
> With windows 98 that didn't work. Part of why Microsoft put windows
> narrator into windows 2000 was because of the problems I had installing
> win 98 at first. After awhile I got so much practice installing win 98 I
> could do it far easier. I haven't tried installing windows 2000 with
> narrator but a side benefit narrator has made possible was for nmci, our
> organization hasn't yet been able to get any of the professional screen
> readers through pop-in-the-box testing so the only way to have a talking
> nmci computer is by using windows narrator. I understand much of the
> other section 508 hardware and software is similarly held up too.
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
--
Janina Sajka, Director
Technology Research and Development
Governmental Relations Group
American Foundation for the Blind (AFB)
Email: janina@afb.net Phone: (202) 408-8175
Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org
prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Vitor Oliveira
` 'Georgina'
` Vitor Oliveira
` 'Georgina'
` Vitor Oliveira
` Jude DaShiell
` Janina Sajka
` Jude DaShiell
` Janina Sajka [this message]
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=Pine.LNX.4.44.0208150912030.3268-100000@TekRD.grg.afb.net \
--to=janina@afb.net \
--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).