16:29:05 RRSAgent has joined #aria 16:29:05 logging to http://www.w3.org/2015/06/11-aria-irc 16:29:07 RRSAgent, make logs public 16:29:07 Zakim has joined #aria 16:29:09 Zakim, this will be WAI_PF 16:29:09 ok, trackbot; I see WAI_PFWG()12:30PM scheduled to start in 1 minute 16:29:10 Meeting: Protocols and Formats Working Group Teleconference 16:29:10 Date: 11 June 2015 16:29:12 chair: Rich 16:29:26 meeting: W3C WAI-PF ARIA Caucus 16:30:50 agenda: https://lists.w3.org/Archives/Public/public-pfwg/2015Jun/0022.html 16:31:19 fesch has joined #aria 16:32:00 http://lists.w3.org/Archives/Public/public-pfwg/2015Jun/0022.html 16:32:03 clown has joined #aria 16:32:09 Present+ Rich 16:32:19 present+ Fred 16:32:26 present+ Joseph_Scheuhammer 16:32:49 present+ Cynthia 16:32:51 present+ MichaelC 16:32:53 present+ Joanmarie_Diggs 16:34:50 scribe: MichaelC 16:35:06 topic: ARIA WG charter 16:35:22 -> http://www.w3.org/2015/04/draft-aria-charter Draft ARIA Charter 16:36:20 mc: should be going to AC in next week or so 16:36:42 has been approved by W3M 16:36:59 regrets+ I'm in an biannual ISO/V2 call. Will join if it ends in time 16:37:01 going in separate surveys for granular results 16:38:28 topic: Label role 16:38:30 action-1422? 16:38:30 action-1422 -- Joanmarie Diggs to Add label role (text from Matt King) -- due 2014-05-05 -- OPEN 16:38:30 https://www.w3.org/WAI/PF/Group/track/actions/1422 16:38:53 jd: have put edits in a branch, feedback so far from Joseph 16:38:59 not convinced we need the role 16:39:11 rs: not sure either but would have helped with captions 16:39:20 jd: caption isn´t a label, there are key differences 16:39:33 rs: we don´t share that view then 16:39:51 jd: there´s text saying you don´t have to use it but can if you like 16:40:04 not sure that´s strong enough reason for a role 16:40:22 rs: agree, but others wanted it to map to HTML figcaption and stuff 16:40:23 q? 16:40:43 q+ to summarize my concerns with lable role. 16:40:58 s/lable/label/ 16:41:17 present+ Bryan_Garaventa 16:41:23 ack c 16:41:23 clown, you wanted to summarize my concerns with lable role. 16:41:27 https://rawgit.com/w3c/aria/label/aria/aria.html#label 16:41:56 An element containing content that labels another element 16:42:15
...
16:42:15 16:42:41 js: my main concern is conflict between containing content, and examples that might not have content 16:42:45 present+ Stefan 16:42:55 which is all fine but the definition isn´t right then 16:43:23 either need to remove content from the definition, or not allow aria-label / aria-labelledby 16:43:27 bgaraventa1979 has joined #aria 16:43:30 jd: agree 16:43:37 this is an inheritance issue 16:43:44 rs: aria-labelledby is global 16:43:51 present+ Bryan_Garaventa 16:43:54 present+ JamesN 16:44:06 Stefan has joined #aria 16:44:31 js: which means it can be applied to any element 16:44:37 q? 16:44:39 q+ 16:44:47 would be weird to disallow it, but I don´t know the use cases enough 16:44:48 ack 16:44:50 ack r 16:45:07 rs: think aria-label aria-labelledby should stay global 16:45:09 easier to remember 16:45:17 no point making exception for a somewhat edge case 16:45:29 use cases for label: 16:45:32 caption 16:45:34 figcaption 16:46:02 but you could handle the labeling at the host language mappings level 16:46:15 to form a virtual labelledby 16:46:26 ack 16:46:28 q? 16:46:37 js, jd, rs: this is useless 16:46:45 action-1422? 16:46:45 action-1422 -- Joanmarie Diggs to Add label role (text from Matt King) -- due 2014-05-05 -- OPEN 16:46:45 https://www.w3.org/WAI/PF/Group/track/actions/1422 16:46:49 no - I agree it is useless 16:47:18 jn: the rationale was an attempt to get a 1:1 mapping between HTML 5 elements and ARIA elements 16:47:26 but don´t think it buys us anything in practice 16:47:33 cs: useful from code clarity point 16:47:51 fe: yes, simplifies some SVG cases 16:48:22 rs: if something is labelled by something else, you can put label role in the platform mapping, don´t need author to do it 16:48:57 js: I heard CS say it makes it easier for author to know what´s gonna happen 16:49:06 rs: have never seen this in the wild 16:49:24 jn: not having it doesn´t stop authors from using HTML label 16:50:10 q+ To raise concern wrt caption 16:50:32 mc: figcaption and caption label their parents; label labels something else 16:50:43 jn: not invalid to have a label in HTML that labels nothing 16:50:50 mc: probably because of limits of DTD expression 16:51:44 fe: would be weird if a label for referenced something that said it´s labelledby was something else 16:52:43 q- 16:52:46 rs: we should kill it 16:52:50 q? 16:53:02 it only helps some behind the scenes computation 16:54:31 mc: expect HTML-AAM will have to map in way to not require ARIA label role, but potentially map to a platform feature nonetheless 16:55:51 does this change any previous decisions to try to provide a comprehensive ARIA? 16:56:07 rs: best to provide roles *where they are useful* 16:56:17 js: SVG? 16:56:24 fe: it´s all groups and stuff 16:56:53 rs: we could make target of an aria-labelledby to defined as a label, but don´t see it as important 16:57:10 fe: could @@ 16:57:17 rs: we could create a label role for SVG 16:57:27 fe: hoped to piggy-back off of this in core ARIA 16:57:36 but not a big deal 16:58:06 rs: more useful to map to text 16:58:18 fe: usually you care about the text, not the symbol 16:58:28 but that may be an SVG-specific issue 16:59:46 in a chart you could have axis with major and minor tick marks, don´t want all of those to become labels 17:00:05 rs: propose that target of aria-labelledby has no mapping 17:00:13 fe: does that stop you from getting to it? 17:00:14 rs: no 17:00:25 jd: if it´s not mapped, AT can´t find 17:01:57 17:02:25 rs: in above example you would ignore the aria-labelledby 17:03:18 label 17:04:28 no, not that, I´m getting at that it´s not meaningful to put aria-labelledby on a label 17:04:45 don´t know why someone would, but... 17:04:47 +1 17:04:58 +1 17:05:15 Proposal: do not put role of “label” in the ARIA spec. as is to prone to author errors 17:05:20 +1 17:05:21 +1 17:05:23 +10000000 17:05:27 + 1/2 17:05:34 +pi 17:05:41 + i 17:05:44 RESOLUTION: do not adopt the label role in ARIA core 17:05:45 +1 17:05:46 +1 17:07:37 topic: Localized role descriptions 17:07:43 ttps://rawgit.com/w3c/aria/roledescription/aria/aria.html#aria-roledescription 17:07:46 action-1417? 17:07:47 action-1417 -- Joanmarie Diggs to Add edit for ISSUE-636: localized role description -- due 2015-06-12 -- OPEN 17:07:47 https://www.w3.org/WAI/PF/Group/track/actions/1417 17:08:18 rs: Markku´s gonna love this 17:12:22 various: sorting what this means 17:12:27 ... 17:12:43 s/descriptoin/description/ 17:13:07 jd: you would use this to provide clarification to the user about the intent of the role 17:13:27 mc: kind of like an unofficial sub-role 17:13:44 jd: get AT to announce something helpful 17:13:54 but needs to be on a meaningful role to begin with, or the AT might overlook entirely 17:14:24 rs: so require ARIA role when this is used? 17:14:41 jd: we tried that, but found use cases for use on elements that have implicit ARIA semantics 17:15:36 so came up with rule that their must either be ARIA role, or have implict role mapping 17:15:47 ??: will authors understand that? 17:16:13 mc: you have to be pretty knowledgeable to know why to use this to begin with, so maybe it´s safe enough 17:16:35 fe: no, it´ll be a shiny toy that people will play with in all sorts of ways 17:17:02 jd: is the concern about what the prose says, or how it says it? 17:19:51 Authors MUST only use aria-roledescription on elements that equate to a valid WAI-ARIA role (have an implicit WAI-ARIA role semantic) or or have a valid WAI-ARIA role applied. If neither condition is met then then the aria-roledescription MUST NOT be exposed by user agents. 17:21:44 17:21:47 Authors SHOULD only use aria-roledescription on elements that equate to a valid WAI-ARIA role (have an implicit WAI-ARIA role semantic) or or have a valid WAI-ARIA role applied. If neither condition is met then then the aria-roledescription MUST NOT be exposed by user agents. 17:22:42 If neither condition is met then user agents MUST NOT expose the aria-roledescription. 17:24:07 Authors SHOULD only use aria-roledescription on elements that equate to a valid WAI-ARIA role (have an implicit WAI-ARIA role semantic) or or have a valid WAI-ARIA role applied. If neither condition is met then user agents MUST NOT expose the aria-roledescription. 17:27:22 RESOLUTION: apply the new text above to replace the second paragraph in the specification. 17:28:15 jd: this needs more review cycles, but if approved I´ll close the action / issue 17:28:26 will do on the list 17:28:34 rs: let me know if it needs to come back in a meeting 17:28:48 topic: Keyboard shortcut help 17:28:54 action-1642? 17:28:54 action-1642 -- Richard Schwerdtfeger to Create aria-keyshortcut proposal to group -- due 2015-06-11 -- OPEN 17:28:54 https://www.w3.org/WAI/PF/Group/track/actions/1642 17:28:58 issue-711? 17:28:58 issue-711 -- Expose Keyboard Shortcut help information to ATs -- open 17:28:58 https://www.w3.org/WAI/PF/Group/track/issues/711 17:29:47 https://lists.w3.org/Archives/Public/public-pfwg/2015Jun/0029.html 17:30:07 rs: HTML trying to create an access key 17:30:21 this issue goes back 10 years 17:30:28 we knew the accesskey attribute had problems 17:30:42 proposed an access element 17:30:49 brought to XHTML WG 17:30:56 but the scene changed 17:31:13 but we´ve been talking about access keys ever since, but not managed to get anything done 17:31:20 good reasons to take up 17:31:24 want to be able to remap keys 17:31:36 on user side, in order not to conflict with AT 17:31:44 and associate description 17:31:50 but that´s just for moving focus 17:31:59 +q 17:32:25 but now we´ve got shortcuts on elements that have a role and label, and activate 17:32:41 so need the key to activate not just focus 17:32:45 but ARIA doesn´t allow that 17:32:53 because it doesn´t define mainstream UI 17:33:12 so doing this in HTML with access key makes sense 17:33:15 but no progress in years 17:33:44 so my proposal is to put stuff in ARIA spec 17:34:00 and make it optional but hopeful that host language would say ¨go ahead and implement in mainstream UI¨ 17:34:17 do have valid use cases for remapping 17:34:36 ack s 17:34:48 Need Concept Parallel to that in HTML next 17:34:55 Must think of Other Agents than AT 17:35:01 Split into aria-hotkey and aria-accesskey 17:35:48 ss: should parallel the HTML design pattern 17:35:59 consider how UAs expose the hot keys 17:36:23 split properties to separate focus from activate 17:36:30 hotkey to trigger function, access key to set focus 17:36:56 rs: we weren´t charged to create ¨accesskey¨ in ARIA, just a shortcut 17:37:13 bg: there´s access key, and access key label 17:37:30 17:37:53 the label is supposed to grab native browser keys and stuff 17:38:15 rs: I don´t use accesskey because of how messed up it is 17:38:33 have some UA interest on this 17:39:23 do you all agree ARIA should not specify UA behavior? 17:39:40 17:40:01 so that´s a position that has not changed 17:40:28 Ok to put this in a branch for further review? 17:40:32 17:41:02 sounds like the next step, then we need explicit review from the UA folks 17:41:27 note that in the current approach, it would only be available to AT 17:41:32 but UAs could expose 17:41:43 jn: or extensions, or special script library 17:42:30 I´d like to take it further, and provide a description of what a shortcut does, not necessarily tied to an element 17:42:42 ss: I proposed that, response was could use aria-describedby 17:42:53 quoting Rich: "The AT will have access to the label and descriptions for the widget" 17:43:14 rs: I meant that enough information is available, not that you use aria-describedby specifically 17:43:21 ss: that requires an additional step 17:43:33 a descriptive string would be useful 17:43:38 rs: gotta figure out where to map it 17:43:46 adds to the set of descriptions we provide 17:43:53 js: aria-hint 17:43:55 fe: aria-help 17:44:09 jd: some platforms have an actions interface to get mappings 17:44:43 rs: CS will bring up control patterns 17:45:19 rs: I´d like to get review on the current first, then address whether to tackle a description 17:46:19 mc: agree with agressively seek review 17:46:24 issue-406 17:46:24 issue-406 -- Proposal for new aria-hint property. (Previously proposed as @aria-help) -- open 17:46:24 https://www.w3.org/WAI/PF/Group/track/issues/406 17:47:24 rs: let´s put this in a review branch, with a note about needing to get back to descriptions 17:48:13 action-1642: https://lists.w3.org/Archives/Public/public-pfwg/2015Jun/0029.html 17:48:13 Notes added to action-1642 Create aria-keyshortcut proposal to group. 17:49:48 https://www.w3.org/WAI/PF/Group/track/products/17 17:49:55 topic: Actions review 17:51:01 rs: issues list is growing 17:51:08 mc: time for another triage to push stuff to 2.0 17:51:40 rs: yes, and we´re moving up the 2.0 timeframe anyways so won´t be forever 17:54:51 close action-1320 17:54:51 Closed action-1320. 17:55:12 action-1380? 17:55:12 action-1380 -- Joanmarie Diggs to #presentation should mention aria-hidden vs presentation role on raster and vector images in relation to ACTION-1379 -- due 2015-06-11 -- OPEN 17:55:12 https://www.w3.org/WAI/PF/Group/track/actions/1380 17:55:16 don´t think mapping the "offscreen" api properties in the situation of aria-hidden="false" on non-rendered elements will go anywhere 17:55:37 action-1379? 17:55:37 action-1379 -- Joseph Scheuhammer to TAC should cover rendered descendants from external sources: svg, iframe, etc. (Compose text and get final review form ARIA subteam) -- due 2015-02-13 -- OPEN 17:55:37 https://www.w3.org/WAI/PF/Group/track/actions/1379 17:56:29 action-1405? 17:56:29 action-1405 -- James Craig to For issue-526 modify spec. to allow non-global attrs to apply to host language elements having the correct aria semantics -- due 2015-01-22 -- OPEN 17:56:29 https://www.w3.org/WAI/PF/Group/track/actions/1405 18:00:29 action-1416? 18:00:29 action-1416 -- James Craig to Include definitions for terms used as first word of all attr definitions (defines, identifies, indicates) -- due 2014-04-07 -- OPEN 18:00:29 https://www.w3.org/WAI/PF/Group/track/actions/1416 18:04:34 action-1424? 18:04:34 action-1424 -- James Craig to Propose spec text for generic/general/??? role (computed role of html:div, html:span, svg:g, etc) and clearly explain explicit usage of this role is not common, and clearly explain relationship to group and none role. -- due 2014-04-21 -- OPEN 18:04:34 https://www.w3.org/WAI/PF/Group/track/actions/1424 18:06:47 rrsagent, make minutes 18:06:47 I have made the request to generate http://www.w3.org/2015/06/11-aria-minutes.html MichaelC 18:09:10 rrsagent, make minutes 18:09:10 I have made the request to generate http://www.w3.org/2015/06/11-aria-minutes.html MichaelC 18:22:23 clown has joined #aria 18:59:23 richardschwerdtfeger has joined #aria 19:24:09 richardschwerdtfeger has joined #aria 19:38:58 richardschwerdtfeger has joined #aria 19:44:18 Zakim has left #aria 20:40:15 richardschwerdtfeger has joined #aria 20:41:20 asurkov has joined #aria 21:52:38 asurkov has joined #aria