[nvda] Re: Audacity problem

Also, actually I did not see much of a problem with the radio buttons in Audasity 1.33, NVDA did seem to read the label associated to the radio button just fine although both jaws and NVDA does seem to miss the group name of these radio buttons. That however is a very common thing with screen readers. I did however notice some unlabeled sliders when browsing through some of the many effects it has. These problems however do arise when using Jaws to. The sliders I did find though also have a labeled edit box that the slider corresponds to that a blind person could use to change the values instead. Basically what I am saying is Audasity 1.33 for the most part is very accessible to a screen reader. It does have a bit of a learning curve but all audio editing software has that. So yeah I still lean toward my original hypothesis. Since version 1.3 is still in beta, it would be a good time for the users of Audasity to tell the Audasity team of problems they encounter. But to take it even further, I even tested the ability of screen readers to tell what track I am on when using its multi-track feature and I have to say also no problems there. Solo, Mute, volume and pan are all hotkeyed in the program itself. I have yet to find a help file and I find that kind of odd given that it is such a complex program but that again is the fault of the Audasity team. lol alright done with my review of Audasity 1.33 beta with NVDA now. Have fun. ----- Original Message ----- From: "Peter vágner" <peter.v@xxxxxxxxxxx> 
To: <nvda@xxxxxxxxxxxxx>
Sent: Thursday, September 27, 2007 1:14 AM
Subject: [nvda] Re: Audacity problem



Hello,
Maybe that's somewhat possible but initially when comparing window handles, control ids, class names and maybe other info when retrieved on a focused objects and info from the objects just pointed to by the object navigation you may see values of these properties are not the same. When using object navigation, window text is always audacity and window class is WXWindowClassNR. Maybe we would be able to retrieve the info after sending some specific window message to the control, but the problem is we don't know which one to send and we even haven't right window handle when traversing using object navigation. Thanks a lot for your ideas. Maybe after a while we will be able to come up with some more hacks. 

Peter
----- Original Message ----- From: "John Greer" <jpgreer17@xxxxxxxxxxx> 
To: <nvda@xxxxxxxxxxxxx>
Sent: Thursday, September 27, 2007 7:38 AM
Subject: [nvda] Re: Audacity problem
I just had a look through Audasity 1.33 beta using Jaws. and it seems that each of the radio buttons in the preferences dialog has its own control ID number. It might be possible to associate a text label to each radio button option through the control ID by assigning the correct text label according to the control ID it has much like what was done for the Outlook Express app module. Just a thought. ----- Original Message ----- From: "Peter Vágner" <peter.v@xxxxxxxxxxx> 
To: <nvda@xxxxxxxxxxxxx>
Sent: Wednesday, September 26, 2007 11:17 PM
Subject: [nvda] Re: Audacity problem



Hello,
What audacity guys are doing or perhaps it's the toolkit they are using problem, as a name they are exposing words such as "radioButton", "staticText", "statusLine"... ETC. When any particular controll gets focused it is possible to retrieve it's text by sending a "getWindowText" winapi message. With object navigation and insert+b you can get roles and states spoken at this point. 

Peter


Gene  wrote:
The odd thing is that if you are in the Audacity window and use insert b, the screen is read and text is read. I don't know if this is what you were getting at in your last message. Object navigation certainly does not produce useful information. I'm not using the latest snapshot so I don't know if this might change marginally but, at least with my nontechnical background, it strikes me as odd that NVDA can identify the buttons and read the associated text in the main window as well as other structures including the cursor position when using insert b but can't read anything useful otherwise. 

Gene
----- Original Message ----- From: "Peter Vágner" <peter.v@xxxxxxxxxxx>
To: <nvda@xxxxxxxxxxxxx>
Sent: Wednesday, September 26, 2007 12:47 PM
Subject: [nvda] Re: Audacity problem



Hello,

James Teh  wrote:
The problem is that these applications don't expose information about some of these controls through MSAA or some other accessibility API. In these cases, we can try to access the information through some other API (perhaps some standard Windows API for that type of control or an API specific to a custom control). For example, as Peter noted, some of these controls might expose their information as window text or the like.
I was wrong when I was tallking about values in my last email on this subject. In fact we are interested in window name not a value in case of radio buttons and checkboxes. So I found a way how to retrieve these names but this only works when controls are focused using caret navigation. When object navigation is used audacity returns some strange values and I am afraid we can do nothing about it. For example we are not able to read status bar, and all the static texts. A bit of code I was about to commit is now there so when new snapshots is made you may play with it if you feel like. for anyone who knows audacity it may be almost usable. For the others I am very sorry. 

Peter
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



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: