From: Chris Brannon <chris@the-brannons.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: UNS: instructions for doing an eyes-free install of chromevox on Linux
Date: Wed, 31 Jul 2013 08:48:37 -0700 [thread overview]
Message-ID: <87k3k6ohm2.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20130731152446.GC26339@concerto.rednote.net> (Janina Sajka's message of "Wed, 31 Jul 2013 11:24:47 -0400")
Janina Sajka <janina@rednote.net> writes:
> Because Chrome is self-voicing with Chrome Vox, Orca (and
> Speech-Dispatcher/Espeak) should be disabled while Chrome has focus.
The easiest solution is to disable Orca temporarily.
AFAIK, there's no way to silence Speech Dispatcher. If you're using it
as the output method for chromevox, you wouldn't want to do that anyway.
I think there might be a way to customize Orca so that Orca is disabled
when self-voicing apps like chromevox have focus. If there is, don't
use it right now. Chromevox does not (yet) speak some browser dialogs.
These can be read with Orca, however. Just enable it temporarily to
read them. Yes, it's annoying!
Here's my current setup.
I run chromium + chromevox under a lightweight window manager,
ratpoison. Chromevox uses Speech Dispatcher with eSpeak for speech.
Yes, I'm not taking the perfectly sound advice I just gave in the
previous paragraph, since I'm running without a desktop environment, and
hence, without Orca.
HTH,
-- Chris
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
Chris Brannon
` UNS: " Janina Sajka
` Janina Sajka
` Deedra Waters
` Chris Brannon [this message]
` Jason White
` Doug Smith
` Kyle
` Doug Smith
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=87k3k6ohm2.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--cc=speakup@linux-speakup.org \
/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).