See also: IRC log
<clown> agenda: this
<scribe> scribe: joanie
<clown> issue-738?
<trackbot> issue-738 -- UIA mapping for heading incorrect -- closed
<trackbot> http://www.w3.org/WAI/ARIA/track/issues/738
JS: Cynthia asked a question
about the heading role.
... Bogdan provided a patch. I pulled it in.
RS: Is it implemented?
JS: I added a comment that it
might not be implemented.
... I closed the issue, but I realized this might be a 1.1
change.
RS: Why if it's under the covers?
JS: Before it just stated to map
it to text.
... But arguably, everything is 1.1. So I don't have to call it
out then?
... But if for UIA everything is 1.1, then we need tests for
everything.
RS: We don't have to do them
all.
... We just have to do what changed in 1.1.
JS: We have a general request
from Microsoft to put greater detail in the Core AAM.
... This request was made off-list.
... The last thing I heard from Bogdan was that he was willing
to do the work.
... I suggested to Bogdan that he write a paragraph explaining
the default interface should be assumed.
... Rather than repeating it everywhere throughout the
spec.
... He is also going to provide some text explaining current
versus cached.
RS: But what are we going to do for the ATTA?
JS: I think we agreed that we'd use cached, but Joanie is concerned about potential ATTA/harness timeouts should the calculation not come back sufficiently fast.
RS: So the ATTA developers will need to handle that.
JS: Also, Bogdan indicated that
he'd do the work, but not when he'd have it done by.
... But this area is progressing and is no longer
stalled.
... I guess I should ask Bogdan when he thinks he'll have it
done by.
RS: Joanie, will we have an ATTA for UIA done in the near future?
JD: I'm not sure.
RS: I would like to have an ETA for ATTAs next week.
JD: <mutters something about regressions Apple introduced to accessibility of WebKitGtk which she has to focus on now>
JS: This is a pull request that Joanie put out about a week ago.
<clown> https://github.com/w3c/aria/pull/537
JS: There's a RELATION_POPUP_FOR
in ATK/AT-SPI, but there's nothing in the spec that allows the
user agent to implement it.
... I had a couple of very small comments.
<clown> https://github.com/w3c/aria/pull/537#pullrequestreview-27926175
JS: One was wording in the ChangeLog
JD: <explains her rationale for using "undid" rather than "removed">
JS: Ok, that's fine. I will pull this in later in the week.
JS: https://github.com/w3c/aria/pull/536
... This is something Joanie discovered.
... AXRoleDescription for alertdialog is now "web alert
dialog"
... AXRoleDescription for dialog is now "web dialog"
... I pulled it in and told Joanie that she could close it if
she thinks it's complete.
<clown> https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-alertdialog
JD: I can close it, but I'm not signed in and two-step authentication means I need to get a code on my phone, and I'm scribing....
JS: I can sign in and close
it.
... Done
RS: Joseph's employer wants to
phase Joseph out his work in ARIA.
... Because they want him to work on other things.
... Being out before 1.1 CR is going to be problematic.
JS: What they want is a transition plan.
RS: We don't have the resources
right now, especially during the CR process.
... I don't know who is going to own it after 1.1.
JD: I'm willing to take on the Core AAM editorship, but NOT until 1.1 is done.
<clown> https://www.w3.org/WAI/ARIA/track/products/23
<clown> https://www.w3.org/Bugs/Public/buglist.cgi?component=Core%20AAM&product=ARIA
JD: I'm behind on ATTA work, I
have implementations to do in WebKitGtk, I have regressions
introduced by others I have to debug and fix....
... However, I think I actually know more about the mappings
and implementation than I do the authoring (hence my lousy
examples in the ARIA spec.) ;)
... So given that the ARIA spec practice has been for people to
make branches which I merge after consensus has been reached, I
think I can take on the Core AAM (after 1.1).
Group: (Discussion about Tracker versus Github)
RS: Let's say we finish these
issues in github that are for 1.1.
... Joseph, you can tell your employer that we will try to
phase you out and phase Joanie in.
... The exact timeline remains to be determined.
action-2117
<trackbot> action-2117 -- Joseph Scheuhammer to Update core-aam to not expose aria-details relationships that reference elements that are hidden. -- due 2016-09-22 -- PENDINGREVIEW
<trackbot> http://www.w3.org/WAI/ARIA/track/actions/2117
RS: You showed that one to us.
JS: Yes I did.
RS: Close it.
... Now you only have nine.
<clown> https://www.w3.org/WAI/PF/Group/track/products/26
JS: There's also the AccName spec.
JD: (only half-joking) Wait, a minute....
<clown> https://www.w3.org/WAI/ARIA/track/products/26
RS + JS: That used to be part of the Core AAM, but was pulled out to be referenced by other specs.
JS: Somebody and some point moved
a bunch of items from the ARIA tracker to AccName without any
explanation.
... Also Cynthia raised a number of issues because Microsoft
was having trouble implementing it and needed more
information.
... Cynthia wanted a list, specific to SVG. But that doesn't
belong in the AccName because that is host-language
independent.
This is scribe.perl Revision: 1.152 of Date: 2017/02/06 11:04:15 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) Succeeded: s/Phillipe// Found embedded ScribeOptions: -final *** RESTARTING DUE TO EMBEDDED OPTIONS *** Default Present: Joanmarie_Diggs, Joseph_Scheuhammer, Rich_Schwerdfeger Present: Joanmarie_Diggs Joseph_Scheuhammer Rich_Schwerdfeger Regrets: Bryan_Garaventa Found Scribe: joanie Inferring ScribeNick: joanie Found Date: 21 Mar 2017 People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]