[Accessibility-handlers] about Minutes20080421

[Pete Brunet]

>If the browser doesn't support some XML dialect then browser EH plug-in 
may be a JS script that allows the browser to expose that XML content to 
AT

PB: We talked about this on the EH call today and we don't understand how 
a JS script can be an a11y EH, i.e. how can JS implement MSAA/IA2 or ATK? 
If not then what are the alternatives?  Can it be done in XUL?  We suspect 
not.  I assume it would be done in C++ using the FF (or IE or Safari) 
plug-in architecture.  In that case would there be a way to define a 
standard browser to plug-in interface, e.g. through IDL?

>and here @implements attribute is used to define when that script should 
be executed. 

>In this chain I don't get what role does AT EH plug-in play. Is it used 
when the specialized markup should be transformed to information to be 
used by something else than screen readers?

The AT EH is a helper for the AT, e.g. a screen reader.  Screen readers 
don't know how to properly speak, for example, math expressions so the 
screen reader would pass off the string which defines the expression in 
some standardized format such as snippet of MathML.  The EH would take the 
MathML as input and send a string suitable for expression by a TTS engine. 
 Neil could give us an example.

So I am envisioning (and maybe there is a better idea)
1) an EH for the browser to provide a navigation UI into sub-objects of 
the entire expression and exposure of a11y info of those sub-objects as 
they get focus via MSAA/IA2 or ATK
2) an EH for the AT that knows how to best express a given piece of MathML 
for a TTS or Braille device.

>Where are ontologies here?
PB: Maybe you can help us with this.

Pete Brunet
                                                                          
IBM Accessibility Architecture and Development
11501 Burnet Road, MS 9022E004, Austin, TX 78758
Voice: (512) 838-4594, Cell: (512) 689-4155
Ionosphere: WS4G




"Alexander Surkov" <surkov.alexander at gmail.com> 
Sent by: accessibility-handlers-bounces at lists.linux-foundation.org
04/24/2008 12:44 AM

To
accessibility-handlers at lists.linux-foundation.org
cc

Subject
[Accessibility-handlers] about Minutes20080421






Hi.

I have some questions when reading 
https://www.linux-foundation.org/en/Accessibility/Handlers/Meetings/Minutes20080421.html
.

"PB: big picture: two EH plug-ins, one for the browser, one for the AT. 
The browser EH provides UI to navigate through the special content; The AT 
EH knows how to transform specialized markup into speech or braille; 
browser EH provides keyboard interface for objects/elements - the 
granularity can be controlled by the user - the typical navigation 
requests would be previous, current, and next item at the currently 
specified level of granularity - when objects in the browser EH get focus 
they fire focus events; theAT asks the object for its acc name which would 
expressed in a standardized markup language for a particular discipline 
(math, music, chem) and then the AT would call the AT EH for a 
transformation of a specific kind (Braille, TTS) and then the AT would 
output the TTS/Braille to the TTS or Braille engine."

There is two cases: when the browser supports the XML dialect natively or 
it doesn't. When the browser does then browser EH plug-in is the browser 
itself (another words: browser EH plug-in is hardcoded into browser). For 
example, like we have in Firefox for HTML. There we expose HTML content to 
AT by AT API (like ATK or IAccessible2) usage. If the browser doesn't 
support some XML dialect then browser EH plug-in may be a JS script that 
allows the browser to expose that XML content to AT and here @implements 
attribute is used to define when that script should be executed. In this 
chain I don't get what role does AT EH plug-in play. Is it used when the 
specialized markup should be transformed to information to be used by 
something else than screen readers? Where are ontologies here?

Thank you much.
Alexander._______________________________________________
Accessibility-handlers mailing list
Accessibility-handlers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/accessibility-handlers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/accessibility-handlers/attachments/20080428/a04bb7e6/attachment.htm