Thanks for the reminder.
I just found your message from a few years back, and tried to test this with
In fact we did the same thing, so sorry for copying your idea without giving
the credit since you discovered this first way back!
Unfortunately it still is impossible to read the values by using Voiceover
reading commands or using the arrow keys.
The only way I found to get something spoken is the following:
1 Press the left bracket key twice to get the dialog open.
2. Press home.
3. Type the exact number and hope for no mistake
4. Press tab.
5. Press shift + tab to move focus back to the edit field and get the values
6. It is possible to change the numbers via the arrow keys but be very very
careful! Because you have to right arrow and guess where you are and then press
the up or down arrow key, then press tab and shift tab to get focus forward and
If you get lost in this press escape and start all over from step 1.
So this can be done, but I would almost never use it because there are so many
things that can go wrong very easy.
Sorry for sounding harsh on this one!
Best regards Thomas
Den 13. maj 2019 kl. 12.28 skrev Andrew Downie <access_tech@xxxxxxxxxxxxxx>:
Re editing in the Selection Toolbar, I worked out a way of doing this a few
years ago and I think the (far less than optimal) approach has come back to
me. This also applies when pressing left or right bracket ([ and ]) when not
As a by the way, I set Audacity to read in hours, minutes, seconds and
milliseconds. Having entered the dialog, I press Home to make sure I am at
the beginning. I then enter the nine digits for the position I want. My
vague memory is that I had a way of checking what I had entered, but the
process escapes me now. This is a far cry from Windows, where it is possible
to enter values easily by either using arrow keys and/or by keying in values
and getting immediate feedback.
Thomas, being the diligent person you are, you may want to confirm or
otherwise the above poorly explained process.
<mailto:audacity4blind-bounce@xxxxxxxxxxxxx>> On Behalf Of Thomas Byskov
Sent: Monday, 13 May 2019 1:30 AM
To: audacity4blind@xxxxxxxxxxxxx <mailto:audacity4blind@xxxxxxxxxxxxx>
Subject: [audacity4blind] Comments on accessibility in Audacity 2.3.2 RC01
for Mac OS (was): Re: Release candidate for Audacity 2.3.2 available for
Hi Paul and David!
I have now tested Audacity 2.3.2 RC1 on my Mac and here are my notes in no
Navigating preferences with Voiceover:
General navigation has ben improved, but there are still room for improvement
When command-comma is pressed to open the preferences focus lands on the Help
button. It would be better if focus was forced to the categories tabel
In order to navigate between the different category items one has to interact
with the category hidden layout area before the items can be read by
Voiceover. Up or down arrowing does not give any feedback but using the
voiceover movement keys (control + option in conjunction with the arrow keys)
does give feedback.
However in the earlier version of Audacity this category item area was
possible to use because Voiceover saw this as a tabel which was easier to
navigate because both the arrow keys and the Voiceover movement keys worked
Changing preferences: For this I specifically wanted to change the language
from system default to English, because I prefer to work with audio
applications in English.
So I did the following:
Pressed command-comma to open preferences.
Pressed voiceover-home to get to the category hidden layout area, where I
interacted with this area.
Navigated to the “interface text” item and stopped interaction.
Now here I see some strange things:
If I navigate with the Voiceover keys all combo boxes where I can select
language, placement of the manual and select a theme is mentioned as dimmed.
A combobox is often called a popup button on the Mac..
If I use the tab key instead the buttons mentioned before aren’t dimmed and I
can activate them with the spacebar.
Interestingly enough I can in fact press the voiceover spacebar on the
buttons as well, but this is not expected behaviour, and this may confuse
users, because the information is mis leading.
As soon as the Voiceover cursor lands on a checkbox the keyboard focus is
there, so some of the preferences works great, but some areas may need some
tweaking to get there.
So far I couldn’t see many changes in this area.
Audacity is however possible to use, but it is not as efficient as in earlier
versions due to the way track selection works at the moment, but it can work
out. It is important though that new users will get some instructions if they
expect the same navigation methods to work on the Mac at the moment.
Editing via the selection toolbar:
This is a quite important area and here I have tried to follow along with the
guide David has created for Jaws-users. This area needs a lot of work.
It was possible for me to navigate to the toolbar with command-shift-F6 and
from here tab to the edit boxes. Voiceover will read the contents, but if I
try to change a position things become quite complicated:
If I for example tab to the start edit box and press the up arrow key it will
change, but no feedback from Voiceover.
If I interact with the edit field I can not get the values spoken regardless
of what I do.
If I type into the start edit box I will not hear any information either. So
I have no idea where I typed my numbers in.
The only way I could get the information spoken was to press tab to the next
edit box and then shift tab back to the previous field where Voiceover will
speak the contents and values.
But this makes doing edits in a project a little hard to do, and almost
impossible on the Mac with Voiceover.
I will say though that I really enjoy the look of the preferences and I for
sure enjoy that Audacity can be used on the Mac again.
Please let me know if I can help testing anything out. I will be more than
happy to do this.
Best regards Thomas
Den 6. maj 2019 kl. 10.55 skrev David Bailes <drbailes@xxxxxxxxx
Here's a list of new features for 2.3.2:
The main feature is probably that the lame mp3 encoder is now included in
For screen reader users on Windows 10, this version now works well with
For Windows users, these are the direct links to the installer and the zip
The following is a direct link to the .dmg for Mac, so that Thomas, and
anyone else interested, can give Paul feedback about the accessibility of
2.3.2 with VoiceOver:
If you test this release candidate and find any problems, please report them
to this list,