This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"IAccessible2 ROLE_SYSTEM_ TEXT" alex wrote: ) abbr elements is exposed in Firefox as "abbr" VARIANT on MSAA and IA2_ROLE_TEXT_FRAME on IA2.
MSAA roles are an enumerated list. Firefox's implementation using VARIANT is unique.
(In reply to comment #1) > MSAA roles are an enumerated list. Firefox's implementation using VARIANT is > unique. IAccessible::get_accRole takes VARIANT, the VARIANT arg should contain MSAA role from enumerated list (http://msdn.microsoft.com/en-us/library/windows/desktop/dd318485%28v=vs.85%29.aspx) or in Firefox case it may contain a string. I assume you meant that. Anyway, IA2 issue is not addressed here.
(In reply to comment #1) > MSAA roles are an enumerated list. Firefox's implementation using VARIANT is > unique. chrome exposes element names (e.g. span) as a string role value in some circumstances. suggest that we spec how firefox/chrome populate role value. what chrome and firefox expose is different , which is not very useful. Also should look at/document how xml:role and other IA2 object attributes are used to work around deficiencies in defined roles etc.
Chrome shouldn't much differ from Firefox implementation but anyway we can run on case by case basis and discuss it. So, reopening bug (at least because unaddressed IA2 mapping).
(In reply to comment #4) > So, reopening bug (at least because unaddressed IA2 mapping). IA2 mapping for abbr updated. Leaving open pending discussion on how to address MSAA role mapping using string for VARIANT.
Use of string "abbr" in MSAA VARIANT by Firefox and Chrome now documented: http://dvcs.w3.org/hg/html-api-map/raw-file/tip/Overview.html#el-3