From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: Needs educating: Message from Linux (fwd)
Date: Tue, 22 Jan 2002 10:15:01 -0500 [thread overview]
Message-ID: <002c01c1a35a$2ee49140$0100a8c0@tward> (raw)
In-Reply-To: <NEBBIDHHCLOFNFBODLHDOEMFCNAA.darocho@earthlink.net>
I take it you don't know much bout the Gnome 2.0 project. Well, here is a
more in depth look at Gnome 2. Which is part of the x-windows system.
1. Gnome 2 is being majorly over halled with speech accessible widgits,
screen reader hooks, and other fixes to make it accessible.
2. synth driver support is being added to support synths for Linux. This
project is called Gnome-speech.
3. the gtk+ language is being modified so that from now on all applications
using the standard gtk+ 2 will come out of the box accessible with
Gnopernicus and other x screen readers like it.
So steps are being taken to make X accessible, but it merely takes time.
----- Original Message -----
From: David Arocho <darocho@earthlink.net>
To: <speakup@braille.uwo.ca>
Sent: Monday, January 21, 2002 9:08 PM
Subject: RE: Needs educating: Message from Linux (fwd)
> The real question is access. Neither JAWS nor WINDOW EYES can give full
> access to the Windows operating system. If you get away from the small
> number of familiar Microsoft applications, you find that you have to limp
> along. This will be so until speech and Braille and large print access
are
> built right into the operating system. Linux is the only operating system
> that has a prayer of getting such access built in. However, until
> X-windows is made accessible, Linux will remain a solution for only a few.
> If it is not done soon, though, and X-windows gets to challenge Microsoft
> for its dominance, blind people will again be left out in the cold. The
> fact is tat, unless some of us get behind it and push and make our own way
> to get X-windows accessible, it is not going to get done. If any of you
> are interested in working aggressively toward that end, let me hear from
> you privately. Lists are great for getting people in touch, but they all
> tend to go in the direction of griping sessions a la talk radio. Let's
> start doing, as talk is very cheap and time is not on our side.
>
> David Arocho
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
Needs educateingRE: " Richard Villa
` Needs educating: " David Arocho
` Thomas Ward [this message]
` David Arocho
` randy turner
` Needs educateingRE: " Kirk Wood
` Thomas Ward
` Charles Hallenbeck
` Raul A. Gallegos
` Needs educating: " David Arocho
` Charles Crawford
` David Arocho
` Charles Hallenbeck
` Amanda Lee
` Geoff Shang
` Charles Crawford
` Geoff Shang
` Jason
` Charles Crawford
` Kirk Wood
` Amanda Lee
` Kirk Wood
` Amanda Lee
` Georgina
` Kirk Wood
` Kirk Wood
` Geoff Shang
` Georgina
` Amanda Lee
` Georgina
` Amanda Lee
` Thomas Ward
` Amanda Lee
` Thomas Ward
` Amanda Lee
` Thomas Ward
` Amanda Lee
` Kirk Wood
` Charles Crawford
` Kirk Wood
` Kirk Wood
` Needs educateingRE: " Thomas Ward
` Georgina
` randy turner
Needs educating: " Gregory Nowak
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='002c01c1a35a$2ee49140$0100a8c0@tward' \
--to=tward@bright.net \
--cc=speakup@braille.uwo.ca \
/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).