I am afraid that Java presents problems that, if Apple has its own Java virtual machine that does not talk to the accessibility API, can be nearly impossible to fix.
The twoapproaches on Windows, JAWS and Window-Eyes, take two separate approaches. JAWS, which has had Java for quite a while, uses the accessibility bridge from Sun which is a bear to deal with. The guy who wrote the hack for Window-Eyes using their kick-ass scripting function went straight to the VM and used its debugging tools - a very clever approach as it neither relied on the largely instable bridge nor on Swing as plenty of developers use the debugging tools with a wide variety of different libraries, including Swing. I don't know a thing about an Apple virtual machine but, if it does contain a debugging system similar to the Sun Java VM, someone, in theory at least, could use the technique of stealing the debugging information and sending it to the synthesizer.s Sadly, I've had my hand in Java accessibility for my tenure at FS (6 years) and a tiny bit since. I would have thought that this problem would have been much closer to a solution in 11 years of trying. On cup #2. cdh On Sep 4, 2009, at 1:39 PM, Barry Hadder wrote: > > Hay, > > You might try the button labeler. I haven't tried it yet so I can't > tell you anything about it. > > The app you are trying to is is accessible as far as java apps go. If > it wasn't, you would be able to tell if there were buttons or anything > els. As I said before though, java still has a ways to go before it's > 100 percent friendly with screenreaders. Even on the Mac. Allot of > things in regards to controls being labeled correctly is largely up to > the developers and what they do or don't do. > > It's my understanding that java on the Mac is Apple's own > implementation so I'm not sure way it's not more reliable in terms of > accessibility than it is, but hopefully it will get better. > Hopefully someone else may have more suggestions then I do. > > On Sep 4, 2009, at 3:07 AM, anouk radix wrote: > >> >> Hello hmm the app i tried, i could read the text on the first page >> but >> the buttons were not labelled nor did they have any helptags. >> Greetings, Anouk, >> On Sep 3, 2009, at 11:13 PM, Barry Hadder wrote: >> >>> >>> Hi, >>> >>> On the Mac, java is accessible right out of the box. No access >>> bridge >>> is required. It seems to me to be marginally better then jaws in >>> Windows, but it's still not perfect. >>> >>> On Sep 3, 2009, at 3:54 PM, anouk radix wrote: >>> >>>> >>>> Hello, in the neoofficce discussion i thought there was some kinf >>>> of >>>> java accessibility toolkit mentioned? Will this also help making >>>> apps >>>> accessible with voicover or was it just for windows and windows >>>> screenreaders? If it would improve java accessibility on the mac I >>>> would like to point the link to the neooffice and jamochamud >>>> devteams. >>>> Greetings, Anouk >>>> >>>>> >>> >>> >>>> >> >> >>> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacVisionaries" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/macvisionaries?hl=en -~----------~----~----~----~------~----~------~--~---
