13:36:45 RRSAgent has joined #wcag-act 13:36:45 logging to http://www.w3.org/2017/05/22-wcag-act-irc 13:39:34 this #wcag-act is Accessibility Conformance Testing Teleconference 13:40:16 agenda? 13:43:40 agenda+ Issue 86 - Update Abstract to not focus only on automated test tools - Pull Request 90 13:43:42 https://github.com/w3c/wcag-act/pull/90/files 13:43:48 agenda? 13:44:15 agenda+ Issue 88 - Update Outcomes section "Cannot tell" - Status 13:44:35 agenda+ Getting Draft 2 of the document out the door (Planned for Aug.) - Action items, concerns 13:44:57 agenda+ Version numbers for rules 13:45:49 agenda+ Publication requirements - Issue #81 13:46:15 agenda? 13:46:36 agenda+ TPAC 2017 13:46:54 agenda+ Next meeting is 29 May 13:49:18 q? 13:57:44 present+ 14:00:53 present+ 14:05:00 Kathy has joined #wcag-act 14:07:15 I'll do it 14:07:35 rdeltour has joined #wcag-act 14:07:41 Scribe : ChrisLoiselle 14:07:45 present+ Kathy 14:07:52 present+ 14:08:15 zakim, next item 14:08:15 agendum 1. "Issue 86 - Update Abstract to not focus only on automated test tools - Pull Request 90" taken up [from maryjom] 14:08:32 https://github.com/w3c/wcag-act/pull/90/files 14:09:31 MaryJo : We will look at changes on update to rules format 14:11:03 Note: General consensus is that changes look good. 14:11:15 zakim, next item 14:11:15 agendum 2. "Issue 88 - Update Outcomes section "Cannot tell" - Status" taken up [from maryjom] 14:11:26 https://github.com/w3c/wcag-act/issues/88 14:11:59 MaryJo: Update from Mo will follow later 14:12:10 zakim, close item 14:12:10 I don't understand 'close item', ChrisLoiselle 14:12:37 zakim, close agendum 2 14:12:37 agendum 2, Issue 88 - Update Outcomes section "Cannot tell" - Status, closed 14:12:39 I see 5 items remaining on the agenda; the next one is 14:12:39 3. Getting Draft 2 of the document out the door (Planned for Aug.) - Action items, concerns [from maryjom] 14:12:53 zakim, next item 14:12:53 agendum 3. "Getting Draft 2 of the document out the door (Planned for Aug.) - Action items, concerns" taken up [from maryjom] 14:13:59 MaryJo: There are a couple of notes on accessibility supports and what that means. 14:14:15 https://www.w3.org/TR/act-rules-format/#structure-acc-supp 14:15:37 MaryJo looks to expand on the editor's notes and what accessibility support means. Opens comments on what language is needed 14:17:01 Kathy W: Testing tools look at DOM vs. responsive designs, possible add in language to clarify that. 14:18:02 MaryJo: We talk to that in Test Subject Types section..we could talk to that in Accessibility Support section. Not all UAs render features etc. 14:19:07 Kathy W: with the selector, we may want to have what version of page we are reviewing. Or maybe that is the "context"... 14:20:18 MaryJo: Wilco wanted to have us look at test cases, vs. checks, vs. unit tests. Settle on single term used. 14:20:30 https://www.w3.org/TR/act-rules-format/#test-proc-cases 14:20:40 Kathy W: No preference on which one we choose. 14:21:20 Romain: No preference. Test Case sounds good. 14:21:30 MaryJo: Test case sounds good 14:21:38 Did we want to have this as a resolution? 14:23:38 MaryJo: Prepare to discuss the contents and what is needed on document before we go forward on 2nd draft. 14:23:57 Wilco will be pulling in examples to help better understand the scope. 14:24:01 zakim, next item 14:24:01 agendum 4. "Version numbers for rules" taken up [from maryjom] 14:25:12 MaryJo: Opens comments on version number for rules. 14:25:47 Romain: 7.4.1. is based on semantic versioning. Possible further clarification on text within 7.4.1. 14:25:48 https://www.w3.org/TR/act-rules-format/#test-proc-cases 14:26:34 different vs. new failure results. needs clarification on what the differences are ? Which version receives the update? 14:26:45 Minor vs. major updates. 14:29:50 MaryJo: Patch updates...usually if there is a bug within a rule. If you are fixing a bug that affects the rule results. Number it as a major updated rather than a patch. Seems that it could be confusing. 14:30:32 Debra : If new results , then a major update should occur. 14:31:04 http://semver.org/ 14:32:41 Romain: If does add a feature, but in a backwards compatible way, it is a minor update. If it breaking the backwards compatibility, it is a major update. Otherwise it is a patch. 14:36:32 Note: Bring point up on Major , Minor and patch up with Wilco and Shadi next week. I.e. what is considered a patch ? 14:37:41 zakim, next item 14:37:41 agendum 5. "Publication requirements - Issue #81" taken up [from maryjom] 14:38:11 https://github.com/w3c/wcag-act/issues/81 14:38:47 Note : Stein Erik, not available. We will talk to this next time. 14:39:26 MaryJo: TPAC https://www.w3.org/2017/11/TPAC/#registration 14:40:17 Book hotels as soon as you can. 14:40:46 Kathy : will follow up with Shadi on planning details of days we will meet. 14:41:51 MaryJo: We will wrap up call today. We will meet next week, even though it is a holiday in U.S. 14:42:15 rrsagent, make minutes 14:42:15 I have made the request to generate http://www.w3.org/2017/05/22-wcag-act-minutes.html ChrisLoiselle 14:42:39 No problem. 14:42:56 Is the meeting made public? 14:43:08 I tried to generate minutes and got an error. 14:43:55 rrsagent, make meeting public 14:43:55 I'm logging. I don't understand 'make meeting public', ChrisLoiselle. Try /msg RRSAgent help 14:44:19 rrsagent, set logs world-visible 14:44:34 rrsagent, make minutes 14:44:34 I have made the request to generate http://www.w3.org/2017/05/22-wcag-act-minutes.html ChrisLoiselle 14:45:08 chair: MaryJoMueller 14:45:17 The title is off on the link, but I'll share to the group 14:45:53 OK. Did you want me to send to the email list? 14:46:03 trackbot, end meeting 14:46:03 Zakim, list attendees 14:46:03 As of this point the attendees have been ChrisLoiselle, maryjom, Kathy, rdeltour 14:46:07 meeting: Accessibility Conformance Testing Teleconference 14:46:11 RRSAgent, please draft minutes 14:46:11 I have made the request to generate http://www.w3.org/2017/05/22-wcag-act-minutes.html trackbot 14:46:12 RRSAgent, bye 14:46:12 I see no action items