From: "propaine" <propaine@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: State of accessibility in linux
Date: Thu, 25 May 2006 18:45:59 -0400 [thread overview]
Message-ID: <003601c6804c$fe528ad0$2f01a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <3DF3EA63-B3C9-4AC6-B381-208D4106ADAA@gmail.com>
Where can I find information on Orca? Thanks!
Propaine
----- Original Message -----
From: "Jacob Schmude" <j.schmude@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, May 25, 2006 5:05 PM
Subject: Re: State of accessibility in linux
> Hi Scott
> With regard to Gnome accessibility, don't forget about the other
> screen reader, Orca. It has great potential and, at least for me, has
> superceded gnopernicus completely. It's scriptable and has
> independent cursor moving keys similar to speakup, with the ability
> to click the mouse where the cursor is as the windows screen readers
> do. Voiceover is still much more efficient at this point, yet Orca is
> getting better quite fast.
> Just my $0.02
>
>
> On May 25, 2006, at 10:01 AM, Scott Howell wrote:
>
> > For Gnome there's Gnopernicus which at least as of the last time I
> > tried it, it worked, but wasn't very efficient. I had real hopes that
> > would be the case, but if your looking for a comparison between the
> > gui-based Linux solutions and the Mac, the Mac would win hands down.
> > I say this because so far KDE isn't accessible to my knowledge,
> > Gnopernicus despite being a solution and a good one isn't really
> > ready for daily use based on my experience, and I am sure this will
> > improve with time. On the other hand, the Mac with VoiceOver is what
> > I use daily and for a large number of tasks and its very good. Is it
> > perfect? No, but then what adaptive solution is. They all have their
> > issues, but you simply have to choose what works best for you. Now if
> > your talking about access from the console, well Speakup will win
> > everytime because there is truly an accessible solution if there ever
> > was one. Speakup reigns supreme from the console providing more
> > access than any other adaptive solution both gui or console-based.
> > Now these are just my opinions and if you disagree, that's fine, I'm
> > not looking to turn this into a pissing contest, just merely making
> > some observations based on my experience.
> >
> >
> > Scott
> >
> >
> >
> > On May 25, 2006, at 6:52 AM, sean murphy wrote:
> >
> >> Hi Andrew,
> >>
> >> The accessibility to Linux varies depending on which application
> >> you are
> >> using. I know of four applications for the shell environment.
> >>
> >> Speakup
> >> Emacs speak (its own desktop environment)
> >> BRLTTY (only used with braille displays)
> >> IBM (They have a screen reader which I know very little about)
> >>
> >> There is a XWindows screen reader, but I don't know much about it
> >> and how
> >> good it is. If anyone on the list could add some info to this, I
> >> would be
> >> welcomed. I would like to know how it compares to Windows or MAC.
> >>
> >> Sean
> >>
> >> ----- Original Message -----
> >> From: "Andrew Wagner" <wagner.andrew@gmail.com>
> >> To: <speakup@braille.uwo.ca>
> >> Sent: Sunday, May 21, 2006 11:40 AM
> >> Subject: State of accessibility in Linux
> >>
> >>
> >>> Hi all.
> >>> I'm pretty new to this list. What is the state of accessibility
> >>> for linux
> >>> users? I read somewhere that there was at one time a goal of
> >>> having a
> >>> screen
> >>> reader that functioned from boot up to shut down. Is that the case
> >>> now? Is
> >>> there a linux distribution where the installation is local and
> >>> accessible?
> >>> What projects need to be done? I have a goal to find/create a linux
> >>> distribution to get my (blind) girlfriend off her dependency on
> >>> Microsoft.
> >>> One of these days...
> >>> _______________________________________________
> >>> Speakup mailing list
> >>> Speakup@braille.uwo.ca
> >>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >>>
> >>
> >>
> >> _______________________________________________
> >> Speakup mailing list
> >> Speakup@braille.uwo.ca
> >> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.394 / Virus Database: 268.7.1/347 - Release Date: 5/24/2006
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
Andrew Wagner
` Chris Norman
` sean murphy
` Scott Howell
` Jacob Schmude
` Scott Howell
` propaine [this message]
` sean murphy
` Andrew Wagner
` Michael Whapples
` Ralph W. Reid
` Andrew Wagner
` Scott Howell
` John covici
` Samuel Thibault
` Scott Howell
` Georgina Joyce
` David Poehlman
` Karen Lewellen
Ryan Mann
LARRY SKUTCHAN
[not found] <7.0.1.0.0.20060531121453.01ac8e68@carolina.rr.com>
` Ricky Enger
` propaine
` Marcel Oats
` Ricky Enger
` Marcel Oats
` Al Puzzuoli
` Marcel Oats
` Hynek Hanke
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='003601c6804c$fe528ad0$2f01a8c0@ALBERTLC7SN0ZA' \
--to=propaine@verizon.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).