16:28:53 RRSAgent has joined #aria 16:28:53 logging to http://www.w3.org/2015/05/07-aria-irc 16:28:55 RRSAgent, make logs member 16:28:55 Zakim has joined #aria 16:28:57 Zakim, this will be WAI_PF 16:28:57 ok, trackbot; I see WAI_PFWG()12:30PM scheduled to start in 2 minutes 16:28:57 Stefan has joined #aria 16:28:58 Meeting: Protocols and Formats Working Group Teleconference 16:28:58 Date: 07 May 2015 16:29:00 WAI_PFWG()12:30PM has now started 16:29:02 chair: Rich 16:29:08 +Fred_Esch 16:29:12 meeting: W3C WAI_PF ARIA Caucus 16:29:18 fesch has joined #aria 16:29:25 +Stefan_Schnabel 16:29:38 RRSAgent, make log public 16:29:46 +??P3 16:29:49 +Joanmarie_Diggs 16:29:56 +Rich_Schwerdtfeger 16:29:59 zakim, who's on the phone? 16:29:59 On the phone I see Fred_Esch, Stefan_Schnabel, ??P3, Joanmarie_Diggs, Rich_Schwerdtfeger 16:30:06 zakim, ??P3 is me 16:30:06 +janina; got it 16:31:21 mgylling has joined #aria 16:31:33 http://www.justice.gov/sites/default/files/opa/press-releases/attachments/2015/04/02/edx_settlement_agreement.pdf 16:32:29 https://lists.w3.org/Archives/Public/public-pfwg/2015May/0047.html 16:33:22 +Markus 16:34:06 +ShaneM 16:34:11 zakim, mute me 16:34:11 ShaneM should now be muted 16:34:57 : http://www.justice.gov/sites/default/files/opa/press-releases/attachments/2015/04/02/edx_settlement_agreement.pdf 16:36:06 +??P7 16:36:27 -ShaneM 16:36:44 +??P6 16:37:21 zakim, ??P7 is me 16:37:21 +ShaneM; got it 16:37:34 ack me 16:37:53 jamesn has joined #aria 16:38:22 scribe: MichaelC 16:38:23 +Matt_King 16:38:50 agenda: https://lists.w3.org/Archives/Public/public-pfwg/2015May/0047.html 16:38:54 ack me 16:39:04 mattking has joined #aria 16:39:34 topic: Zakim decomissioning 16:39:40 js: Zakim bridge will be turned off due to cost 16:40:01 switching to WebEx, which has no marginal cost to W3C because of MIT agreement 16:40:15 will still use the Zakim bot in IRC, but it won´t identify callers 16:40:22 have to transition within a few weeks 16:41:03 Web interface to WebEx not terribly accessible 16:41:08 but smartphone clients seem to be 16:41:29 need to test out soon 16:41:30 ack me 16:41:38 +James_Nurthen 16:43:15 mc: you can dial out, request it call you, or use its VOIP feature 16:43:29 best to install the client before the meeting starts 16:44:13 mk: what about passcodes? 16:44:44 mc: different passcode for each meeting 16:45:37 but a given meeting can have the same passcode week to week 16:45:50 https://www.w3.org/WAI/PF/Group/track/issues/709 16:45:58 rs: issue with passcode collision with different dial-in numbers? 16:46:12 mc: afaik it´s a global system, no passcode collision 16:46:20 topic: Issue 709 Define an Extension Mechanism for ARIA roles 16:46:32 https://lists.w3.org/Archives/Public/public-pfwg/2015Apr/0160.html 16:49:08 rs: ^ starting proposal 16:50:02 mk, rs: 16:50:10 rs: need AAPI mappings for new roles 16:50:15 some things may not map 16:50:36 mk: in which case how does it pass CR? 16:50:41 q+ 16:51:17 q+ To talk about what all "mapping" might mean wrt exposure 16:51:36 mg: implementations needn´t be limited to browsers 16:51:46 an epub reader could be a valid test target for DPub roles 16:52:07 though guess we want to check with W3C process 16:52:21 jnurthen has joined #aria 16:52:21 rs: think we´d want in browsers or authoring tools 16:52:22 q+ to mention that I don't think authoring tools are relevant to CR for ARIA specs (today) 16:53:05 for ARIA 1.0 we looked for two implementions of each role in the mapping table 16:53:18 mk: note we didn´t look at AT implementation 16:54:08 mg: publishers are interested in other things than AT mapping 16:54:19 doing element repurposing 16:54:25 affects authoring more than rendering 16:54:42 rs: benefits a11y for AU tools to support that 16:55:22 mg: but for CR, not necessarily expecting to measure AAPI mappings, if there are other things of interest to measure 16:55:38 q+ 16:55:53 rs: think there should be AAPI mappings for DPub extension 16:55:57 ack me 16:56:22 q? 16:57:37 mc: W3C process doesn´t force certain interpretation of CR 16:57:46 ack joanie 16:57:46 joanie, you wanted to talk about what all "mapping" might mean wrt exposure 16:58:02 we´ll have to decide in our extension planning whether AAPI mappings is a hard requirement 16:58:15 jd: @@ 16:58:25 q? 16:58:33 ack ShaneM 16:58:33 ShaneM, you wanted to mention that I don't think authoring tools are relevant to CR for ARIA specs (today) 16:58:33 ack ShaneM 16:58:49 sm: don't think authoring tools are relevant to CR for ARIA specs (today) 16:59:12 we have avoided conformance requirements targeting AU tools 16:59:17 what sort of things are not mapped? 16:59:30 rs: rowgroup wasn´t mapped in 1.0 (for one platform) 16:59:45 sm: what does that mean? 16:59:59 rs: the ARIA role was discarded on that platform 17:00:22 sm: my proposal is any new roles have to map into taxonomy 17:00:24 s/@@/In cases where things are "not mapped" (e.g. to a specific role), they can still be exposed (e.g. via an object attribute). This exposure to accessibility APIs would make it possible to implement, and verify implementation of, items in extensions like DPUB. 17:00:40 RRSAgent, make minutes 17:00:40 I have made the request to generate http://www.w3.org/2015/05/07-aria-minutes.html joanie 17:00:41 so what you´re saying isn´t about that, it´s about AAPI mapping 17:00:43 rs: right 17:00:53 important to tell AT what to do 17:01:14 mk: if an extension didn´t have a mapping, what value does it bring? 17:01:35 rs: platforms are different 17:01:36 +q 17:01:50 mk: but what about if no mapping on any platform? 17:01:59 q+ To reiterate what she was saying, in response to Matt's current question. 17:02:17 q+ to talk about speculative mapping 17:02:38 rs: example: role=¨part¨ 17:02:52 doesn´t help AT, but helps authors, or someone doing landmark navigation 17:03:01 helps to have the semantics present 17:03:05 q? 17:03:10 ack jo 17:03:10 joanie, you wanted to reiterate what she was saying, in response to Matt's current question. 17:03:40 jd: say ¨part¨ was really important for AT 17:03:56 there could be an object attribute, that an authoring tool could get at even though not a direct AAPI feature 17:04:00 q- 17:04:08 jamesn has joined #aria 17:04:31 rs: one API turns on ¨isLandmark¨ but doesn´t expose specific role 17:04:46 mk: something with 0 exposure has no value 17:05:12 still need *something* defined 17:05:16 q? 17:05:20 jd: yup 17:05:26 the DAAM would provide that 17:05:39 17:05:46 ack janina 17:05:57 js: we can negotiate CR exit criteria 17:06:32 and global requirements are fairly loose, there´s room for negotiation 17:06:54 some of it depends on the specific wordign we choose for the spec 17:07:29 just need to demonstrate something reliably happening 17:07:41 there may be cascading situations where need to test more than 2 to work out the permutations 17:07:44 q+ 17:07:46 q? 17:07:50 ack Stefan 17:08:37 ss: @@ extensions properties 17:08:51 rs: the properties mechanism might be more owrk 17:08:53 q? 17:09:17 ss: what about expandable region descending from region? 17:09:33 general case of pattern taken from base role 17:09:34 rs: that´s ARIA 2.0 17:09:42 we´re just dealing with name conflicts now 17:09:53 q+ to ask why new roles cannot add other states or properties that are already defined? 17:09:58 ack me 17:09:59 Michael_Cooper, you wanted to talk about speculative mapping 17:10:03 ack Michael_Cooper 17:10:53 mc: we might want roles that map to features that don´t yet exist 17:11:11 rs: don´t want to throw stuff over the wall 17:11:56 mc: in that case we would say ¨expose an object attribute¨ 17:11:57 +Cynthia_Shelly 17:11:58 ack mgylling 17:12:15 but might want to say ¨we´d love a more direct feature¨ 17:12:37 newtron has joined #aria 17:12:42 mg: we can provide mappings in the DPub-AAM for DPub roles 17:13:04 some of the mappings might be the same as ancestor roles in the taxonomy 17:13:15 q+ To ask about - vs : as the myvocab separator 17:14:16 q? 17:14:16 q? 17:14:20 ack ShaneM 17:14:20 ShaneM, you wanted to ask why new roles cannot add other states or properties that are already defined? 17:15:35 sm: if we collaborate we should be able to avoid collisions 17:16:07 we don´t yet have a way to add new states and properties in extensions 17:16:25 but can extensions use existing states and properties? 17:16:27 rs: yes 17:16:47 jn: what about new values for states and properties? 17:17:01 rs: that would change existing roles 17:17:09 jn: yet that´s needed for extensions 17:17:16 rs: lots of work to do on that level of extensibility 17:17:25 ack me 17:18:00 q? 17:18:07 mc: I´m hearing we have 2 extensibility levels now 17:18:11 a full fledged one for ARIA 2 17:18:23 and some immediate needs that are more constrained 17:18:34 let´s sort what goes into which bucket 17:18:41 and then focus on supporting the immediate case 17:19:20 rrsagent, make minutes 17:19:20 I have made the request to generate http://www.w3.org/2015/05/07-aria-minutes.html janina 17:19:49 mk: did you mean to be so specific in extension restrictions? 17:20:15 sm: HTML 5 constrains us, can´t use full extensibility features of the Role Attribute 17:20:26 so we have to sort out what to do in a single namespace 17:22:19 rs: which is why we have aria-* for properties 17:22:31 mk: problem with multiple hyphens in a property name? 17:22:45 rs: expect to use vocab-aria-property pattern 17:23:02 a lot more to sort before we get there 17:23:10 ack me 17:23:29 ack mattking 17:23:29 mattking, you wanted to ask about - vs : as the myvocab separator 17:23:33 I don't mind using aria-foo-stateName for extensions... 17:25:02 mc: why ¨MAY¨ descend from existing taxonomy 17:25:48 sm: so not constrained by existing taxonomy, if it lacks features 17:26:01 mc: can extend from roletype at least, suggest that be must extend taxonomy 17:27:12 js: we need a thorough consensus test on this 17:27:21 mc: yes, plus we also need really solid documentation 17:27:29 q+ to say I dont think this proposal addresses the core issue 17:27:47 we spent an hour discussing questions on the proposal, need to give more specific answers to DPub to allow them to restart work 17:27:54 mg: don´t have that clarity just yet 17:28:00 want to avoid getting deadlocked again 17:29:00 ack s 17:29:00 ShaneM, you wanted to say I dont think this proposal addresses the core issue 17:29:02 ack ShaneM 17:29:06 ack Michael_Cooper 17:29:13 q? 17:29:14 mk: would this go in the ARIA spec? 17:29:15 sm: no 17:29:19 mg: why? 17:29:48 sm: the core issue that came up after proposal went out 17:29:53 q? 17:29:55 q+ 17:29:56 is that people want to propose roles without semantic value 17:30:08 that´s not an extension issue, that´s a ¨what is role for¨ issue 17:30:26 we need a way for people to be able to add roles and not be called idiots 17:30:28 q+ To ask if the way forward is the new AAM 17:30:43 js: so we may need to have that ¨what is role for¨ discussion as well 17:30:55 need to have something solid before we tell DPub to go ahead 17:31:02 ack r 17:31:33 rs: some of the discussion on DPub echoed our past experience trying to put ARIA in HTML 17:31:51 we´re not the DPub experts and don´t think we should bottleneck the work of those who are 17:32:09 +1 to our not being DPub experts 17:32:17 Hypenation is NOT the issue here 17:32:29 s/Hypenation/Hyphenation/ 17:32:30 yes, the issue of hyphenated role values was an issue 17:32:42 but other discussion of valid roles is beyond our scope 17:33:07 DPub should be welcome to define roles 17:33:09 q? 17:33:12 q+ 17:33:14 ack joanie 17:33:14 joanie, you wanted to ask if the way forward is the new AAM 17:33:17 we just need to sort out potential collisions if they want un hyphenated role names 17:33:33 jd: is the next step to work on the DAAM? 17:33:38 q- 17:33:48 think would find some really interesting stuff there 17:33:49 q+ 17:33:56 q+ to ask how the mapping is different than saying what the parent role and additional properties are? 17:34:00 maybe that would address philosophical problems 17:34:01 ack me 17:34:06 ack Michael_Cooper 17:35:05 mc: concern that you can´t have mappings without something to map from 17:35:13 wanted to put up roles, then map them 17:35:24 could work on the roles and mappings together, but would be a while to publishing 17:35:34 they were trying to go step by step 17:35:38 jd: but it didn´t work out 17:35:45 ack me 17:35:45 ShaneM, you wanted to ask how the mapping is different than saying what the parent role and additional properties are? 17:35:46 ack ShaneM 17:35:48 should find paths forward that don´t depend on FPWD 17:36:09 sm: what does the mapping offer? 17:36:43 jd: let´s take example of a footnote 17:36:47 would love to add that to ATK 17:36:57 could work on that while people debate the merits of footnotes 17:37:11 sm: we do want to avoid implementation before we have basic agreement on the structure 17:37:20 or we get boxed in with future directions 17:37:25 that happened in ARIA 1.0 17:37:33 rs: there is always something sub-optimal 17:37:43 mk: tend to take FPWD as signal to start exploring implementation 17:37:55 js: need to think through the consequences carefully 17:38:49 there are legitmate clashes from different vocabularies 17:38:55 q+ 17:39:33 For the record, I'm not a blocking person. 17:39:38 but we can´t rewrite centuries of usage of a particular term 17:40:06 need to figure out how to accomodate the legit clashes 17:40:18 q+ was there any objection to dpub-part? 17:40:37 cs: prototyping can be a good way to play with implementation without being over-committed 17:40:42 ack r 17:40:52 rs: want to prevent negative interaction with DPub TF 17:41:05 we´re not going to redefine the publishing industry 17:41:46 straw proposal - if a group puts role values in their own hyphenspace, we should not push back on the role 17:42:12 (though have to talk about it if incorporating into ARIA core roles) 17:42:20 q+ to say I agree with Rich but dont think it would solve the problem 17:42:41 jn: no concerns if its in their hyphenspace, but original proposal was to put in the null hyphenspace 17:42:42 ack ShaneM 17:42:42 ShaneM, you wanted to say I agree with Rich but dont think it would solve the problem 17:43:04 sm: the core issue that came up was ¨this does not add to a11y¨ 17:43:08 we are not in a position to say that 17:43:49 jn: it´s not a correct argument that was brought up 17:43:56 knowing what something is makes it easier to get to it 17:44:06 q? 17:44:22 q+ 17:44:23 sighted people have been doing this since Gutenberg, screen reader users only since DAISY 17:44:54 rs: proposed resolution: If a group wants to put roles in their own hyphenspace, they have last say in what goes there 17:45:17 mg: there was a discussion about scope of the role attribute 17:45:23 is it only a11y, or is it more generic? 17:45:43 have heard one thing, but also had W3C staff blatantly ignoring it 17:45:53 q+ 17:45:58 ack m 17:46:01 +1 to needing a positive statement from the PFWG about the scope of role values. 17:46:39 js: think it´s a political argument, that it´s beyond mandate of PFWG to propose non-a11y roles 17:46:45 q+ 17:46:53 q+ to compare HTML role from Role Attribute 17:47:24 whereas our POV has been to invite people to take curbcut advantage of things like this 17:47:34 mg: but get a different answer from HTML WG 17:47:36 ack r 17:47:54 rs: as long as it doesn´t break AAPI mappings, people should be able to use from beginning 17:48:10 ack Michael_Cooper 17:48:10 Michael_Cooper, you wanted to compare HTML role from Role Attribute 17:49:55 sm: yes, long post on HTML list 17:49:57 ack me 17:50:11 mc: PF published Role Attribute which clearly invites non a11y roles 17:50:14 so we have precedent 17:50:24 but have to negotiate with HTML inclusion of values in the HTML role attribute 17:50:36 which only accepts ¨ARIA roles¨ 17:51:16 could put us in a situation of needing to define ¨a11y ARIA roles¨ and ¨other recognized roles¨ - which might be helfpul or anathema 17:51:34 Action: Shane work with Rich on updated process for creating new role value taxonomy extensions 17:51:34 Created ACTION-1633 - Work with rich on updated process for creating new role value taxonomy extensions [on Shane McCarron - due 2015-05-14]. 17:51:36 rs: SM, let´s work it up again 17:51:43 mk: @@ 17:52:22 sm: HTML 5 has an extension mechanism, we need an extension mechanism 17:52:26 -ShaneM 17:52:35 mc: thought the HTML on is very informal, doens´t say how conflicts managed 17:53:01 topic: Review Open Action Items and Issues 17:53:48 rs: there are lots of actions that are not gettign done 17:53:55 need to assign some of them 17:53:55 -Markus 17:54:03 action-1073? 17:54:03 action-1073 -- Matthew King to Update aria-selected to reflect that it communicates selectability and clarify responsibility for ensuring aria-selected=false is on selectable elements -- due 2015-03-26 -- OPEN 17:54:03 https://www.w3.org/WAI/PF/Group/track/actions/1073 17:54:14 https://www.w3.org/WAI/PF/Group/track/actions/1073 17:55:00 mk: ??? 17:56:06 https://rawgit.com/w3c/aria/master/aria/aria.html#aria-current 17:56:47 rs: looking at actions for aria-current 17:56:52 mk, jd: think they´re done 17:57:01 In some use cases for widgets that support aria-selected, current and selected can have different meanings and can both be used within the same set of elements. For example, aria-current="page" can be used in a navigation tree to indicate which page is currently displayed, while aria-selected="true" indicates which page will be displayed if the user activates the treeitem. Furthermore, the same tree may support operating on one or more selected pages 17:57:01 (treeitems) by way of a context menu containing options such as "delete" and "move." 17:58:03 close action-1573 17:58:04 Closed action-1573. 17:59:29 action-1363? 17:59:29 action-1363 -- James Craig to Patch issue-603: aria-startsmedia -- due 2015-03-12 -- OPEN 17:59:29 https://www.w3.org/WAI/PF/Group/track/actions/1363 17:59:33 rs: JD, can you take this? 17:59:49 jd: I don´t agree with it, think someone who agrees with it should work on it 18:00:24 mk: could move to ARIA 2 18:00:44 jn: or propose ¨wontfix¨ 18:01:05 rs: will move issue-603 to ARIA 2.0 18:01:58 rs: out of time; enough to bring up for next week? 18:02:07 jd: do we need to start thinking ARIA 1.2? 18:02:58 rs: bigger discussion 18:04:18 rs: for heartbeat, want @@ in the spec 18:05:00 -James_Nurthen 18:05:05 mc: I have to start publication prep Monday, and need a WG consensus by Wednesday 18:05:09 and all that is pushing the timeline 18:05:40 js: we don´t know if we can publish for a while, if we don´t publish by 14 May, because charter discussion is not closed 18:05:53 jd: MK and I will try hard to do it for Monday 18:06:09 -Cynthia_Shelly 18:06:09 js: everyone please vote on the Authoring Practices FPWD 18:06:11 -Rich_Schwerdtfeger 18:06:11 -Matt_King 18:06:16 -Michael_Cooper 18:06:18 -Joanmarie_Diggs 18:06:18 -janina 18:06:28 -Fred_Esch 18:06:38 zakim, list attendees 18:06:38 As of this point the attendees have been Fred_Esch, Stefan_Schnabel, Joanmarie_Diggs, Rich_Schwerdtfeger, janina, Markus, ShaneM, Michael_Cooper, Matt_King, James_Nurthen, 18:06:41 rrsagent, make minutes 18:06:41 I have made the request to generate http://www.w3.org/2015/05/07-aria-minutes.html MichaelC 18:06:41 ... Cynthia_Shelly 18:07:00 rrsagent, make log world 18:07:10 rrsagent, make minutes 18:07:10 I have made the request to generate http://www.w3.org/2015/05/07-aria-minutes.html MichaelC 18:10:43 -Stefan_Schnabel 18:10:44 WAI_PFWG()12:30PM has ended 18:10:44 Attendees were Fred_Esch, Stefan_Schnabel, Joanmarie_Diggs, Rich_Schwerdtfeger, janina, Markus, ShaneM, Michael_Cooper, Matt_King, James_Nurthen, Cynthia_Shelly 19:19:17 newtron has joined #aria 19:20:49 newtron_ has joined #aria 20:22:51 newtron has joined #aria 20:27:01 Zakim has left #aria 20:53:10 newtron has joined #aria 20:54:06 newtron_ has joined #aria 21:27:32 richardschwerdtfeger has joined #aria 21:48:48 richardschwerdtfeger has joined #aria 21:50:42 ShaneM_ has joined #aria 22:04:20 newtron has joined #aria 22:06:25 newtron has joined #aria 23:41:31 newtron has joined #aria 23:47:44 MichaelC has joined #aria