[jawsscripts] Fw: Firefox: Could the ISimpleDOMNode.idl TLB bug be elevated to high priority?

Forgive the cross-post... FYI, in case anyone is interested. This is a 
continuation of a conversation on the Mozilla Accessibility Dev list.

    ----- Original Message ----- 
From: "Bryan Garaventa" <bgaraventa11@xxxxxxxxxxxxxx>
To: "dev-accessibility Firefox" <dev-accessibility@xxxxxxxxxxxxxxxxx>
Sent: Wednesday, July 16, 2008 9:56 AM
Subject: Could the ISimpleDOMNode.idl TLB bug be elevated to high priority?


> Thanks for the IAccessible2 info, that makes sense. There doesn't look to 
> be
> a way to convert an IAccessible2 object to a DOM object though, which is
> where the crux of the problem appears to be regarding screen reader
> scripting support.
>
> Would it be possible to elevate the ISimpleDOMNode.idl TLB bug to a
> significant priority? At least regarding accessibility.
>
> Ensuring ISimpleDOMNode.idl TLB support would ensure the following...
>
> 1) That all Windows AT applications, including JAWS and Window Eyes, would
> be able to create an internal COM object, and use this within their own
> application regardless of their dev environment. This COM object could 
> then
> be used within the AT to return the W3C standard DOM for the Firefox
> IAccessible MSAA object returned by AccessibleObjectFromEvent. This DOM
> object could then be used as a return value for a relevant function call
> within the AT scripting language.
>
> 2) Since the standard W3C DOM is returned within JAWS when using a JAWS
> scripting function such as IEGetCurrentDocument(), having the ability 
> within
> the AT to use the ISimpleDOMNode.TLB type class to convert the IAccessible
> MSAA object to a standard W3C DOM would automatically ensure that all
> current IE JAWS scripts would seamlessly work as designed by the scriptor
> within Firefox. It would be a simple matter for the AT to determine which
> browser is being used, and reference the correct DOM object accordingly.
> Since Window Eyes now has extensive COM scripting support, accessibility
> within Window Eyes would equally be assured using this type class.
>
> 3) All that would be needed by the Firefox dev team would be to ensure 
> that
> the ISimpleDOMNode.idl interface can be successfully converted to a COM
> accessible TLB type class. There would be no need to implement COM or
> IDispatch support within Firefox to ensure AT accessibility.
>
> This bug fix would essentially hit quite a few birds with the same stone.
>
> Best wishes,
>
> Bryan
>
>
> --------------------------------------------------------------------------------
> Bryan Garaventa
> Senior Accessibility Engineer
> SSB + BART Group
> bryan.garaventa@xxxxxxxxxxxxxxxx
> www.SSBBartGroup.com
> Accessibility-On-Demand
>
>
> ----- Original Message ----- 
> From: "James Teh" <jamie@xxxxxxxxxxx>
> Newsgroups: mozilla.dev.accessibility
> To: <dev-accessibility@xxxxxxxxxxxxxxxxx>
> Sent: Tuesday, July 15, 2008 9:49 PM
> Subject: Re: Compiling IDL files using Midl.exe?
>
>
>> Bryan Garaventa wrote:
>>>   Thanks for the bug info, I'm not familiar with IAccessible2, does this
>>> interface roughly cover the same functionality as
>>> ISimpleDOMDocument.idl, ISimpleDOMNode.idl, and ISimpleDOMText.idl?
>> IAccessible2 is an extension to IAccessible (MSAA) which provides the
>> rich accessibility coverage that MSAA lacks. For example, it handles
>> editable text, images, attributes on objects and text, tables, etc.
>> Conceptually, when using IAccessible2 with Firefox, you are viewing an
>> accessibility hierarchy. It is not an exact replica of the DOM, although
>> it does follow the DOM in some respects. Most DOM nodes are represented
>> in some way, but you might obtain information differently. For example,
>> if you have a hyperlink object, you wouldn't look at its href attribute
>> to get the URL, but you would instead use its accessible value or query
>> to the IAccessibleHyperlink interface. To provide another example, if
>> you are looking at a clickable piece of span, you wouldn't look for an
>> onClick attribute, but rather, you would examine its accessible action
>> to determine whether it is "click".
>>
>> You can find more info on IAccessible2 here:
>> http://www.linuxfoundation.org/en/Accessibility/IAccessible2
>>
>> Jamie
>>
>> -- 
>> James Teh
>> Email: jamie@xxxxxxxxxxx
>> WWW: http://www.jantrid.net/
>> MSN Messenger: jamie@xxxxxxxxxxx
>> Jabber: jteh@xxxxxxxxxx
>> Yahoo: jcs_teh
>> _______________________________________________
>> dev-accessibility mailing list
>> dev-accessibility@xxxxxxxxxxxxxxxxx
>> https://lists.mozilla.org/listinfo/dev-accessibility
>
> _______________________________________________
> dev-accessibility mailing list
> dev-accessibility@xxxxxxxxxxxxxxxxx
> https://lists.mozilla.org/listinfo/dev-accessibility 

__________ 
View the list's information and change your settings at 
http://www.freelists.org/list/jawsscripts

Other related posts: