W3C home > Mailing lists > Public > public-pfwg@w3.org > March 2014


From: <jason@accessibleculture.org>
Date: Mon, 3 Mar 2014 10:18:39 +1300
Message-Id: <0B789E09-1DBE-4C32-828E-0AFF2DEE71F9@accessibleculture.org>
Cc: Cynthia Shelly <cyns@microsoft.com>, Rich Schwerdtfeger <schwer@us.ibm.com>, David Bolter <dbolter@mozilla.com>, Joseph Scheuhammer <clown.idi@gmail.com>, public-pfwg@w3.org, HTML Accessibility Task Force <public-html-a11y@w3.org>
To: steve Faulkner <faulkner.steve@gmail.com>, Alexander Surkov <surkov.alexander@gmail.com>
Looking for folks’ opinions on how we relate, in the HTML to accessibility API mappings, Firefox and Chrome’s use of VARIANT to return the tag name as string (BSTR) for elements without established roles in MSAA.

I think we had decided at one point that since this approach isn’t “described by the MSAA specification”, we wouldn’t indicate or promote it as a preferred mapping in the actual mapping tables, but instead just include a note about it [1]. The note exists [2], but we still have this use of BSTR noted in the MSAA + IA2 mappings themselves, for example, see the mapping for abbr [3].

Am I right in thinking, one, that Mozilla is looking at dropping the “BSTR hack” [4], and two, that the individual element mappings for MSAA + IA2 shouldn’t include this use of BSTR?



[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=16769#c3
[2] http://rawgithub.com/w3c/html-api-map/master/index.html#use-of-msaa-variant-by-some-user-agents
[3] http://rawgithub.com/w3c/html-api-map/master/index.html#el-abbr
[4] https://bugzilla.mozilla.org/show_bug.cgi?id=798492

Jason Kiss
Received on Sunday, 2 March 2014 21:19:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:01 UTC