This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27079 - Clarify simultaneous implementatinon of MSAA + UIA and MSAA + IA2
Summary: Clarify simultaneous implementatinon of MSAA + UIA and MSAA + IA2
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-16 15:39 UTC by Dominic Mazzoni
Modified: 2014-11-10 20:21 UTC (History)
5 users (show)

See Also:

Attachments

Description Dominic Mazzoni 2014-10-16 15:39:22 UTC 
How is a server supposed to simultaneously support MSAA + UIA Express and MSAA + IAccessible2 where the MSAA part differs?

As one example, the spec currently maps the HTML element ARTICLE to ROLE_SYSTEM_GROUPING in the UIA column, but ROLE_SYSTEM_DOCUMENT in the IA2 column.

A user agent can only implement one COM object per node. The MSAA / IAccessible part is shared; it can't change what it returns from get_accRole depending on whether the client speaks UIA or IA2, because there's no way for it to know.
Comment 1 alexander surkov 2014-11-10 20:21:20 UTC 
basically they have to be in sync. there are derivation on implementation level (like Firefox doesn't do what IE does) but it was suggested to call that other implementations or so. in other words there is standard and there are other implementation that may vary from each other