From: Ryan Mann <rmann@rmisp.net>
To: speakup@braille.uwo.ca
Subject: Re: GNOME Accessibility Update
Date: Sun, 5 May 2002 19:49:08 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0205051946320.728-100000@rmnet> (raw)
In-Reply-To: <Pine.LNX.4.44.0205051229180.7861-100000@toccata.grg.afb.net>
Will this gnopernicus screen reader be able to read applications such as
Mozilla or Open Office? or will an application have to be written
specifically for the Gnome desktp?
On Sun, 5 May 2002, Janina
Sajka wrote:
> I thought folks on this list would appreciate the following
> progress report on GNOME accessibility:
>
> ---------- Forwarded message ----------
> From: Bill Haneman <bill.haneman@Sun.COM>
>
> As Marc indicated things are pretty busy here. The GNOME architecture
> and initial implementations of the APIs are nearly complete, we are
> working in several areas.
>
> GNOME 2 is nearing community 2.0(.0) release. We are hoping to get the
> kinks ironed out with regard to keyboard navigation and theme support.
> We are working on some GTK+ themes for low vision including
> high-contrast and large-size icons (which have been done tigert and
> jimmac in the GNOME community).
>
> ATK support for the base GTK+ library is substantially complete and we
> expect to have reasonable support for the core GNOME 2 desktop. Apps
> like gedit, gcalc, gnome-terminal, etc and the GNOME 2 panel are
> substantially accessible, though many bugs remain.
>
> Currently I am integrating the Java Accessibility API into the at-spi
> services, so that Java applications using the Java Foundation Classes
> will be accessible in the GNOME environment.
>
> Work is well underway in the open assistive technology projects as well,
> 'gok' the virtual keyboard suite, and the 'gnopernicus' screen reader.
> Our test tools for at-spi are also continuing to develop.
>
> We have a wish list; in addition to getting close to being able to
> integrate contributions of speech and braille drivers, we need:
>
> * a "virtual DDX" for XFree86 (that is, a way to create a virtual
> display framebuffer within a regular X Server instance), for
> magnification;
>
> * assistance in improving the performance of our basic screen
> magnification service;
>
> * a volunteer to port an upcoming new X extension for keysnooping to
> XFree86;
>
> * someone willing to tackle the issues of accessibility for an open PDF
> viewer;
>
> * people to port applications, test accessibility, and log bugs.
>
> best regards,
>
> Bill
>
> > Best,
> >
> > --JP
> >
> > =====
> > -
> > Cell Phone - 206-849-9032
> > Time Zone - Pacific (-08:00 UTC)
> > Home Page - http://ocularis.sourceforge.net
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Health - your guide to health and wellness
> > http://health.yahoo.com
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Janina Sajka
` Ryan Mann [this message]
` Janina Sajka
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.0205051946320.728-100000@rmnet \
--to=rmann@rmisp.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).