Jonathon, you are right that JAWS has much greater market share than ZoomText, but what does it help?
When the problem is in AT, not in OOo, we can't fix it, so ZoomText is good for proving that it's very likely not a OOo bug. To some of the other AT on your list: Next version of Dolphin Supernova will support Java Accessibility, so hopefully OOo too. We tried 6.52 Beta, there are still some problems. Look Out, WindowEyes and Virgo don't support Java Accessibility API. For the others I don't know, but I guess they also don't support Java Accessibility API. To your concerns regarding filing issues to JAWS: You might be right that they don't care much about home users, but as I said, we (Sun) also failed to convince them to do something. To your points > i) Write a JAWS script for OOo. Freedom Scientific has already spent many years only in writing and maintaining scripts for MS Office and IE, and still spend a lot of time and resources into that. I am not sure someone who doesn't work for JAWS can do that in a reasonable time. If possible at all, depends on what scripting can do, like accessing Java Accessibility API. > ii) Help develop of FLOSS screen reader for Windows; We help to do this on Linux/Solaris running GNOME. Open source AT on open source desktops. Malte. Jonathon Blake wrote: > Malte wrote: > > >>ZoomText supports Java Accessibility much better! > > > JAWS has much greater market share than ZoomText has. > > Also need to look at: > i) HAL / Dolphin Software > ii) Look Out / Choice Technology; > iii) WindowEyes > iv) Virgo / Baum > v) BRLTTY / FLOSS (?) > vi) EmacSpeak / > vii) Suse-BLinux / SUSE > viii) VoiceOver (Macintosh) > > >>please file bugs to Freedom Scientific, we can't work around them. > > > The only bug reports that Freedom Scientific takes seriously are those > filed by corporate users. [Their apparent working assumption, which > probably is legitimate, is that all home users who have JAWS are using > either a pirated version of JAWS, or a version that has reached the > end of its life. Not many people who use JAWS can afford to buy the > updates.] > > >>- Not every issue flagged with Accessibility keyword means that there is >>really a big problem > > > "Big" is very much the perception of the beholder. For blind users, > things that might appear to be trivial, can have major consequences. > [Consider, for example, a warning message in its own box popping up on > a computer screen. If the blind person doesn't know that the message > is there, from their perspective, the computer system has crashed, and > none of their data has been saved.] > > >>Would be nice to see more people testing Accessibility on GNOME :) > > > When will GNOME be available for Windows? > > I'm not sure who wrote: > > >>Problem is not technical Accessibility, in Mass they talk about *efficiency* >>We can't do much in OOo for improving this, this is in the hand of AT >>companies! > > > i) Write a JAWS script for OOo. > ii) Help develop of FLOSS screen reader for Windows; > > xan > > jonathon > -- > Does your Office Suite conform to ISO Standards? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
