And one further point. People who are blind sometimes forget that there are other people in the world who see and who use the mouse. I happen to know a couple with low vision who use SR. True, they may lose enough of their vision at some point to need to use more of the keyboard commands, and they already use many of them. But, using the mouse for them, not to mention people who have normal vision, is a very normal thing to do. So, one would definitely point out ways to use SR with the mouse. If you really want to read a manual that is mouse crazy, try the Sound Forge manual. Yes, they have a lot of short cut keys, but for the most part, the manual is written for sighted users. So, in my opinion, SR has gone out of its way to make the manual easy to use by all people. I think that is a definite plus and not a minus. Neal -----Original Message----- From: studiorecorder-bounce@xxxxxxxxxxxxx [mailto:studiorecorder-bounce@xxxxxxxxxxxxx] On Behalf Of ROB MEREDITH Sent: Wednesday, June 21, 2006 8:10 AM To: studiorecorder@xxxxxxxxxxxxx Subject: [studiorecorder] Re: New Exciting Beta Version Daveed: Our manual is what it is, a manual for the product. We don't favor any group specifically; we only document the product and its features. If anything, we feel like we offer much more accessibility than any other wave editor, and it is all documented. As for moving marks with the keyboard, this is not possible directly. The easiest thing to do is simply clear the mark, move to the place where you want it, and set a new one. This may sound like we are skirting the issue, but if you think about, designing an interface to move marks with the keyboard would be more complacated than just clearing the mark and creating one somewhere else. Can you imagine being in "mark move mode"? Sounds dreadful! Rob Meredith >>> daveedm@xxxxxxxxxxxxx 06/20/06 10:47PM >>> I still wish to plead, Rob, that you provide some explicit and clearer docs for keyboard-related stuff, as opposed to mouse girations. For instance, moving marks and selection are discussed with the mouse, and one must dig to find keyboard equivalents. I still hyaven 't found the one for moving marks. Am I, what the British describe as daft or something? I think you might also address how to make Studio Recorder as accessible as possible using screen readers. I realize the product was first and foremost meant for sighted monitors and narrators, but since we blind folks have discovered a real hit with this product, I feel the docs could be significantly more blind-friendly. Now remember, I'm a big SR booster, so don't take me wrong here--but yours docs are very sight-oriented. Take care. --Daveed--At 12:30 PM 6/20/2006, you wrote: >We try! We'll keep trying! > > >>> curtis@xxxxxxxxxx 06/20/06 03:26PM >>> >Holy Toledo! Rob, what an exciting product! I mean it really is quick, >innovative, very stable compared to all others, and in all ways, easy >to use, speech friendly (accessible with screen readers with graphics >only for those who want them), and surprisingly the interface is >intuitively elligant. > > > >Curtis Delzer > > >At 11:43 AM 6/20/2006, you wrote: > >Yet another new feature graces Studio Recorder in this new beta >release. > >Well, actually two new features, but one big one. Resampling Rules! > >(I'll let you read the What's New file for the other feature.) > > > >Rob Meredith > > > > > > >-- >No virus found in this incoming message. >Checked by AVG Anti-Virus. >Version: 7.1.394 / Virus Database: 268.9.2/370 - Release Date: 6/20/2006 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.1.394 / Virus Database: 268.9.2/370 - Release Date: 6/20/2006