Hi guys,
OOo has a nice Accessibility properties panel. I suggest putting it there (as
a user configuration option). Also OOo already has logic to determine whether
it is supporting the Java Access Bridge and exposing AT-SPI information. So
you could use that to help decide whether to emit these events or not.
Thing is, for some AT usage you won't mind this, and for others you will.
So... I think the best option probably is to put it in the Accessibility
properties panel.
Without seeing this feature in real life, I don't have a strong opinion about
whether it should be off by default.
Of course, what might be off by default is emitting the events for the text
change...
Peter
Bill Haneman wrote:
Jörg Wartenberg wrote:
Hi Bill,
Some interessting details, that IMHO shoud be considered fo OOo 3.0:
-Mouse over a 'toolbar' button shows a preview at the current cursor
position
This would need to be configurable, and probably off by default, for
accessibility reasons (otherwise way too much noise emitted in the
form of attribute-change events from the text).
Interresting point, but why not switching it only off, if such a
device is used (e.g. if a braille reader is connected)?
Needs to be configurable, because one size doesn't fit all. If a feature
"disappears" without user control based on the use of an assistive
technology, that itself can be a serious accessibility violation.
Also there is no way to tell if a braille display is connected, etc.
Bill
Regards Jörg Wartenberg
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
