See also: IRC log
<trackbot> Date: 17 February 2015
<clown> agenda: this
<scribe> scribe: joanie
JS: David was going to work on this. I heard from him, he cannot come to the meeting.
<clown> action-980?
<trackbot> action-980 -- David Bolter to Describe/define managed aria related states: aria-setsize, aria-posinset, aria-level, focused, focusable with reference to section 5.5 bullet 1 of the UAIG. -- due 2015-01-27 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/980
JS: Anyone else want to discuss this?
RS: I don't quite
understand.
... Ok, it basically wants to say how the browser manages these
states if they are missing.
JS: The current text in the
mapping guide is vague with respect to what happens if the
states are absent.
... David volunteered to take this up.
... I periodically ping David; he's still working on it.
... It was raised, I believe, at a face-to-face meeting.
... David indicated he wants to come up with a list of managed
states.
... I'll ping him again.
... We might still be able to get it in for 1.1.
JS: Cynthia is not here (yet).
<clown> action-1104?
<trackbot> action-1104 -- Cynthia Shelly to Define what the accessibility API mapping is for UIA on aria-describedby in section 5.5.1 table when the element does not exist in the accessibility tree such as when css: display:none applies -- due 2015-02-10 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1104
JS: You can have an
aria-describedby that has display:none on it.
... As far as UIA is concerned, this means the description
doesn't exist.
... Other APIs allow you to expose the description text.
... I did see a number of emails about this about a month
ago.
... I think Steve and Marco were encouraging them to use MSAA
accDescription.
... But I believe Cynthia said they had some problems with
that.
RS: In the past, perhaps due to poor documentation, people were misusing this property.
JS: Maybe what we need to do is fix the Microsoft documentation.
<clown> issue-700?
<trackbot> issue-700 -- Discuss rowgroup, tbody, and thead in aapis -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/700
<clown> action-1544?
<trackbot> action-1544 -- Cynthia Shelly to Document rowgroup mappings for ie 11 for both uia express and uia -- due 2015-02-03 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1544
<clown> action-1546?
<trackbot> action-1546 -- David Bolter to Make sure the rowgroup mapping for msaa/ia2 is accurate -- due 2014-12-23 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1546
JS: This issue relates to action-1544 and action-1546.
RS: Let me see if I can get Alex to join us.
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-rowgroup
<clown> action-1546?
<trackbot> action-1546 -- David Bolter to Make sure the rowgroup mapping for msaa/ia2 is accurate -- due 2014-12-23 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1546
JS: David said last week that he wanted to talk to Alex about it.
RS: I'm going to email Alex about it.
<clown> http://www.w3.org/2015/02/10-aapi-minutes.html#item07
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-rowgroup
JS: (Reads from the above)
... MSAA and UIA Express expose the role as a property, which
means there is an accessible there.
... IA2 exposes it as ROLE_SYSTEM_GROUP.
RS: Actually, that's probably ok, right?
JS: UIA exposes it as 'group'
RS: Which also means nothing.
JS: ATK and AXAPI do not map it.
There is no accessible.
... I think the interoperability issue is if an accessible
should be there at all.
RS: (Finishes email to Alex and CCs David)
<clown> action-980
<trackbot> action-980 -- David Bolter to Describe/define managed aria related states: aria-setsize, aria-posinset, aria-level, focused, focusable with reference to section 5.5 bullet 1 of the UAIG. -- due 2015-01-27 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/980
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#statePropertyMappingGeneralRules
<clown> item 1 at that URL
(The above are related to the email being written)
<richardschwerdtfeger> https://lists.w3.org/Archives/Public/public-pfwg/2015Feb/0054.html
RS: The above is the message I sent.
action-1554
<trackbot> action-1554 -- Cynthia Shelly to Provide UIA mapping for role="searchbox" -- due 2015-02-10 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1554
JS: I was asking for mappings for
the new searchbox role.
... Cynthia has not yet been able to join us.
... We've got a mapping for ATK/AT-SPI2.
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-searchbox
JS: That's the only one so
far.
... Cynthia, we're working on the mapping for
role="searchbox"
<clown> action-1554
<trackbot> action-1554 -- Cynthia Shelly to Provide UIA mapping for role="searchbox" -- due 2015-02-10 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1554
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-searchbox
CS: We would use the editabletext pattern and a localizable control type. So just like an input, but the string would say "search box".
RS: So I guess for CR, we're only going to test for English mappings.
CS: I'm updating the action now.
JS: When you're done, assign it to me and I'll put in the mapping spec.
JD: Was this added to the email Rich sent?
JS: Nothing about searchbox or
switch.
... The same thing (mapping for searchbox) is needed for
MSAA/IA2.
... This is David's action.
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-switch
JS: We have mappings for UIA and ATK/AT-SPI2. Not IA2 or AX API.
JD: I need to do a patch for the
ATK mappings in WebKit.
... When I do so, I'll have to deal with the mapping for AX
API, so I may be able to get us mappings for that platform as
well.
... In which case I'll update James' actions.
<clown> action-1104?
<trackbot> action-1104 -- Cynthia Shelly to Define what the accessibility API mapping is for UIA on aria-describedby in section 5.5.1 table when the element does not exist in the accessibility tree such as when css: display:none applies -- due 2015-02-10 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1104
JS: This is aria-describedby pointing to something with display:none.
CS: We're still working on it.
JS: I mentioned earlier that Steve Faulkner and Marco Zehe suggested accDescription.
CS: That's gone now.
... We're talking about adding something like it.
JS: So what do we want to do? Set the date further out?
CS: March 15th.
<clown> action-1569?
<trackbot> action-1569 -- Jason Kiss to Create a section that describes AAPI differences -- due 2015-03-03 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1569
JS: This is something Jason Kiss
wanted to do.
... He did do it, but it's on a special branch.
... The email was sent here:
<clown> http://rawgit.com/w3c/aria/issue-540/core-aam/core-aam.html#comparing-accessibility-apis
JS: He's basically copied a note I'd written about ATK versus AT-SPI. Then added content about names and descriptions.
(Group reads)
CS: With respect to 1.3.1 there's
a lot of differences between how UIA and the other
Accessibility APIs work.
... For example, patterns.
... You can give me an action to provide some of this
information.
<clown> ACTION: Cynthia to add to the section on differences among AAPIs highlighting the features of UIA. [recorded in http://www.w3.org/2015/02/17-aapi-minutes.html#action01]
<trackbot> Created ACTION-1585 - Add to the section on differences among aapis highlighting the features of uia. [on Cynthia Shelly - due 2015-02-24].
<clown> action-1585?
<trackbot> action-1585 -- Cynthia Shelly to Add to the section on differences among aapis highlighting the features of uia. -- due 2015-02-24 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1585
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/ping him/ping David/ Succeeded: s/accdescription(?sp)/MSAA accDescription/ Succeeded: s/I think the interoperability issue there is if an accessible should be there at all./I think the interoperability issue is if an accessible should be there at all./ Succeeded: s/localizable role/localizable control/ Succeeded: s/ugh// Succeeded: s/timie// Succeeded: s/time yes// Found Scribe: joanie Inferring ScribeNick: joanie Default Present: Joseph_Scheuhammer, Bryan_Garaventa, Rich_Schwerdtfeger, Joanmarie_Diggs, Cynthia_Shelly Present: Joseph_Scheuhammer Bryan_Garaventa Rich_Schwerdtfeger Joanmarie_Diggs Cynthia_Shelly Regrets: David_Bolter Found Date: 17 Feb 2015 Guessing minutes URL: http://www.w3.org/2015/02/17-aapi-minutes.html People with action items: cynthia WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]