W3C home > Mailing lists > Public > wai-xtech@w3.org > September 2012

Re: MSAA role mappings in a11y API guide

From: Alexander Surkov <surkov.alexander@gmail.com>
Date: Thu, 20 Sep 2012 11:17:14 +0900
Message-ID: <CA+epNsfv+B3+Ot+KGM08bYDi8oh133cwjZbNoxk8m0AuwgH=Gg@mail.gmail.com>
To: Jason Kiss <jason@accessibleculture.org>
Cc: wai-xtech@w3.org, Steve Faulkner <faulkner.steve@gmail.com>, Cynthia Shelly <cyns@microsoft.com>, Larry Weiss <lweiss@microsoft.com>, Char James-Tanny <charjt@helpstuff.com>, David Bolter <david.bolter@gmail.com>
Hi, Jason. It sounds very reasonable but it's not clear about "MSAA +
IA2 + UIA" browsers. It can be addressed later though when we get
these browsers on the market.
Thank you.
Alex.


On Thu, Sep 20, 2012 at 10:49 AM, Jason Kiss
<jason@accessibleculture.org> wrote:
> The HTML to Platform Accessibility APIs Implementation Guide [1]
> currently includes mappings for MSAA. Given the somewhat legacy status
> of that API, we would like to remove the separate MSAA mappings, and
> instead provide mappings as has been done with the ARIA User Agent
> Implementation Guide [2]. That is, we would note instead mappings for
> "MSAA + UIA Express" and "MSAA + IAccessible2".
>
> We would additionally add a section about other accessibility
> implementations. For instance, this section would include an updated
> version of the current note about Firefox and Chrome's use of MSAA
> VARIANT [3] to read as follows:
>
> "In MSAA, the VARIANT returned by the IAccessible::get_accRole method
> is limited to a finite number of integer role constants insufficient
> for describing every HTML element, especially new elements introduced
> by HTML5. To address this limitation, some user agents, e.g., Firefox
> and Chrome in cooperation with some screen readers, have elected to
> expose new roles by returning a string value in that VARIANT in a way
> that is not described by the MSAA specification."
>
> Are there any concerns with the above approach?
>
> Alex, does the above change to the note about FF and Chrome address
> the concerns you had with it [4]?
>
> Thanks,
>
> Jason
>
>
> [1] http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html
>
> [2] http://www.w3.org/TR/wai-aria-implementation/#mapping_role_table
>
> [3] http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html#note_variant
>
> [4] https://www.w3.org/Bugs/Public/show_bug.cgi?id=16769#c2
Received on Thursday, 20 September 2012 02:17:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 20 September 2012 02:17:42 GMT