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.
