[audacity4blind] Re: Since I've decloaked...
- From: Leland <audacity4blind@xxxxxxxxxxx>
- To: audacity4blind@xxxxxxxxxxxxx
- Date: Tue, 10 Jun 2008 09:09:18 -0500
--On June 10, 2008 1:13:53 AM -0600 Gene <gsasner@xxxxxxxxx> wrote:
It depends on how you define accessible. JAWS and Window-eyes can read
many items in dialogs that System Access can't. I don't know how much
work would be involved in changing this nor whether the changes would
require other changes to make the interface look the same to sighted
users. However, you may want to be aware of the fact that some controls
in dialogs aren't accessible to less sophisticated screen-readers for
reasons I don't have the technical knowledge to discuss.
I hear that. I just recently tried Satogo and found that it and Audacity
didn't cooperate very well. But, I also found that NVDA read some things
better than Jaws or Window Eyes. And I don't know where Hal95 was getting
its information from, but it wasn't Audacity. ;-)
The way Audacity provides information to screen readers is via Active
Accessibility. If the product supports that interface, then it "should"
function well. I say "should" because it seems that everybody has a
different way of interpreting the Active Accessibility documentation and
this is causing me some headaches. Heck, even different versions of Jaws
utilize the interface differently.
I'll be curious what responses you get regarding the apparent recording
bug.
Here's a couple of responses. Nothing from the main devlers yet:
http://www.nabble.com/Any-reports-of-recording-issues--td17747720.html
Looks like I may have to dig into this one myself. (Again with the path
straying. ;-))
Leland
The audacity4blind website is at
http://users.northlc.com/sberry/
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:
