From: Ari Moisio <armoi@sci.fi>
Cc: emacspeak@cs.vassar.edu, Blinux-list <blinux-list@redhat.com>
Subject: Re: some comments on software platform accessibility
Date: Thu, 6 Dec 2001 17:40:52 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.40.0112061640310.9052-100000@nkl.local> (raw)
In-Reply-To: <Pine.LNX.4.40.0112051257030.603-100000@beethoven.wgaughan.net>
Hi!
Comments on comments:
First there is lot of job opportunities within file, mail and
webserver maintenance. MOst of those use some *x operating system. Most
of those have no configuration interface, just a bunch of text files to
edit. No menus, no buttons, no dialogues, no bitmaps, no images and no
accessibility problems.
Secondly: ever after learnign windows and all tricks of his/her
screenreader with every program used blind worker should be equally or
more productive than sighted colleagues who can sinply look the screen.
This difference exists of ccourse in *x environment too but there it
is mainly reading speed, not figuring layout of the screen.
As a sidenote: local training center for the blind planned to keep
course on Linux but they had severe problems to find a teacher; all
blind advanced LInux users they askedwere too busy with their own jobs.
Fortunately they found finally one who volunteered because it was
Linux course.
--
Mr. Ari Moisio, Niittykatu 7, 41160 Tikkakoski, +358-40-5055239
ari.moisio@iki.fi http://www.iki.fi/arimo PGP-keyID: 0x3FAF0F05
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15373.49271.43983.793325@gargle.gargle.HOWL>
` Bill Gaughan
` Ari Moisio [this message]
` Bill Gaughan
` Luke Davis
[not found] ` <Pine.LNX.4.40.0112061615370.2275-100000@beethoven.wgaughan .net>
` Brent Harding
Ian Blackburn
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.40.0112061640310.9052-100000@nkl.local \
--to=armoi@sci.fi \
--cc=blinux-list@redhat.com \
--cc=emacspeak@cs.vassar.edu \
/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).