See also: IRC log
<trackbot> Date: 17 March 2015
<clown> agenda: this
<clown> brb
<scribe> scribe: joanie
<clown> action-1554?
<trackbot> action-1554 -- Cynthia Shelly to Provide UIA mapping for role="searchbox" -- due 2015-02-17 -- PENDINGREVIEW
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1554
JS: This is a holdover from last
week.
... I have written up all the mappings for searchbox and wanted
verification from everyone that the mappings are correct.
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-searchbox
JS: I am waiting to hear back from Cynthia.
RS: Let me take a look.
... There is an issue here. You are probably going to want to
implement accessible text for this, also for IA2.
JS: I got this from Surkov.
RS: I don't think he was thinking about the interface when you asked.
<clown> "The object represents selectable text that allows edits or is designated read-only"
<clown> rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-textarea
JD: I see that the mapping does
not say anything about needing to implement the accessible text
interface.
... And yes, the accessible text interface does need to be
implemented.
... I'm questioning if it needs to be specified for each of
these mappings.
... Because all text objects should implement the accessible
text interface.
JS: I think you're right that for IA2 we need to add a statement about multiline versus singleline.
RS: I think you also need to add that the text interface needs to be implemented.
JS: I just typed it in earlier (reads)
RS: That's great, but how do you know where the caret is, what text is selected, etc.?
JS: I'm happy to update the mappings to mention that the accessible text interface needs to be implemented for searchbox and textbox.
JD: Makes sense to me, though from scanning through the mappings, I see a number of cases where interfaces are not mentioned at all.
RS: Perhaps Alex Surkov can provide you with a list of the roles which implement accessible text and editable text.
JS: I know there's an issue in
the HTML mapping spec where Jason asked if we should add all
the interfaces.
... This first topic was about the UIA mappings. We've gotten
far away from that.
<cyns> having phone trouble
Zakim: take up item 6
<clown> action-1533
<trackbot> action-1533 -- Joanmarie Diggs to Investigate and possibly create a minimal/skeleton javascript at-spi2 listener with the aim of automating the 1.1 tests. -- due 2015-03-03 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1533
JD: Make it 1 May please.
JS: Done.
<clown> action-1542?
<trackbot> action-1542 -- Joanmarie Diggs to Verify the commit for mozilla bug 1013584 and report the atk role to joseph. -- due 2015-02-24 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1542
JD: No updates.
<clown> action-1515?
<trackbot> action-1515 -- Richard Schwerdtfeger to Discuss issue-678 at the mon aria teleconference. -- due 2015-02-24 -- CLOSED
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1515
JD: I'll ping them I guess. They've not done anything on that bug.
JS: I make it 1 May as
well.
... This is also related to action-1515.
JD: We'll see where they are in May.
<clown> action-1554?
<trackbot> action-1554 -- Cynthia Shelly to Provide UIA mapping for role="searchbox" -- due 2015-02-17 -- PENDINGREVIEW
<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
JS: We discussed this last week.
You (Cynthia) said give you a week to look it over.
... The text in the spec is based on the notes you gave me.
CS: That looks fine.
<clown> issue-692?
<trackbot> issue-692 -- Map role="searchbox" -- raised
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/692
JS: This action is also
associated with issue-692.
... Now that all the actions are closed, I think we can close
issue-692.
... Any objections?
CS and RS: None.
JS: I'll add something about implementing accessible text for some of the platforms for searchbox.
<clown> action-1444?
<trackbot> action-1444 -- Joseph Scheuhammer to Update atk/at-spi2 mapping for role presentation in tables and lists. -- due 2015-02-24 -- PENDINGREVIEW
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1444
JS: This is more than just ATK/AT-SPI2.
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-presentation
JS: I put some text in the
presentation role regarding presentation tables and
lists.
... The URL is above.
<clown> For objects that have required owned descendants (e.g., a grid owns gridcells, a list owns listitems), expose each leaf descendant as ROLE_SECTION.
JS: I put it in for ATK and UIA, customizing it for each platform (ROLE_SECTION for ATK, Text Pattern for UIA).
CS: Document structure is very different for UIA.
<clown> For objects that have required owned descendants (e.g., a grid owns gridcells, a list owns listitems), expose each leaf descendant using the text pattern.
JS: Above is the text for UIA.
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-presentation
JS: Now that I'm looking at it, I'm wondering why there are not similar sentences for UIA Express and IA2.
action-1444
<trackbot> action-1444 -- Joseph Scheuhammer to Update atk/at-spi2 mapping for role presentation in tables and lists. -- due 2015-02-24 -- PENDINGREVIEW
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1444
JD: That looks good to me.
JS: Then I will close this action.
<clown> action-1445?
<trackbot> action-1445 -- Cynthia Shelly to Investigate the ideal uai mapping for role presentation in tables and lists. -- due 2015-01-20 -- PENDINGREVIEW
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1445
issue-661
<trackbot> issue-661 -- UAIG1.1: Specify how to map children of table/lists with role presentation. -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/661
JS: Is what I've done for UIA sufficient? (This is for action-1445)
CS: Yes.
JS: Then I was close action-1445
as well.
... What's left on the issue is action-1311 which is the bigger
issue related to panels and groups.
... We're waiting on the ARIA caucus to finish that work.
<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-03-15 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1104
CS: I haven't done anything with this yet, though I'm talking to people internally.
JS: April 7th?
CS: Yes.
action-1309
<trackbot> action-1309 -- Cynthia Shelly to Determine the best place to map aria-colindex and aria-rowindex for msaa+uiexpress and uia. -- due 2015-03-10 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1309
JS: This one is about mapping
aria-colindex and aria-rowindex.
... Does this related to the current discussion about rowcount,
etc.?
RS: Yes. There's a computation aspect to these.
CS: When do you think this is going to stablize?
RS: Tables are big enough, we probably are looking at a month.
CS: So give me that month, plus a week.
RS: We should get the tables and panels, and then do a heartbeat for the spec.
JS: Also aria-current.
RS: And that includes
mappings.
... 1st week of May?
JS: It should be doable.
(Group agrees)
RS: I'll mention this on Thursday's call.
JS: We're going to need mappings for rowindex, colindex, etc. for all the platforms.
RS: Yes we are.
<clown> https://developer.gnome.org/libatspi/2.13/libatspi-atspi-table.html
<clown> action-1373?
<trackbot> action-1373 -- Cynthia Shelly to Create a test case for when aria-posinset and aria-setsize are provided explicitly on some but not all elements. -- due 2015-02-23 -- OPEN
<trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1373
JS: Another one for Cynthia! :)
<clown> issue-441?
<trackbot> issue-441 -- Normative UAIG requirements for what UAs do when aria-posinset or aria-setsize is provided explicitly on some, but not all, elements within a set. -- open
<trackbot> https://www.w3.org/WAI/PF/Group/track/issues/441
CS: Give me a week on this one.
JS: The 24th.
<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: The mappings for rowgroup.
RS: Wasn't Alex going to do this?
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-rowgroup
JS: Did you ask him in that email?
<clown> https://lists.w3.org/Archives/Public/public-pfwg/2015Feb/0060.html
JS: The above link is the
email.
... His answer is that I only see one use for role
rowgroup.
... (Reads Alex's response from the email)
RS: Nobody else maps it.
JS: He does seem to be saying he wants to map it.
<clown> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-rowgroup
RS: Is he the only one who wants to map it?
JS: Here (above) are the current
mappings.
... (Reads from mappings)
... ATK doesn't map it and AX API doesn't map it.
... So two map it, and two don't.
... Is that right for UIA, Cynthia?
CS: Yes.
... There's a larger issue here. I think we actually need a
synonym for group that is not the generic group.
JD: Will the new panel role address that?
CS: Possibly.
JS: Another point Alex makes:
Firefox doesn't expose tbody, thead, etc. as accessibles unless
the author makes them focusable.
... If the author makes it focusable, then there needs to be an
accessible for it.
RS: If a rowgroup had a role of group, it wouldn't really matter would it?
JS: No.
RS: There you go.
JS: Should the mapping table have that exception, namely not mapped unless focusable in which case it has the group role?
RS: I think so, though I'd like to hear other people's thoughts on it.
JD: If it has to be exposed, I guess that's the way to go. But it's going to mess up the hierarchy.
JS: Is the conclusion that we're willing to accept this mapping if the rowgroup is focusable?
(Group agrees)
JS: I'll create a branch of the mapping spec, named according to the issue number (700), and put that text in and we can revisit it next week.
<clown> https://lists.w3.org/Archives/Public/wai-xtech/2015Mar/0004.html
Read https://lists.w3.org/Archives/Public/wai-xtech/2015Mar/0004.html
<clown> yes, read the thread.
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) Found Scribe: joanie Inferring ScribeNick: joanie Default Present: Joseph_Scheuhammer, Joanmarie_Diggs, Rich_Schwerdtfeger, +1.650.738.aaaa, Bryan_Garaventa, cyns, Cynthia_Shelly Present: Bryan_Garaventa Cynthia_Shelly Joanmarie_Diggs Joseph_Scheuhammer Rich_Schwerdtfeger Regrets: David_Bolter Found Date: 17 Mar 2015 Guessing minutes URL: http://www.w3.org/2015/03/17-aapi-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]