ACTION-2056: Coordinate the mappings for the various AAPIs of the enumerated aria-haspopup values

Coordinate the mappings for the various AAPIs of the enumerated aria-haspopup values

State:
closed
Person:
Joanmarie Diggs
Due on:
June 7, 2016
Created on:
April 26, 2016
Associated Issue:
Mappings for aria-haspopup
Related emails:
No related emails

Related notes:

Rich, also modify the error section, especially the table that states what the fall-back mappings are for missing required aria-* attributes:
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#authorErrorDefaultValuesTable

The entire error section, for your reference:
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#document-handling_author-errors

Joseph Scheuhammer, 28 Apr 2016, 17:58:58

Rich added all platforms but webkit for Mac. Joanie to do this part. Rich's branch was pulled in.

Richard Schwerdtfeger, 24 May 2016, 19:24:40

Rich's change merged with some editorial fixes:

https://github.com/w3c/aria/commit/673df28b8f80f3f415a1777a72a2ec2512927527

Joseph Scheuhammer, 6 Jun 2016, 21:42:29

It's unlikely we need this change in 1.1 since the element that "has popup" already references the role type of the popup through the IDREF of @aria-controls or @aria-owns. For the sake of scoping, please reconsider whether this modification is critical for 1.1.

Of note is that this change is not backwards-compatible with ARIA 1.1 because authors changing aria-haspopup="true" to one of the new enumerated types will find that this breaks all current implementations. It will currently be treated as aria-haspopup="false" (the default value for ARIA 1.0).

The only implementation change that WebKit would require is to make the other token values (any string besides "false" or "undefined") exposed as the boolean True. It's unlikely any user-perceivable change would be required, since users are not used to hearing things like "popup button opens dialog" or whatever the intention was with this property.

James Craig, 17 Jun 2016, 20:51:08

@James, So, the problem with relationships is that if it has not been popped up yet it may not exist in the accessibility tree. So, the reason that the aria-haspopup valuse are present are to tell the user that the combobox will open a dialog, etc. so that when they land in new context they are not wondering why the web page author landed them in a dialog box from a combobox and hopefully they will not go back into having to retrace their steps to find out how they got there.

Richard Schwerdtfeger, 18 Oct 2016, 19:56:30

Closing as both AX API and UIA are not implementing this at this time. They may in the future. The mappings are given in the Core-aam.

Joseph Scheuhammer, 31 Jan 2017, 20:39:23

Display change log.


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 $