[nvda] Re: Audacity problem

Ok, I am still a bit confused as to the point of this email.  I also tried the 
page using Jaws and it seems to have the same issues with the page that NVDA 
has.  While there are accessibility features in some aspects of flash, the 
programmer of the flash application has to use those accessibility features.  
It is basically the same with any application.  If the programmer puts a bunch 
of bitmap images that look like knobs on the screen the screen reader can't do 
optical character recognition on the screen to see the knob's label.  What must 
happen in cases like that is the programmer must put in the identifying code 
that a screen reader needs to be able to tell what the control is.  While it is 
fine that a control may have a tool tip associated with the control, there 
still needs to be a standard keyboard access to the control.  Many sighted 
programmers although not all, don't realize that screen reader users do not 
access their computer using the mouse.  The same goes for the original subject 
of this thread.  Myself also being a Jaws scripter just finished scripting for 
a program called Mini Moog.  The only reason I was able to script for the 
program at all is because I still have enough sight to see all of the knobs and 
buttons that were placed in the application.  Unfortunately a scripting tool 
called JFW Technical nor a tool called bx could even see there were controls on 
the screen.  So, because I have a little sight I was able to tell jaws to go to 
certain points on the screen and then tell jaws what the control was.  All of 
this would not have even been necessary if the programmer of Mini Moog would 
have taken the time to put standard identifiers in the program during design 
time.  Trying to get a screen reader to do all of these things should not and 
probably will not fall on the shoulders of the screen reader programmers.  Some 
responsibility also has to come from the developer's of the applications 
themselves.  As for the original subject of the thread.  If the programmer's of 
Audasity will put in 2 or 3 lines of code as an identifier of those radio 
buttons, it would save the programmers of NVDA, Jaws, Window Eyes etc. hours of 
work trying to extend the capabilities of the screen reader to accomodate a 
single application.  Much of this has been of my own opinion but I hope it 
makes sense to some.
  ----- Original Message ----- 
  From: Debra Riese 
  To: nvda@xxxxxxxxxxxxx 
  Sent: Tuesday, September 25, 2007 9:47 PM
  Subject: [nvda] Re: Audacity problem


  o for crying out loud, must be careful with typos, I will copy and paste 
links from now on.  Funny just finished reading an article about that too, how 
these people are buying up typo domain names.  Cheez, you guys must've thought 
I was a crazy lady.    

  http://www.myspace.com/dkriese (copied and pasted)

  This MP3 is limited and not fully coded.  I will send everyone the copied and 
pasted links when the updated version is ready, 
   
  http://www.newdigitalmedia.net/KBrown/TextMP3Player.swf

  The above is the direct link to the model that is in progress NVDA reads all 
the text placed in the window, however, need to get it to read the file 
embedded on an HTML page needs coding, some of you may not see it becuase your 
browser needs to support the opening of SWF files.  The other problem is 
getting focus onto the the page itself once the visually impaired user gets 
there.  But if you mouse over the buttons and player NVDA does read it. 
   
  This is a work in progress.

  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: