public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* Feisty SpeakUp
@  Henrik Nilsen Omma
   ` Willem van der Walt
                   ` (3 more replies)
  0 siblings, 4 replies; 8+ messages in thread
From: Henrik Nilsen Omma @  UTC (permalink / raw)
  To: speakup

Hello,

I'd like to ask for some input on a spec I'm doing for the next version 
of Ubuntu. We currently have speakup in the kernel but it's very far 
from Just Works. See: 
https://wiki.ubuntu.com/Accessibility/Specs/FeistySpeakup

I guess I first have to ask what the common use cases are. Is speakup 
largely used by system admins and developers working from the CLI? Is it 
valuable to have a Live CD that boots to the CLI with speakup? We 
currently don't have CLI Live CD AFAIK.
 
The possible areas I could imagine improving usability are:

 * Server edition -- Currently has the speakup module, but not simple 
way to install or run live
 * The debian installer -- currently used on the alternate and server CDs
 * spoken boot -- have all the boot messages read out as you boot
 * Standard CLI, simple launch -- For those who prefer gnome it may be 
difficult to recover when X fails. It should be trivial to launch 
speakup in such cases: 'start-speakup'. An introduction with basic 
operating instructions should be read out.
 * anything else?


Another point I want to emphasise is that if we do this it would be in 
the main Ubuntu distribution, not a special derivative. It is not just 
intended for advanced computer users, but beginners as well. The 
features should then also get picked up by Kubuntu, Edubuntu, Mephis, etc.


Henrik


^ permalink raw reply	[flat|nested] 8+ messages in thread
* re: feisty speakup
@  Jude DaShiell
  0 siblings, 0 replies; 8+ messages in thread
From: Jude DaShiell @  UTC (permalink / raw)
  To: speakup

speakup gets you into all of the places orca and lsr and gnopernicus can't 
go because they're console interfaces.  It might be run by default 
whenever an xterm window opened up to speak the content in that window 
too.  The general use case for most on the speakup mailing list and the 
blinux-list is that speakup runs in the console environment when x in any 
of its forms isn't going to run or hasn't been started yet.  With a 
text-based installer that didn't use X to operate, speakup could probably 
work to install ubuntu onto many more systems or failing that make it 
possible for ubuntu to get bug reports back when installs fail maybe some 
text equivalent of bug-buddy that could do its work with a working 
internet connections and a few questions for the user.  I wonder does that 
bug-buddy have facility to add say a typescript file as part of the bug 
report as an attachment to a report that's about to be sent?  If so, 
developers could get a blow by blow account of what happened to reproduce 
the failure; along with other relevant system information perhaps captured 
by something like discover.




^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 Feisty SpeakUp Henrik Nilsen Omma
 ` Willem van der Walt
   ` Gene Collins
 ` Scott Ford
 ` John Heim
   ` Henrik Nilsen Omma
 ` Marcel Oats
 feisty speakup Jude DaShiell

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).