[nvda] Re: Audacity problem

I am responding to your post because it is relevant to the work I am doing
too.  I am working on MP3 players for the visually impaired, as in this day
and age of MP3 music and YouTube Videos, web content for this community is
becomming limited.

What I have found is that I have to place separate text over each button to
have the screen readers recognize it.  I have mentioned this to the NVDA
developers and they are aware that certain content whether it be flash or
software applications need to have separate text identifiers.

As a developer, this has created multiple coding for me, one for the button
action, one for the function and one for the text to be read describing what
to do.

As soon as I have the Flash prototype ready, it will be presented to the
NVDA developers as they are interested in my development and use of their
screen reader.  So far so good with that.

I also use Audacity - it's a great application, so I will send my flash
widget/application/prototype to the Audacity developers so they can get an
idea of how I got the screen readers work with my application.

These MP3 players will be available free of charge to the visually
impaired.  This is the MP3 player that got this project started, if anyone
is interested.

www.mypsace.com/dkriese you will see the player I made for blind musician
Kevin Brown.
A portion I found could be read by the screen reader when I was testing it
on my computer.

Deb

On 9/25/07, Gene <gsasner@xxxxxxxxx> wrote:
>
> I may send a report to the development team.  However, my concern was not
> just with Audacity.  If it only sees radio buttons in this program in
> certain dialogs and no associated text, the text isn't seen on the screen
> at
> all which is demonstrated by using insert b to read the entire window,
> then
> this may be a problem that will be seen in other programs as well.  How
> many
> I don't know but I thought the NVDA developers might want to examine  the
> method used to display such text to determine the extent and ease of
> solution.
>
> Gene
> ----- Original Message -----
> From: "John Greer" <jpgreer17@xxxxxxxxxxx>
> To: <nvda@xxxxxxxxxxxxx>
> Sent: Monday, September 24, 2007 1:15 PM
> Subject: [nvda] Re: Audacity problem
>
>
> > That could also be an issue you may want to bring up with the audasity
> > team. If it is still in beta then there is no better time than the
> > present.  It does seem that because it doesn't work with other screen
> > readers that also rely on MSAA info that it may be a Audasity UI problem
> > that should be addressed.
> > ----- Original Message -----
> > From: "Gene" <gsasner@xxxxxxxxx>
> > To: <nvda@xxxxxxxxxxxxx>
> > Sent: Monday, September 24, 2007 1:34 PM
> > Subject: [nvda] Audacity problem
> >
> >
> >>I was just experimenting with Audacity while using NVDA.  In the
> >>preferences dialog, some items read correctly and some don't.  I'm using
> >>the beta version, 1.3 though I believe these problems would be present
> in
> >>earlier versions as well.
> >>
> >> So far, the specific problem I've found is that when you are on the
> file
> >> formats part of the treeview, radio buttons are announced as you tab
> >> through the dialog but no associated text is read.  I haven't checked
> >> much else yet but I did find that one other part of the dialog, when on
> >> another item in the treeview is read properly.
> >> The following information may or may not make it easier to determine
> the
> >> cause of the problem more quickly, but for what it's worth, the radio
> >> buttons are not read properly by Narrator, Thunder, or Serotek
> (spelling)
> >> System Access.
> >>
> >> Gene
> >> To post messages to the list send email to
> >> nvda@xxxxxxxxxxxxx
> >> To modify your NVDA Email settings go to:
> >> http://www.freelists.org/list/nvda
> >> Thank you for your continued support of Nonvisual Desktop Access, an
> open
> >> source free screen reader for Microsoft Windows:
> >> http://www.nvda-project.org/
> >> To get the latest NVDA snapshot:
> >> http://www.nvda-project.org/snapshots/
> >> Report bugs or make feature requests at:
> >> http://trac.nvda-project.org/
> >> Message Archive:
> >> http://www.freelists.org/archives/nvda
> >>
> >
> > To post messages to the list send email to
> > nvda@xxxxxxxxxxxxx
> > To modify your NVDA Email settings go to:
> > http://www.freelists.org/list/nvda
> > Thank you for your continued support of Nonvisual Desktop Access, an
> open
> > source free screen reader for Microsoft Windows:
> > http://www.nvda-project.org/
> > To get the latest NVDA snapshot:
> > http://www.nvda-project.org/snapshots/
> > Report bugs or make feature requests at:
> > http://trac.nvda-project.org/
> > Message Archive:
> > http://www.freelists.org/archives/nvda
> >
>
> To post messages to the list send email to
> nvda@xxxxxxxxxxxxx
> To modify your NVDA Email settings go to:
> http://www.freelists.org/list/nvda
> Thank you for your continued support of Nonvisual Desktop Access, an open
> source free screen reader for Microsoft Windows:
> http://www.nvda-project.org/
> To get the latest NVDA snapshot:
> http://www.nvda-project.org/snapshots/
> Report bugs or make feature requests at:
> http://trac.nvda-project.org/
> Message Archive:
> http://www.freelists.org/archives/nvda
>

Other related posts: