16:26:56 RRSAgent has joined #aria 16:26:56 logging to http://www.w3.org/2016/08/18-aria-irc 16:26:58 RRSAgent, make logs world 16:26:58 Zakim has joined #aria 16:27:00 Zakim, this will be 16:27:00 I don't understand 'this will be', trackbot 16:27:01 Meeting: Accessible Rich Internet Applications Working Group Teleconference 16:27:01 Date: 18 August 2016 16:27:02 chair: Rich 16:27:10 RRSAgent, make log public 16:29:06 mck has joined #aria 16:29:30 https://lists.w3.org/Archives/Public/public-aria/2016Aug/0171.html 16:30:06 fesch has joined #aria 16:31:14 https://lists.w3.org/Archives/Public/public-aria-admin/2016Aug/0015.html 16:31:15 present+ MichaelC 16:31:50 LJWatson has joined #aria 16:32:08 https://lists.w3.org/Archives/Public/public-aria-admin/2016Aug/0015.html 16:32:25 Scribe: Stefan 16:33:03 Rich: CFC results of TF 16:33:05 https://lists.w3.org/Archives/Public/public-aria-admin/2016Aug/0011.html 16:33:18 Rich: we only got results of support 16:33:28 Rich: no objections, Michael? 16:33:35 present+ LJWatson 16:33:41 present+ Janina 16:33:45 Michael: no 16:33:47 present+ Rich_Schwerdtfeger 16:33:51 present+ JaEunJemmaKu 16:33:54 Rich: how is this staffed? 16:34:05 present+ fesch 16:34:13 Michael: we are still wrking on that 16:34:27 Michael: we needs people of all three WG's 16:34:44 Michael: we ask people from small list of candidates 16:35:08 Janina: gona have to beat the bushes, no chair already known 16:35:19 present+ matt_King 16:35:58 Michalel: assuming charter goes throught thn group will have clear indication .. we are cooking things together at TPM 16:36:28 Janina: bunch of mails from seevral groups, will be clearer after the week-end 16:37:33 Matt: no overlaps with CSS please at TPAC 16:37:55 Matt: could also be not on Monday 16:38:20 Rich: we are wrking to split things between different working groups 16:39:08 jemmafromdesktop has joined #aria 16:39:16 Matt: 30 min req. to get the ball rolling in that area 16:39:24 Rich: Thursday perhaps 16:39:39 Rich: we reach decision to form up TF 16:40:38 Rich: we have concerns how this will be staffed, this is quite "overcommitted" 16:41:12 Michael: CSS mappings is not a ARIA deliverable 16:41:38 Topic: Action 2107 16:41:42 https://www.w3.org/WAI/ARIA/track/actions/2107 16:41:50 http://rawgit.com/w3c/aria/action2107-aria-details/aria/aria.html 16:42:04 Matt: URL to branch with proposal 16:42:51 Matt: I found some middle ground but not sure what is wanted in long run 16:43:08 http://rawgit.com/w3c/aria/action2107-aria-details/aria/aria.html#aria-details 16:43:12 Rich: (reading it) 16:43:21 present+ ShaneM 16:43:45 Matt: changed ws: 2nd paragraph int two 16:44:09 Matt: changed intent (availability of decription, nav to it, visible etc,) 16:44:25 Matt: simplified paragraphs basically 16:44:42 Matt: name/description was broken up into separate units 16:45:17 Matt: flattened into a string is useful 16:45:56 Matt: next paragraph some acc apis is aout precedence of aria-details 16:46:34 Matt: one reason for this is UAs are moving in direction to support both, in the long run we can remove the statement 16:47:03 Matt: only reveal details and hide description ist the other way to go 16:47:39 Rich: I worry about that we have two descriptions both of them visible - which one to go? 16:47:39 q+ to say how can you ensure aria-details reference is visible and points to a different web page? 16:48:31 Matt: aria-describedby is NOT only for description, it is multi-purpose, whereas aria-details is much more specifiic in terms of what is decribed 16:48:58 q? 16:48:59 Matt: both a re useful I can imagine both scenarios+ 16:49:10 ack fesch 16:49:10 fesch, you wanted to say how can you ensure aria-details reference is visible and points to a different web page? 16:49:32 Fred: visible on page or different web page, is the different page visible, too? 16:49:35 +q 16:49:49 ack me 16:50:06 Rich: examples changed? Matt: no 16:50:56 Rich: extended description, alternative drawing could also be possible 16:51:09 James: big tooltip with structural info also 16:51:30 Rich: tooltip never came up, but why is this not a description? 16:51:36 James. because it is structured 16:52:10 Rich: intent is we don't want to be stringified 16:52:34 James: we need also way to keyboard user to move to structured content 16:52:47 Rich: big discussion in API working group 16:53:11 Rich: new key shortcuts are also topic for aria-details nav to 16:53:31 Matt: devil is in details for focus ,oving 16:54:08 Matt: ARIA 2.0 discussion: do we have a diffeernt kind of key attribut on an element 16:54:23 Rich: yeah, ARIA 2 16:54:44 Rich: we need meeting to discuss ARIA 2 items before TPAC 16:55:17 Matt: ACC API's : if group things limiting authors then we should decide so 16:56:15 RicH. it is more a browser limitation than a AT limitation, original concern was using certain relationships under covers and this will hold up everything 16:56:36 Rich: no normative text change, I'm ok with this 16:56:42 q? 16:56:43 +1 16:56:45 +1 16:56:47 +1 16:56:49 R+1 16:57:50 RESOLUTION: accept ed. change for action 2107 16:57:58 q- 16:58:34 zakim, agenda? 16:58:34 I see nothing on the agenda 16:59:53 Topic: https://www.w3.org/WAI/ARIA/track/actions/1723 17:00:31 Rich: Joanie is not here 17:00:47 Michael: not able to anser fast if this was pulled in 17:01:25 Rich: (looking into it too) 17:02:00 Rich: we move on 17:02:24 Topic: Testable Statements (Coordination) and test case Authoring 17:02:35 Rich: Shane was creating a wiki 17:02:55 Shane: I don't have this action item 17:03:13 Rich: all new 1.1 statements 17:03:34 Michel: I don't remember creating any new 1.1 testable statements 17:03:45 Shane: Joanie finished that after the meeting 17:04:19 https://www.w3.org/wiki/ARIA_1.1_Testable_Statements#Overview 17:04:32 https://www.w3.org/wiki/ARIA_1.1_Testable_Statements 17:05:27 Fred: we have pearl script that takes cntent from wiki and put it into jason blom or whatever 17:05:59 Fred: we can tweak wiki pages and turn them into automated test pages 17:06:10 Rich: can you explain format 17:07:01 Fred: code is there but not testable staement 17:07:16 https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions_with_Tables 17:07:56 Fred: (explains first example) 17:08:07 Fred: if it fails will be identified with FAIL 17:08:32 Fred: important part is saying IF_GIVEN 17:08:50 Fred: below that is table what we expect found by platform 17:09:06 Rich: can there be breaks or must it be one line in testable statement 17:09:31 Fred: space is fine, Returns probably also ... 17:09:44 Fred: no wiki markup please 17:10:22 Rich: original one for ARIA .. testable statements .. bunch of properties 17:10:23 https://www.w3.org/wiki/ARIA_1.1_Testable_Statements 17:10:38 Rich: aria-busy for example 17:10:58 Rich: must have same structure as for SVG testable statements# 17:11:49 Fred: add normative requirement (aria-busy=true), I'm not sure that we have that as offerings 17:12:22 Matt: in this case that normative change won't drive a testable statement 17:12:27 Rich: can ou add comments? 17:12:41 Fred: actually pulls that out and put it in JSON 17:12:52 Rich: comments a re not parsed 17:13:00 Rich: we can work with this 17:13:11 Rich: we need testable statements for aria-busy 17:13:35 Rich: what is if aria-busy is applied to Table etc. 17:13:47 can we look at : https://www.w3.org/wiki/ARIA_1.1_Automated_Testing#Draft_ARIA_Test_Case_Format 17:13:57 Rich: does everybody undestands? OK. 17:14:31 q+ to talk about aam stuff 17:15:16 Fred: multiple people cannot edit page at same time, it is a wiki 17:15:31 Rich: who does what? I'm gpoing to do that NOW :) 17:16:07 Fred: right now I'm going tompull out the PRE 17:16:39 Fred: looks like the other stuff disappeared .. strange .. must check 17:17:38 Rich: let's assign things to people 17:17:57 Rich: who wants to take 3.1 to 3.10? 17:18:29 Rich: for things that have changed in ARIA 1.1 17:19:23 Rich: Fed will get an action 17:20:35 ACTION: Fred Esch write testable stements and testcases for 3.1 to 3.10 17:20:36 Created ACTION-2109 - Esch write testable stements and testcases for 3.1 to 3.10 [on Fred Esch - due 2016-08-25]. 17:21:07 ACTION: Rich write testable stements and testcases for 3.10 to 3.22 17:21:07 Created ACTION-2110 - Write testable stements and testcases for 3.10 to 3.22 [on Richard Schwerdtfeger - due 2016-08-25]. 17:22:21 ACTION: Fred Esch write testable stements and testcases for 4.1 to 4.14 17:22:21 Created ACTION-2111 - Esch write testable stements and testcases for 4.1 to 4.14 [on Fred Esch - due 2016-08-25]. 17:23:52 ACTION: Fred Esch write testable stements and testcases for 4.15 to end of 4 17:23:53 Created ACTION-2112 - Esch write testable stements and testcases for 4.15 to end of 4 [on Fred Esch - due 2016-08-25]. 17:25:21 Topic: Blockers for entering CR 17:25:34 Rich: I can not see any 17:25:54 Rich: just some things with Alexander Surkov / James Craig 17:26:03 Michel: no blockers 17:26:22 Matt: no blockers, there was an action but was discussed in API call 17:27:06 Rich: I thing we are OK now 17:27:20 Rich: we need relationships nailed down with Alex 17:27:39 Rich: some people must still respond 17:28:06 Rich: we got tget this wrapped up 17:28:22 Rich:we now get started on this. Anything else? 17:28:37 Topic: Automation 17:28:42 https://www.w3.org/wiki/ARIA_1.1_Automated_Testing#Draft_ARIA_Test_Case_Format 17:29:02 Shane: link goes to a fragment with test case formats 17:30:09 Shane: support info requested in this format, so we care for EACH API mapping what is the bits we care about .. this info was in manual tests before .. useless for machines must e machine readable 17:30:26 Shane: automation of result evaluation must be easier 17:31:03 Rich: will you define lotta stuff of table for an UIAutiomation table interface? 17:31:20 Shane: can you give example? 17:31:56 Rich: each of element mappings - can we do a hierarchy? 17:32:08 Shane: as long if something has an ID 17:32:28 Rich: do all elements need ID's? 17:32:33 Shane: yes. 17:33:40 Shane: you can use CSS selectors for traverse, too 17:34:05 Rich: let's get a path out it, maybe a couple of pathers 17:34:23 p a lotShane: need working examples will help a lot 17:35:35 Shane: fake screen reader, gets info out of acc. tree each platform we want to automate, thats the basic idea 17:35:50 Rich: let's get started on 17:36:20 Ricjh: Fred, documenting this format is also important, do you have time for this? 17:36:23 Fred: yes 17:37:03 RRSAgent, make minutes 17:37:03 I have made the request to generate http://www.w3.org/2016/08/18-aria-minutes.html Stefan 19:17:05 sam has joined #aria 19:27:01 Rich has joined #aria 19:47:51 Zakim has left #aria 19:57:41 Rich has joined #aria 22:36:29 sam has joined #aria 23:58:02 chaals has joined #aria