Comment 1 by briang1 on 2011-04-27 15:16
Has anyone else had this as a problem?
Does it only affect servers, or are there times when this is needed on regular pcs?

If the program could check the relevant info, and enable sound, why should it need to be a choice after that. Surely if you are running a screenreader you want it to talk to you.
I might also add that from bitter experience, there can be many reasons why the sound does not work. Dealing as I do with second hand systems, many offices seem to set it off in all sorts of nasty ways like bios or hacks.
I doubt this is a worry for most though!

How hard would this be to do transparently? does it need to reset the machine to do it?
This could be a problem.

Comment 2 by jteh on 2011-04-27 20:17
Generally, I feel that intrusive and potentially unwanted changes like this are bad. This is particularly true for a server, where an administrator should carefully consider any change that is made. It's possible that the person installing the software does not want the service to be enabled. For example, they might want to use braille only. In addition, if they were able to start the installer (presumably with sighted assistance or by knowing how to do it blind), it figures that they should be able to enable the service themselves (which can also be done blind). Unless these points can be addressed, I believe we should not introduce this.

Closing as won't fix as per the rationale in #1474 (comment). Server admins should be aware of this fact.