Re: [orca-list] fluxbox accessibility

["B. Henry" <burt1iband gmail com>]

Hardly
No need to always think the worst with out doing your research my friend.
Speech-dispatcher does not work for me here and I've done all you say. It did the first day or two I ran with 
the enable 
flag, but then an update to either chrome or chromevox, think the former broke it here and for others. It 
seems that some 
people can still use this however. I will try with chromium on arc h to make sure behavior is the same, but 
with stock 
chrome it's 100% no go with speech-dispatcher now for me.
The google folks made speech-dispatcher an opt-in option because the ammount of error they were getting was 
un-acceptable 
with current code, and sadly this is the case here as it won't run at all as mentioned. 
I have a need for the speech-dispatcher alternative as google-tts is not loud enough on my netbook, so 
hopefully some day 
soon things can be addressed. 
Perhaps speech-dispatcher needs some love and care?
I'll report back if I get anywhere using chromium, but it was working less well compared with chrome on Vinux 
for me so I 
did not install on Arch.

On Sun, Jun 15, 2014 at 04:08:22PM -0500, kendell clark wrote:
> speech-dispatcher support in chromium is broken? works fine here. All
> you need to do is add the --enable-speech-dispatcher flag when launching
> chromium. IF you want to make this permanent, try copying
> /usr/share/applications/chromium.desktop to ~/.local/share/applications/
> and opening the file in nano or your favorite editor. Go down to the
> exec line and after /usr/bin/chromium, type space, followed by
> --enable-speech-dispatcher. Save and close, and voila. It works again.
>  Every time you start chromium you'll get a nag about you're using an
> unsupported command line flag, and you're not as secure. I assume this
> is a nag to get you to install the google tts voices, who knew google
> would stoop to this.
>
> On 06/15/2014 12:17 PM, B. Henry wrote:
> > Just an update. 
> > On this slow system I can be working in aprox 5 seconds. It appears to take fluxbox about 2s before I can 
> > successfully 
> > press my shortcut for launching orca. I'll try getting orca to auto launch next, but at anyrate assumng 
> > nothing cpu 
> > intensive is going on anywhere else it takes orca about 3 seconds to say screenreader on after the 
> > shortcut is pressed. 
> > Still no luck on the list of aps I mentioned before. So, with no feedback in runbox terminals or 
> > filemanagers it's a bit 
> > uncomfortable for those like myself who like feedback along the way, and when you don't remember a file's 
> > exact 
> > name...lol. For sure the ticket for jumping on a voip ap quickly, or firing up firefox. 
> > BTW, google-chrome browser with chromevox works, but the google-tts engines that one is forced to use 
> > these days since 
> > speech-dispatcher support was broken don't sound very good compared with when I run chrome from a full on 
> > desktop.
> > Still looking for any ideas on getting orca to work with other programs that work on gnome, mate, etc.
> > gsettings set org.gnome.desktop.a11y.applications screen-reader-enabled true
> > has been done for some time here, so that isn't the problem.
> > --
> > B.H.
> >   
> > On Sun, Jun 15, 2014 at 01:03:14AM -0500, B. Henry wrote:
> >
> > > I am always looking for how to speed things up on my netbook, and generally am interested in helping 
> > > those who can't come 
> > > by the latest and greatest hardware to have a productive accessible Linux experience. Finally I have 
> > > gotten around to 
> > > trying fluxbox, and it certainly works well most of the time when it works,, e.g. firefox performs 
> > > better than it does on 
> > > the Desktop invironments I've tried; and instead of waiting 20 seconds before I hear screenreader on as 
> > > is the case with 
> > > Mate or XFCE Orca's ready to go in 10 secs or less. (and I can't start workin the instant I hear orca on 
> > > the full featured 
> > > desktops either as stuff is still loading)
> > > Anyway, several programs do not show Orca what it needs it seems, programs that are normally accessible 
> > > with no issues. No 
> > > terminal emulator has worked for me yet, pidgin also isn't showing me anything, and neither caja nor 
> > > pcmanfm "talk" to me.
> > > Rhythmbox, mangler, mumble, teamtalk client, and a few others are working very well so far. 
> > > Has anyone figured anything out to improve interaction between fuxbox and orca, or orca and any of these 
> > > troublesome aps 
> > > when using fluxbox?
> > > Thanks in advance for any ideas.
> > >  
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > https://mail.gnome.org/mailman/listinfo/orca-list
> > Visit http://live.gnome.org/Orca for more information on Orca.
> > The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > Log bugs and feature requests at http://bugzilla.gnome.org
> > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp