Andrew Brown wrote:
OK. I just spent five minutes playing with the Jaws 7.0 demo on a
system running windows 2k with 1GB of memory. Resource usage was not an
issue,so far as I could tell -- but t would have been catastrophic if
it was. On the other hand, Jaws and OOo 2.0 do not work well together.
The big and immediately obvious problems were
dialogue boxes -- not recognised by Jaws. It would navigate within them
if I could see what I was doing but that rather defeats the point.
There was no way to get it to read out all the choices
wizard dialogue boxes, with panes and different sheeets, completely
defeated it.
Menus sort of worked. But for about half the entries with icons it
would read out a meaningless entry before the choice itself, like
"Graphic 794 Fax". This seemed to happen at the top of a menu, before
the first separator, but not after. Some menu entires with icons were
read out as they should be.
Reading text from the screen -- this seemed to jump about in a
bewildering fashion. I could never tell where it was going to start,
and whether it would skip whole paragraphs. That may have been becaseu
I am an inexperienced, and sighted, operator. But it wasn't good.
So I think we have a real and serious problem here, unless there are
other screenreader programs which work better with OOo.
If I were blind I would refuse to use OOo with Jaws or to consider the
combination usable.
Thanks for the info! Can you file an issue for this?
Maybe it's related to
http://qa.openoffice.org/issues/show_bug.cgi?id=56539
Here are a few queries that pull up related issues:
Issues with keyword "accessibility":
http://qa.openoffice.org/issues/buglist.cgi?issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&keywords=accessibility&keywords_type=anytokens
-- 91 hits. Yikes!
Issues in subcomponent AccessBridge:
http://qa.openoffice.org/issues/buglist.cgi?subcomponent=AccessBridge&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED
-- 14 hits. mostly targeted for OpenOffice 3.0 due to lack of resources
http://qa.openoffice.org/issues/buglist.cgi?long_desc=jaws&long_desc_type=substring
-- 1 hit
It sounds rather like Sun sort of punted on accessibility for 2.0.
Maybe we can help them un-punt for 2.0.2.
One thing that would help is to go through all the bugs
related to this and make sure they have the keyword 'accessibility'.
Anybody feel up to that?
- Dan
--
Trying to get a job as a c++ developer? See
http://kegel.com/academy/getting-hired.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
