- From: Joanmarie Diggs <jdiggs@igalia.com>
- Date: Tue, 13 Dec 2016 16:07:56 -0500
- To: ARIA Working Group <public-aria@w3.org>
- Cc: "wai-xtech@w3.org" <wai-xtech@w3.org>
URL: https://www.w3.org/2016/12/13-aapi-minutes.html
Plain text follows:
[1]W3C
[1] http://www.w3.org/
Accessible Rich Internet Applications Working Group Teleconference
13 Dec 2016
See also: [2]IRC log
[2] http://www.w3.org/2016/12/13-aapi-irc
Attendees
Present
Joanmarie_Diggs, Joseph_Scheuhammer,
Richard_Schwerdtfeger, Bryan_Garaventa
Regrets
Chair
Joseph_Scheuhammer
Scribe
joanie
Contents
* [3]Topics
1. [4]Meeting next week (Dec 20).
2. [5]UIA mappings (Joseph/Bogdan) Finished and closed.
3. [6]ACTION-2066: (Joseph) Include spec text in 5.6.4
for automatic computation of posinset and setsize for
menuitems.
4. [7]ISSUE-654/ACTION-2130: (Joanie) Determine if AX API
supports description changes.
5. [8]ISSUE-618/ACTION-2129: (Rich) Deal with Cynthia's
single-selection-changed-event test file.
6. [9]Triage issues/actions:
https://www.w3.org/WAI/ARIA/track/products/23
* [10]Summary of Action Items
* [11]Summary of Resolutions
__________________________________________________________
<clown1> agenda: this
<scribe> scribe: joanie
Meeting next week (Dec 20).
JS: The decision is to not meet next week because there are not
enough people around.
RS: The ARIA Working Group meeting is not going to occur this
week.
UIA mappings (Joseph/Bogdan) Finished and closed.
JS: All of Bogdan's stuff has been merged into master.
... I think we're done with UIA mappings and ready for it to go
to testing.
... Reminder: We have UIA mappings for aria-haspopup, roles for
range-related widgets and for new table properties, feed, and
aria-details.
RS: Firefox supports the feed role.
ACTION-2066: (Joseph) Include spec text in 5.6.4 for automatic
computation of posinset and setsize for menuitems.
<clown> action-2066
<trackbot> action-2066 -- Joseph Scheuhammer to Include spec.
text in 5.6.4 for automatic computation of posinset and setsize
for menuitems and their subclasses. -- due 2016-05-19 -- OPEN
<trackbot> [12]http://www.w3.org/WAI/ARIA/track/actions/2066
[12] http://www.w3.org/WAI/ARIA/track/actions/2066
JS: I came across this action and thought I could knock it off
really quickly.
... Then looking at it I concluded it may already be done.
<clown>
[13]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#m
apping_additional_position
[13]
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_additional_position
JS: The above link is where it would be added.
... Third paragraph down begins (reads from spec)
<clown> Otherwise, walk backward and forward within the DOM
parent, counting items that have the same role.
JS: The above is from the spec
... (Discusses some language changes)
... Change "DOM parent" to "DOM parent or parent defined by
aria-owns"
JD: Parent or ancestor?
JS: I think I will leave it as proposed until someone
complains.
... For "walk backward and forward within the DOM parent",
"process the DOM parent counting items the have the same role."
RS: These are normative changes, right?
JS: Yes.
... I think it might be good to also add a statement to the
effect of, "If the role supports aria-posinset and
aria-setsize...."
... This is just so that people don't think they have to always
calculate it.
... If I make the above changes, do we agree that covers
menuitems?
... If I add special language for menuitems, then I think I
have to do so with option and other roles to which these
properties apply.
... I think we can cover all the applicable roles with a
blanket statement such as "if the role supports aria-posinset
and aria-setsize...."
<clown> "Otherwise, if the role supports aria-posinset and
aria-setsize, process the parent (DOM parent or parent defined
by aria-owns), counting items that have the same role"
BG: Can you have aria-posinset without aria-setsize?
JS: This is about user agent calculating the values if the
author didn't provide them.
... There is a special case for treeitem.
... (Reads)
<clown>
[14]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#m
apping_additional_position
[14]
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_additional_position
JS: 'for role="treeitem", walk the tree backward and forward
until the explicit or computed level becomes less than the
current item's level. Count items only if they are at the same
level as the current item.'
... Is what is currently in the spec for aria-posinset and
aria-setsize for treeitem elements
... Do my changes satisfy this action?
action-2066
<trackbot> action-2066 -- Joseph Scheuhammer to Include spec.
text in 5.6.4 for automatic computation of posinset and setsize
for menuitems and their subclasses. -- due 2016-05-19 -- OPEN
<trackbot> [15]http://www.w3.org/WAI/ARIA/track/actions/2066
[15] http://www.w3.org/WAI/ARIA/track/actions/2066
RS: I think so, yes.
JS: Then I will add a note to the action to make the
agreed-upon changes to the bullets we just discussed.
... Then I will close this action.
ISSUE-654/ACTION-2130: (Joanie) Determine if AX API supports
description changes.
<clown> action-2130?
<trackbot> action-2130 -- Joanmarie Diggs to Determine if AX
AXPI supports an event if the accessible description changes.
-- due 2016-12-13 -- OPEN
<trackbot> [16]http://www.w3.org/WAI/ARIA/track/actions/2130
[16] http://www.w3.org/WAI/ARIA/track/actions/2130
<clown>
[17]https://rawgit.com/w3c/aria/master/accname-aam/accname-aam.
html#events
[17]
https://rawgit.com/w3c/aria/master/accname-aam/accname-aam.html#events
JD: Sorry, I have not gotten to this yet.
JS: You were also going to check the event for name-changed.
JD: I'll do it next week on the 20th.
ISSUE-618/ACTION-2129: (Rich) Deal with Cynthia's
single-selection-changed-event test file.
<clown> ACTION-2129
<trackbot> ACTION-2129 -- Richard Schwerdtfeger to Deal with
Cynthia's test file referenced in issue-618 -- due 2016-12-13
-- OPEN
<trackbot> [18]http://www.w3.org/WAI/ARIA/track/actions/2129
[18] http://www.w3.org/WAI/ARIA/track/actions/2129
JS: Rich, you had an action last week to deal with this
orphaned test file.
RS: I'm going to add it, but we've had problems with the
password.
JS: This is the wiki?
RS: Yes.
JS: The action also indicates you should talk to Joanie and
Shane about events.
RS: I'll tackle this in January.
... I can now log in.
... It's now at the very end as a TODO:
[19]https://www.w3.org/wiki/ARIA_1.1_Testable_Statements#Select
ion_Events_for_MSAA_for_Single_Selection
... I'll also work on updating the testable statements for UIA.
... Can you move the action and issue to the test plan product?
[19]
https://www.w3.org/wiki/ARIA_1.1_Testable_Statements#Selection_Events_for_MSAA_for_Single_Selection
JS: Done.
Triage issues/actions:
[20]https://www.w3.org/WAI/ARIA/track/products/23
[20] https://www.w3.org/WAI/ARIA/track/products/23
<clown> issue-647
<trackbot> issue-647 -- Should aria-hidden=false put things in
the tree, or stay a no-op as it is now, and done in the 1.1
timeframe? -- open
<trackbot> [21]http://www.w3.org/WAI/ARIA/track/issues/647
[21] http://www.w3.org/WAI/ARIA/track/issues/647
<clown> [22]https://bugzilla.mozilla.org/show_bug.cgi?id=945194
[22] https://bugzilla.mozilla.org/show_bug.cgi?id=945194
JS: The associated Mozilla bug has been closed as WONTFIX.
... Does that make this issue an ARIA 2.0 item?
JD: I'm re-reading the Mozilla issue. But I do not like
aria-hidden="false".
... I'm ok with aria-hidden="true".
... Some of my concerns were stated here:
[23]https://bugzilla.mozilla.org/show_bug.cgi?id=945194#c60
[23] https://bugzilla.mozilla.org/show_bug.cgi?id=945194#c60
BG: For what it's worth, I don't like aria-hidden="false"
either.
... There are, and have been, issues related to this for quite
a while now.
BG + JS: There are interoperability issues because Firefox
won't override exposure for non-rendered content, but Safari
includes it in the tree.
JS: So what do we do?
JD: Was this introduced in ARIA 1.1? In other words is it at
risk?
JS: No.
... At some point in the 1.1 timeframe, it took on additional
meaning such as overriding display:none.
... But the spec mapping is "not mapped."
<clown>
[24]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#a
riaHiddenFalse
[24]
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaHiddenFalse
JS: But do we do about the issue?
JD: Do we want a statement in some spec so that authors are
made aware of this?
<clown>
[25]https://w3c.github.io/aria/aria/aria.html#aria-hidden
[25] https://w3c.github.io/aria/aria/aria.html#aria-hidden
JD: There's a note here
[26]https://rawgit.com/w3c/aria/master/aria/aria.html#aria-hidd
en
... That is something I can live with
[26] https://rawgit.com/w3c/aria/master/aria/aria.html#aria-hidden
JS: So we can close the issue?
JD: As far as I'm concerned.
JS: Objections?
Note text: At the time of this writing, aria-hidden="false" is
known to work inconsistently in browsers. As future
implementations improve, use caution and test thoroughly before
relying on this approach.
JS: Since no one is objecting, I am going to close this after
indicating in the issue why we're closing it.
<clown> issue-714?
<trackbot> issue-714 -- Need mappings for aria-roledesription
-- open
<trackbot> [27]http://www.w3.org/WAI/ARIA/track/issues/714
[27] http://www.w3.org/WAI/ARIA/track/issues/714
issue-714
<trackbot> issue-714 -- Need mappings for aria-roledesription
-- open
<trackbot> [28]http://www.w3.org/WAI/ARIA/track/issues/714
[28] http://www.w3.org/WAI/ARIA/track/issues/714
JD: Why is this open? All the actions are closed.
RS: Mac?
JS: There.
... All the mappings are present.
[29]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#a
riaRoleDescription
[29]
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaRoleDescription
JS: I'll close it.
issue-737
<trackbot> issue-737 -- Determine platform mappings for new
"term" role introduced in ARIA 1.1 -- open
<trackbot> [30]http://www.w3.org/WAI/ARIA/track/issues/737
[30] http://www.w3.org/WAI/ARIA/track/issues/737
<clown> issue-738
<trackbot> issue-738 -- UIA mapping for heading incorrect --
open
<trackbot> [31]http://www.w3.org/WAI/ARIA/track/issues/738
[31] http://www.w3.org/WAI/ARIA/track/issues/738
JS: We waiting on UIA and AXAPI on issues-737
issue-738
<trackbot> issue-738 -- UIA mapping for heading incorrect --
open
<trackbot> [32]http://www.w3.org/WAI/ARIA/track/issues/738
[32] http://www.w3.org/WAI/ARIA/track/issues/738
JS: This was raised by Cynthia.
... (Reads issue)
<clown>
[33]https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#r
ole-map-heading
[33]
https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-heading
RS: What did Bogdan do?
JS: It still says, "text"
<clown> issue739
<clown> issue-739
<trackbot> issue-739 -- UIA doesn't support heading without
level, how should we map role=heading without aria-level? --
closed
<trackbot> [34]http://www.w3.org/WAI/ARIA/track/issues/739
[34] http://www.w3.org/WAI/ARIA/track/issues/739
JS: It also references issue-739 which has been fixed and
closed.
... There is nothing in the UIA mapping other than text.
... And Cynthia says it also needs heading styleID in the texct
pattern run.
... I will email Bogdan.
Summary of Action Items
Summary of Resolutions
[End of minutes]
Received on Tuesday, 13 December 2016 21:08:38 UTC