Edit ACTION-1569: Create a section that describes AAPI differences

Title:

State:

Person:

Due Date:

(accepts formats such as "2005-05-17", "+1 week", "14 August 2005" and "next Thursday")

Associated Issue:

Or Associated Product:

Add notes (no markup allowed, URIs get automatically hyperlinked):

Related emails:

  1. PFWG-ACTION-1569: Create a section that describes AAPI differences (from sysbot+tracker@w3.org on 2015-01-26) (from sysbot+tracker@w3.org on 2015-01-26)

Related notes:

"Comparing Accessibility APIs" section created in CORE-AAM on 2015-02-02 in "issue-540" branch at https://github.com/w3c/aria/tree/issue-540/core-aam

Jason Kiss, 3 Jun 2015, 02:35:01

Raw git url to the new section:
http://rawgit.com/w3c/aria/issue-540/core-aam/core-aam.html#comparing-accessibility-apis

Joseph Scheuhammer, 23 Jun 2015, 18:59:43

Second email sent to Jason for his thoughts. Sent privately, but it is a copy of:
https://lists.w3.org/Archives/Public/public-aria/2016Jan/0119.html

Joseph Scheuhammer, 1 Feb 2016, 18:23:39

Merged in Jason's changes, see:
https://github.com/w3c/aria/commit/9c69c0cba4cdd878c1dc076fe76035bf6095c9f2

Marking as "pending review"

Joseph Scheuhammer, 19 Feb 2016, 20:42:22

Email to Jason (and Cynthia) for their final review:
https://lists.w3.org/Archives/Public/wai-xtech/2016Feb/0046.html

Joseph Scheuhammer, 22 Feb 2016, 19:16:50

Latest pull request from Jason:
https://github.com/w3c/aria/pull/289/

Joseph Scheuhammer, 9 Mar 2016, 15:49:48

Waiting on Cynthia's modified UIA example. See ACTION-2032.

Joseph Scheuhammer, 14 Mar 2016, 18:38:12

Roughly, move first sentence of ATK/AT-SPI section outside since it is more general.

Joseph Scheuhammer, 5 Apr 2016, 19:31:20

Email from Jason, suggesting some editorial changes for UIA (see below). Joseph emailed the suggestions to Cynthia for her input.

Jason's suggestions:

Hi Joseph,

All good by me. I’d just fix a few inconsistent capitalizations in the UIA section, as follows:



<section>
<h5>UIA</h5>
<p>Central to UI Automation is the concept of Control Patterns. Control Patterns allow the description of common kinds of UI element behavior. These behaviors can be grouped together to express new types of UI controls. For example, the <code>TreeItem</code> Control Type is required to support the <code>ExpandCollapse</code> Pattern, because expanding and collapsing is what defines a tree item. Tree items can optionally have other behaviors. A developer creating a <code>TreeItem</code> Control can also choose to implement the <code>Invoke</code> Control Pattern if the tree item can perform a command, <code>ScrollItem</code> Control Pattern if the tree is scrollable, and the <code>SelectionItem</code> Control Pattern if it is possible to have an active selection that is maintained when the user returns to the tree container.</p>
<p>ARIA 1.x does not directly support Control Patterns, but many of the UIA mappings in the AAM documents combine Control Patterns to express web interaction concepts that are not Control Types in UIA.</p>
</section>


Cheers,

Jason

Joseph Scheuhammer, 2 May 2016, 17:33:12

Confirmed Jason's suggested changes at 03-May-2016 AAPI telecon (see comment 02-May-2016).

Added those changes:
https://github.com/w3c/aria/commit/e919427ed77c45894c72eecfd98c8da4f3f4f66f

Closing.

Joseph Scheuhammer, 5 May 2016, 13:52:01


James Nurthen <nurthen@adobe.com>, Chair, Michael Cooper <cooper@w3.org>, Ruoxi Ran <ran@w3.org>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <w3t-sys@w3.org>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $