[audacity4blind] Re: Audacity 2.0 build for Mac
- From: "John W. Hess" <wysiwygtechnologies@xxxxxxxxx>
- To: audacity4blind@xxxxxxxxxxxxx
- Date: Wed, 20 Jun 2012 20:21:04 -0500
> Good evening David.Answers to your questions .below.
> Given that VoiceOver can't read the input slider, do you use the sound window
> of system preferences to adjust the input volume? Gale has suggested
> assigning a keystroke (for example ctrl+4) to adjust input gain in the
> keyboard category of preferences. This then brings up an input volume dialog
> which contains both an edit box and a slider. My feeling is that using system
> preferences might be easier for new users of audacity.
> This is an excellent idea and although I haven't assigned the key I do use
> system preferences. Question, how do you assign a key for that particular
> function. I haven't played much with keyboard shortcuts and this would be
> quite helpful to know.
> 2. When VoiceOver reads a text box containing a number, it just reads out a
> series of digits, and doesn't read out if there's a minus sign, or if there
> are decimal points in the number. For example, in the amplification effect,
> when VoiceOver reads the Amplification text box, it doesn't read any decimal
> point. From what I remember, if you interact with the text box, you can arrow
> through the characters in the text box, and all the characters are read,
> although it reads a minus sign as dash.
> If you set punctuation to all you'll hear the dash and also the decimal
> point. press control-option-v to open verbosity and then press right arrow
> until you hear "punctuation". Press down arrow to move through the choices
> and enter or escape to exit the dialog.
> 3. Equalization effect. If the Graphic EQ radio button is checked, then
> VoiceOver can interact with the sliders. It's strange that it can interact
> with these sliders, but not the input/output sliders in the main window.
> However, if you move a slider to a low value, like 0%, then it get's stuck
> and you can't increase it beyond about 5%.
> I've noticed the stuck behavior and usually use page up or down to move in
> larger increments. It would be good to have this corrected. Yes, I don't know
> why the sliders don't work in the main window. Would be worth a look if
> nothing else for the learning and understanding. Perhaps they are different
> in some way in class? I really appreciate the attention the mac build is now
> getting. This is fantastic and Please! write if I can be of further help.
> David.
>
>
> ________________________________
> From: John W. Hess <wysiwygtechnologies@xxxxxxxxx>
> To: audacity4blind@xxxxxxxxxxxxx
> Sent: Tuesday, 22 May 2012, 5:41
> Subject: [audacity4blind] Re: Audacity 2.0 build for Mac
>
>
> Good evening David. I am a mac user and use the 2.0 accessible build that was
> made available by leland. I have not tried the knightly builds. LEt me try to
> answer your questions.
>
> 1. With a track being the focus, if you change whether it is selected or mute
> or solo, voiceover doesn't automatically read its updated state. I had to
> move away and then back to it to get it to read this. Is there a voiceover
> keystroke to read the current object so that the user doesn't have to move
> away and then back? (like insert+up arrow in Jaws).
>> Control-Option-W is the command to do this. REmember for this to work you'll
>> need to interact with the item that says "panel" and then interact with the
>> scroll area within the panel. Then control-w will read the track name and
>> it's state weather it's selected, soloed or muted.
>
>
> 2. In the controls for selection start, selection end etc, if you use the
> arrow keys to change the time, then voiceover doesn't automatically read
> anything.It has ben that way since Leland started working on the accessible
> builds. admittedly I didn't report this one because I found that using
> Control-option-W would read the information adequately. It would be nice to
> have it read when the arrows were moved. Perhaps something that can be worked
> on?
> 3. Voiceover didn't read the input or output sliders in the toolbars. It just
> said multiple indicators.
>> I see the same thing here. Interacting with the slider doesn't help here to
>> get the information. Would be nice to have this working.
> .
>
> 4. In the metadata editor, voiceover couldn't read anything in the table.
>> Haven't used that at all.
>> My access to a mac is limited, but I'd be grateful if mac users of audacity
>> would let me know if these are real problems, or if there's something I
>> haven't done right.
>> They are definitely problems and if possible should be addressed.
>
>
> thanks,
>> David.
>>
>>
>> ________________________________
>> From: Leland <leland@xxxxxxxxxxxxxxxx>
>> To: audacity4blind@xxxxxxxxxxxxx
>> Sent: Thursday, 22 March 2012, 0:38
>> Subject: [audacity4blind] Re: Audacity 2.0 build for Mac
>>
>> The Mac accessibility patches have been applied to the main source and you
>> should now be able to use the nightly builds to get quicker access to new
>> features and help test (hint, hint :-)).
>>
>> The nightly builds can be found at:
>>
>> http://audacity.homerow.net/index.php?dir=mac
>>
>> Leland
>>
>> The audacity4blind web site is at
>> //www.freelists.org/webpage/audacity4blind
>>
>> Subscribe and unsubscribe information, message archives,
>> Audacity keyboard commands, and more...
>>
>> To unsubscribe from audacity4blind, send an email to
>> audacity4blind-request@xxxxxxxxxxxxx
>> with subject line
>> unsubscribe
>>
>> The audacity4blind web site is at
>> //www.freelists.org/webpage/audacity4blind
>>
>> Subscribe and unsubscribe information, message archives,
>> Audacity keyboard commands, and more...
>>
>> To unsubscribe from audacity4blind, send an email to
>> audacity4blind-request@xxxxxxxxxxxxx
>> with subject line
>> unsubscribe
>>
>>
>
> The audacity4blind web site is at
> //www.freelists.org/webpage/audacity4blind
>
> Subscribe and unsubscribe information, message archives,
> Audacity keyboard commands, and more...
>
> To unsubscribe from audacity4blind, send an email to
> audacity4blind-request@xxxxxxxxxxxxx
> with subject line
> unsubscribe
>
Other related posts:
