Re: Use of BSTR in MSAA VARIANT

Thanks, Joseph. It is useful. There is a similar section in the HTML
guide [1], but slightly less detailed.

On the BSTR hack question, I think that the HTML guide should follow
suit. Especially given the new outline for the implementation guides,
they should be consistent where appropriate.

[1] http://rawgithub.com/w3c/html-api-map/master/index.html#exposing-html-features-that-do-not-directly-map-to-accessibility-api-properties

Cheers,

Jason


On Wed, Mar 5, 2014 at 5:00 AM, Joseph Scheuhammer <clown@alum.mit.edu> wrote:
> FWIW, the ARIA UIAG [1] mappings do not recommend using the BSTR hack.
>
> There is a section in the UAIG about handling ARIA attributes that don't
> have direct mappings to a11y APIs [2].  Briefly:  With respect to UIA, use
> AriaRole and/or AriaProperties; and for IA2, use object properties.  Also,
> there is a note at the end of the section about MSAA:
>
> 'Editorial Note: MSAA does not provide a mechanism for exposing attributes
> that do not map directly to the API and among implementers, there is no
> agreement on how to do it."
>
> There are a number of cases in the role mapping table [2] that recommends
> these mechanisms.  For example for role="banner", the MSAA+UIA Express
> mapping is "Expose as text string in AriaRole". The MSAA+IA2 mapping is use
> object attribute "xml-roles:banner".
>
> Finally, there is no "pure" MSAA implementation documented in the UAIG, as
> MSAA is always used in concert with either UIA or IA2.
>
> Hope that's useful.
>
> [1] http://www.w3.org/TR/wai-aria-implementation
> [2] http://www.w3.org/TR/wai-aria-implementation/#mapping_nodirect
> [3] http://www.w3.org/TR/wai-aria-implementation/#mapping_role_table
>
> --
> ;;;;joseph.
>
>
> 'A: After all, it isn't rocket science.'
> 'K: Right. It's merely computer science.'
>              - J. D. Klaun -
>
>
>

Received on Wednesday, 5 March 2014 21:13:02 UTC