Some of you just played a little bit with JAWS. If you find problems, could you please verify with ZoomText, what ZoomText does with OOo?
ZoomText supports Java Accessibility much better! I had long conference calls with JAWS people some time ago, trying to get better support for OOo, but they even don't fix bugs on their side when we report some. We are not JAWS customers, and OOo is not on their focus, because of market share and missing demand from customers. So if you are a JAWS customer, and have trouble using OOo with JAWS, please file bugs to Freedom Scientific, we can't work around them. BTW - someone pointed to http://groups.google.com/group/mailing.comp.open-office/msg/ecdd0f0087459d88 and said bad performance and memory consumption is because of Java. This is not true. Big memory consumption and loop/crash is because JAWS doesn't support the Java AccessibelTabe interface correctly, so they try to get the content for millions of cells. To the accessibility issues: - Not every issue flagged with Accessibility keyword means that there is really a big problem - OOo 2.0.2 will concentrate on Accessibility tasks.... - ... but that wont help much for Windows Screen Readers if they don't fix bugs on their side - This is why OOo AT support on GNOME is better than on Windows. If something doesn't work because of a bug in AT, we can fix it there, because all GNOME AT is open source! Would be nice to see more people testing Accessibility on GNOME :) Malte. Malte Timmermann wrote: > To summarize, > > you are right that the AT page on OOo is outdated, we will fix that soon. > > AT that works: > ============== > > Windows, Screen Reader > - ZoomText 7.11, 8.12, 9.0 (yes, ZT *is* a screen reader since 7.x!) > - JAWS 6.2 > > Windows, Screen Magnifier > - ZoomText 7.11, 8.12, 9.0 > > Windows, On Screen keyboard > - IMHO all, they are quite stupid and just send Windows messages > > GNOME, Screen Reader > - Gnopernicus > - Orca soon > > GNOME, Screen Magnifier > - Gnopernicus > - Orca will become a Screen Magnifier some time > > GNOME, On Screen keyboard > - GOK > - Dasher > > > Java, Resources > ================ > > We can't remove Java usage on Windows, Java Accessibility API is the > only available Accessibility API on Windows right now. > Windows Vista will change that with UIAutomation. > MSAA doesn't help for exposing the document content, so AT would need to > use OOo API, which they don't plan to support. > > We might exchange the Java stuff with a native ATK implementation some > time on GNOME, but thats a lot of work to do. > ( Any volunteers? ;) ) > > > Accessibility in general > ======================== > > Problem is not technical Accessibility, in Mass they talk about > *efficiency*. This is good with MS Office and JAWS because JAWS does > special things (scripting) for MS Office and Internet Explorer. > They don't plan to do all these things for OOo. > We can't do much in OOo for improving this, this is in the hand of AT > companies! > > Malte. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
