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

RE: Bug 13205

From: Cynthia Shelly <cyns@microsoft.com>
Date: Tue, 20 Sep 2011 22:33:02 +0000
To: Andi Snow-Weaver <andisnow@us.ibm.com>, David Bolter <david.bolter@gmail.com>
CC: "wai-xtech@w3.org" <wai-xtech@w3.org>
Message-ID: <C7E43C8B2FFAC740A28B5E52CF7EA91916848D@TK5EX14MBXC293.redmond.corp.microsoft.com>
Replace all of that with this.  We need the names of the equivalent to DefaultAction in ATK/AT-SPI and OSX.
As part of mapping roles to accessible objects as defined in (section), users agents will have implemented an MSAA DefaultAction, one or more UIA Pattern methods, or (whatever this is called in other APIs).

*         If an AT calls MSAA DoDefaultAction on an accessible object, the browser SHOULD simulate a click on the DOM element which is mapped to that accessible object.

*         If an AT calls the IA2 IAccessibleAction on an accessible object, the browser SHOULD simulate a click on the DOM element which is mapped to the that accessible object.

*         If an AT calls any UIA pattern method on an accessible object, the browser SHOULD simulate a click on the DOM element which is mapped to that accessible object.

*         ATK/AT-SPI ...

*         OSX ...
Note: Authors will need to create handlers for those click events that update ARIA states and properties in the DOM accordingly, so that those updated states can be populated by the browser in the Accessibility API.





From: Andi Snow-Weaver [mailto:andisnow@us.ibm.com]
Sent: Tuesday, September 20, 2011 1:09 PM
To: Cynthia Shelly; David Bolter
Cc: wai-xtech@w3.org
Subject: Bug 13205


Cynthia,

Working on bug 13205.

In the bug, you wrote "We actually think we should remove most of the section, including the table, and tell browsers to simulate a click if MSAA doDefaultAction is called, or if *ANY* pattern method is called via UIA.  JavaScript event handlers can then react to the click event and set the aria properties.  The browser will update the API based on the aria property changes, and it should all work."

I have removed the table from section 5.7 Actions. But I am uncertain what "remove most of this section" means.

<current text>
Actions are exposed by the following rules:

  *   elements which are natively focusable will usually have a default action or pattern specified as part of the native markup language specification.
  *
  *   User agents should set the default action to click or set the Invoke pattern for elements that have been made focusable by the author. For example, in HTML, authors indicate elements that are focusable using tabindex="0".
  *
  *   User agents should set the default action to click if the element has registered a click event handler

In MSAA, an action can be mapped to the DoDefaultAction and DefaultAction properties unless it is already supported by the baseline mapping (e.g., jump action for the hyperlink element).

In Microsoft UIA, an action can be mapped to the Invoke pattern, unless it is already supported by the baseline mapping.

In IAccessible2, an action can be exposed by the IAccessibleAction interface.
</current text>

Please advise specifically what, if any, of this remaining text needs to be deleted.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=13205

Andi
[cid:image001.gif@01CC77A6.8A390190]

[IBM Research]

Andi Snow-Weaver
Accessibility Standards Program Manager
Human Ability & Accessibility Center

Tel: +1-720-663-2789
Email: andisnow@us.ibm.com<mailto:andisnow@us.ibm.com>

[cid:image001.gif@01CC77A6.8A390190]





image001.gif
(image/gif attachment: image001.gif)

image002.gif
(image/gif attachment: image002.gif)

Received on Tuesday, 20 September 2011 22:33:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:16:12 GMT