14:47:21 RRSAgent has joined #wai-wcag 14:47:21 logging to http://www.w3.org/2016/08/09-wai-wcag-irc 14:47:23 RRSAgent, make logs public 14:47:25 Zakim, this will be WAI_WCAG 14:47:25 ok, trackbot 14:47:26 Meeting: Web Content Accessibility Guidelines Working Group Teleconference 14:47:26 Date: 09 August 2016 14:47:29 Chair: AWK 14:47:31 +AWK 14:47:36 Zakim, agenda? 14:47:36 I see 4 items remaining on the agenda: 14:47:37 1. TPAC Registration reminder: https://www.w3.org/2016/09/TPAC [from AWK] 14:47:37 2. Survey on SC requirements: https://www.w3.org/2002/09/wbs/35422/reqsWCAG21/results 14:47:37 3. WCAG Techniques and Understanding comments – soliciting assistance for items https://github.com/w3c/wcag/issues 14:47:38 4. Communication practices discussion [from AWK] 14:47:48 Zakim, clear agenda 14:47:48 agenda cleared 14:48:07 agenda+ TPAC Registration closes September 2: https://www.w3.org/2016/09/TPAC 14:49:36 agenda+ ACT TF Proposal https://www.w3.org/community/auto-wcag/wiki/(Proposed)_Accessibility_Conformance_Testing_(ACT)_Task_Force_Work_Statement 14:50:03 agenda+ Survey on Public Comments: https://www.w3.org/2002/09/wbs/35422/August9Misc/results 14:50:31 agenda+ SC requirements discussion 14:51:57 Wilco has joined #wai-wcag 14:53:33 davidmacdonald has joined #wai-wcag 14:53:47 regrets+ Laura_Carlson, Shawn_Lauriat, Wayne 14:54:02 LisaSeeman has joined #wai-wcag 14:54:35 Rachael has joined #wai-wcag 14:56:15 Makoto has joined #wai-wcag 14:56:23 agenda+ github issue volunteers 14:58:36 alastairc has joined #wai-wcag 15:00:14 agarrison has joined #wai-wcag 15:00:37 agenda 4 is SC requirements discussion https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria 15:00:45 Kathy has joined #wai-wcag 15:00:45 agenda 4 = SC requirements discussion https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria 15:00:58 Zakim, agenda? 15:00:58 I see 5 items remaining on the agenda: 15:00:59 1. TPAC Registration closes September 2: https://www.w3.org/2016/09/TPAC [from AWK] 15:00:59 2. ACT TF Proposal https://www.w3.org/community/auto-wcag/wiki/(Proposed)_Accessibility_Conformance_Testing_(ACT)_Task_Force_Work_Statement [from AWK] 15:00:59 3. Survey on Public Comments: https://www.w3.org/2002/09/wbs/35422/August9Misc/results [from AWK] 15:01:00 4. SC requirements discussion https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria 15:01:00 5. github issue volunteers [from AWK] 15:01:15 SarahHorton has joined #wai-wcag 15:02:28 present+ alastairc 15:02:32 steverep has joined #wai-wcag 15:02:32 shadi has joined #wai-wcag 15:02:36 present+ Rachael 15:02:40 present+ agarrison 15:02:48 present+steverep 15:02:50 Mike_Elledge has joined #wai-wcag 15:02:55 present+ Makoto 15:03:02 present+ shadi 15:03:10 present+ Mike_Elledge 15:03:15 present+ SarahHorton 15:03:23 Present+ David MacDonald 15:03:37 present+ Kathy 15:04:11 I can scribe if noone else would like to do so. 15:04:27 +Greg_Lowney 15:04:53 present+ MichaelC 15:04:55 Scribe: David 15:05:10 ZAkim, take up item 1 15:05:10 agendum 1. "TPAC Registration closes September 2: https://www.w3.org/2016/09/TPAC" taken up [from AWK] 15:05:11 Zakim, take up item 1 15:05:12 agendum 1. "TPAC Registration closes September 2: https://www.w3.org/2016/09/TPAC" taken up [from AWK] 15:05:36 AWK coming to last reminder for TPAC 15:06:18 Zakim, take up item 2 15:06:18 agendum 2. "ACT TF Proposal https://www.w3.org/community/auto-wcag/wiki/(Proposed)_Accessibility_Conformance_Testing_(ACT)_Task_Force_Work_Statement" taken up [from AWK] 15:06:59 AWk enough iterest expressed for concept to pursue 15:07:21 s/iterest/interest 15:08:04 Sarah_Swierenga has joined #wai-wcag 15:08:12 Separate question. is there enough resources... there are people already working on it 15:08:29 AWK cjair feel we should support it. 15:08:46 s/cjair/chairs 15:08:57 present+ Sarah_Swierenga 15:08:59 MoeKraft has joined #wai-wcag 15:09:13 marcjohlic has joined #wai-wcag 15:09:41 ACT = Accessibility Conformance Testing 15:10:20 KimD has joined #wai-wcag 15:10:39 Wilco: ACTS automated testing proposals, figure out what would make for good test rules and use those as a rallying point, brought into a single repository... 15:11:03 Judy has joined #wai-wcag 15:11:06 q+ 15:11:18 ack mi 15:11:20 SHadi: includes semi automated and other types of human tesign 15:11:28 q? 15:12:14 Mike-E: defined rules for automated and semi automated... wondering if we collide with existing tools, is it an issue and how to mitigate ot 15:12:53 present+ Judy 15:13:19 +KimD 15:13:34 Wico: It can be an issue... that is why we want to do this work... tools have disparity of results... want to come together to get an approach that tool devs cannagree on 15:13:52 s/wico/Wilco 15:14:17 s/cannagree/can agree 15:14:31 Mike: Is there interest by developers 15:15:01 q+ 15:15:10 Wilco: Deqaue, IBM, SSB, Site Improve and others are on board 15:15:27 q- 15:15:34 Mike: What skill sets are you looking for? 15:15:43 s/Deqaue/Deque/ 15:16:19 Wilco: Knowing WCAG and and working on tools, QA people 15:16:27 q? 15:16:28 q+ 15:16:31 ack j 15:17:01 Judy: Thanks to Wilco and Shadi, part of work would be under a new charter, yes? 15:17:26 AWK: Need figure out deliverables... 15:17:32 q+ 15:17:49 ack j 15:18:01 AWK: Ability to deliver, is dependant on people coming into the group from the community group 15:18:16 Judy: There are a few orgs that can 15:19:10 Judy: some orgs cannot easily participate on community group but can be under a WCAG group... 15:19:41 AWK: Assuming group agrees. 15:20:13 Michael: We can probably put it in our space quickly before the CFC 15:21:03 Judy: Sounds doable, there would be an approval timeframe... want to ensure we can maintain enthusiasm from contributing orgs during this transition time. 15:21:35 AWK: Are we comfortable with concept and work statement 15:21:57 AWK if so we can proceed 15:22:09 i can not access the link 15:22:25 AWK anyone uncomfortable... (silence=agreement) 15:22:30 https://www.w3.org/community/auto-wcag/wiki/(Proposed)_Accessibility_Conformance_Testing_(ACT)_Task_Force_Work_Statement 15:22:36 jon_avila has joined #wai-wcag 15:22:42 present+jon_avila 15:23:09 q+ wondering about approval of tools 15:23:10 RESOLUTION: Working group approves work statement and TF proposal 15:23:19 ack s 15:23:20 @LisaSeeman I think you have to take the quote mark off the end. 15:23:40 s/proposal/Proposal for the ACT task force 15:23:57 q+ 15:24:31 Steve: are we going endorse or evaluate any tool for accuracy with our agreed set of tests 15:24:40 AWK: Not likely 15:24:40 ack sh 15:24:51 Shadi: AAc doesn 15:24:59 @Judy - it is clear, I only said that as earlier there was talk about the automated rules being first up in terms of work, helping to standardise rule set. 15:25:13 q+ 15:25:24 W3C doesn't make assertions on tools or browser etc... 15:26:36 Ryladog has joined #wai-wcag 15:26:49 Present+ Katie_Haritos-Shea 15:27:03 ack wil 15:27:05 Shadi: Tool makers can say what tools they are following, as a self declarations 15:27:12 present+ marcjohlic 15:27:32 Zakim, agenda? 15:27:32 I see 5 items remaining on the agenda: 15:27:33 1. TPAC Registration closes September 2: https://www.w3.org/2016/09/TPAC [from AWK] 15:27:33 2. ACT TF Proposal https://www.w3.org/community/auto-wcag/wiki/(Proposed)_Accessibility_Conformance_Testing_(ACT)_Task_Force_Work_Statement [from AWK] 15:27:33 3. Survey on Public Comments: https://www.w3.org/2002/09/wbs/35422/August9Misc/results [from AWK] 15:27:34 4. SC requirements discussion https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria 15:27:34 5. github issue volunteers [from AWK] 15:27:52 Zakim, close item 1 15:27:52 agendum 1, TPAC Registration closes September 2: https://www.w3.org/2016/09/TPAC, closed 15:27:54 I see 4 items remaining on the agenda; the next one is 15:27:54 2. ACT TF Proposal https://www.w3.org/community/auto-wcag/wiki/(Proposed)_Accessibility_Conformance_Testing_(ACT)_Task_Force_Work_Statement [from AWK] 15:27:58 Zakim, close item 2 15:27:58 agendum 2, ACT TF Proposal https://www.w3.org/community/auto-wcag/wiki/(Proposed)_Accessibility_Conformance_Testing_(ACT)_Task_Force_Work_Statement, closed 15:28:00 Wilco: A lot of doscussion about writing test that can prove a tool is implemented properly. Likely will be a suite of tools to run agaonst tools to ensure they've implemented our recommendations 15:28:01 I see 3 items remaining on the agenda; the next one is 15:28:01 3. Survey on Public Comments: https://www.w3.org/2002/09/wbs/35422/August9Misc/results [from AWK] 15:28:10 Take up item 4 15:28:34 dropping off 15:29:07 AWK: WCAG 2.1 SC requirements... almost at agreement. 15:29:12 https://www.w3.org/WAI/GL/wiki/WCAG_2.1_Success_Criteria 15:29:44 Acceptance criteria for proposals 15:30:25 Want to ensure proposals are consistent 15:31:32 AWK: Idea is to have simple format, and guidelines in a template 15:31:49 q+ 15:32:52 Q+ alastairc to ask whether there are criteria / standards for the evidence needed for a new SC 15:33:44 q- 15:34:48 ack lis 15:35:37 Lisa: We are close but would like clarifications innthe draft. Concerned this is the intent, written, but people may forget, and time wasted pulling up minutes etc... evidence can be a link to the evidence... 15:36:02 Lisa: Lots of work for evidence, if it helps 6 different disabiloties 15:36:24 s/disabiloties/disabilities 15:37:29 Lisa: Let's add links, or anecdotal evidence... the ones where we rely on anecdotal are self evident such as exposing a user's information 15:37:29 q+ 15:38:51 Lisa: Desciption of how it can be tested is a lot of work, not aware it would be required for FWD 15:39:06 Lisa: Concerned we can't get that in time 15:39:36 Lisa: Would like a clause "time permitting" 15:40:03 ack AWK 15:40:05 AWK: Ameded #5 may be a link to a seoarate resource 15:41:44 AWK: Regarding evidence... that is where WG will be engaged... SCs with rock solid evidence that specific users, changes discussiona nd makes it easier... if its anectotal, then it's still evidence, but is harder and longer and more discussion... people will want to learn about the issue and ask many questions 15:42:02 q+ 15:42:32 AWK: I'm not inclined to say what kind of evidence they submit... butnwe'll need some sort of evidence that WG can consider 15:42:50 s/butnwe/but we 15:43:00 ack lis 15:43:47 Lisa: Worried... first round ... don't want us to discriminate towards issues with less research or evidence for cognitive disabilities. 15:45:08 q+ 15:45:23 AWK: Wondering what those who were in WCAG think? there was some sort of evidence... 15:45:41 LISA: Burden of evidence is similar to 2.0 15:46:18 ack r 15:46:30 LISA: WCAG 2 ... a person showed us on a computer and we accepted it... just seeing that it works... 15:47:15 Katie: Whatever you have here, is associated with evidence, associated with the resource, can be hidden, but we need a trail of evidence... 15:48:22 LISA: Do not expose information where it can do them harm... its anecdotal... my dad got dementia and people tried to sell him stuff... 15:49:51 LISA: Should write a summary of the evidence... we're on the same side... when less evidence, is when its completely obvious... 15:50:25 Katie: When presenting the SC, we would want someone on COGA available to answer questions... 15:50:45 LISA: Yes that would meet our need... 15:51:07 AWk: What's the proposal? 15:51:38 Katie: We want someone available to answer questions from WG about evidence 15:52:55 AWK: If a proposal doesn't have the benfits etc... then we don 15:53:05 q+ to disagree with gruelling time constraints 15:53:43 if there are no benefits listed or evidence, we don't have a proposal, we have an idea. 15:53:49 q+ 15:53:51 q+ 15:54:40 Ryladog_ has joined #wai-wcag 15:54:43 ack m 15:54:43 MichaelC, you wanted to disagree with gruelling time constraints 15:54:48 AWK: perhaps have incomplete proposals have "at risk" 15:55:30 ack lis 15:55:35 Michael: Don't think time frame is unreasonable... there are hundreds of pages of work. 15:55:44 +1 to must have option for "at risk" status 15:56:58 LISA: COGA is a category, its a huge area, not like low vision... etc... very complex huge fields, covers as much variety and people as WCAG... first draft, we were not asked for this new information 2 15:57:03 q+ to accept Lisa´s broad scope for cognitive definition, but we´re not boiling the ocean in WCAG 2.1, we´re doing what we can with what´s in front of us 15:57:59 q+ to say the timeline includes lots of discussion time - the December deadline is just to get first version of SC in front of us 15:58:17 ack d 15:58:26 David: couple of things 15:58:36 q+ to say the ask is not as big as you fear, it´s just to have high-level indication of need and implementability, not full resources 15:58:40 ... my preference is to get more req from PWD 15:58:41 ... 15:59:15 ... in WCAG 2.0 we wanted to provide more req for cognitive but the information wasn't available at the time 15:59:42 ... my hope is that more is testable now, more research now 16:00:19 ack m 16:00:19 MichaelC, you wanted to accept Lisa´s broad scope for cognitive definition, but we´re not boiling the ocean in WCAG 2.1, we´re doing what we can with what´s in front of us and 16:00:22 ... to say the timeline includes lots of discussion time - the December deadline is just to get first version of SC in front of us and to say the ask is not as big as you fear, 16:00:22 ... it´s just to have high-level indication of need and implementability, not full resources 16:01:21 David: WCAG 2 did what we could... Cognitive research was low, the field was huge and many issues were not testable. Hopefully there is more research now... 16:02:01 q+ 16:02:38 Michael: I feel I could write the requirements and testability in a couple of afternoons... 16:02:40 q+ to say that we are looking to get to a FPWD in February 16:02:41 q? 16:02:44 q+ 16:02:48 ack AWK 16:02:48 AWK, you wanted to say that we are looking to get to a FPWD in February 16:03:26 ack Lisa 16:03:27 AWK: December deadline is for FPWD early in the year to get feedback from public for a 2.1 in first quater of 2018 16:04:19 q+ to ask Lisa what problems she is concerned about down the line 16:04:47 Lisa: Let's say that research and testing can be described in a few sentences... explicitly in the SC requirements. 16:05:15 q+ 16:05:33 ack AWK 16:05:33 AWK, you wanted to ask Lisa what problems she is concerned about down the line 16:07:18 Lisa: Want to ensure we have a change to address concerns... a conversation rather than a sharp cutting off of the proposal. 16:07:22 go ahead 16:07:45 s/chance/change 16:08:08 s/change/chance 16:09:14 ack kath 16:09:19 q+ 16:09:38 AWK: This is a checklist, getting it on the agenda to consider rather than accepting it on WCAg 16:10:28 Kathy: Do we want to suggest what level it is at ... and indicate if there are new guidelines... if there are new techniques for existing tSC, how does that fit in... 16:10:59 s/tSC/SC 16:12:00 AWK: If its a new technique just do what we are doing now 16:13:14 ack lisa 16:13:27 AWK: Just put it in "what principle of guideline does it fall under" 16:13:38 s/of/or 16:15:44 +1 to checklist is good 16:16:28 AWK: Anyone object to sending checklist of proposals. 16:17:51 Greg Lowney: Suggest we can add optional examples if they have them under #9 ..."User examples beneficial but not required" 16:18:35 RESOLUTION: Checklist for proposals for new SC approved 16:18:54 TOPIC: Success Criteria Requirements 16:19:59 LISA: Object to the word "reasonable". 16:21:06 LISA: change "common format" to "readily available"... 16:21:21 q+ 16:21:44 ack d 16:22:04 q? 16:22:12 +1 16:23:33 Have Success Techniques which demonstrate that each Success Criterion is implementable, using readily available formats, user agents, and assistive technologies. 16:23:54 RESOLUTION: Acepted SC requirements 16:23:55 TOPIC: Success Criteria Best Practice Guidelines 16:24:15 Are short in length. However brevity should not at the expense of clarity or testability. Minimize the use of lists to where they make the success criteria easier to follow. Lists can be used to prevent the creation of multiple, similar, success criteria. When using lists, numbered lists are preferred to more easily allow referencing specific items Avoid the use of "notes" unless it makes the success criteria easier to follow (Notes are regarde[CUT] 16:24:18 s/Acepted,Accepted 16:24:30 d s/Acepted/Accepted 16:24:40 s/Acepted/Accepted 16:25:17 Are short in length. However brevity should not at the expense of clarity or testability. 16:25:41 Minimize the use of lists to where they make the success criteria easier to follow. Lists can be used to prevent the creation of multiple, similar, success criteria. 16:26:07 +1 16:26:11 I like the change +1 16:26:36 Einstein's: as short as possible but not shorter? 16:26:44 : ) 16:26:49 Ryladog has joined #wai-wcag 16:27:03 s/not shorter/no shorter 16:27:38 q+ 16:27:42 +1 16:27:50 ack r 16:28:12 AWK: concerned about irony of a guideline about short SCs being long... 16:28:16 q+ 16:29:36 Rachel: Make the clarification to "ensure that the SC ..." 16:29:47 ack li 16:30:09 LISA: Concerned people on the call will not understand... 16:30:21 What about "1. Are concise and clear" 16:30:52 +1 16:30:53 +/-1, don't mind. 16:30:59 +1 16:31:03 +1 16:31:44 Bye all 16:32:09 AWk not quite there on this Best Practice section .... we'll end the call and come back to it next time 16:32:22 Trackbot, end meeting 16:32:22 Zakim, list attendees 16:32:22 As of this point the attendees have been AWK, JF, Joshue108, Rachael, Makoto, Lauriat, Kathy, Laura, Greg_Lowney, lisa, adam_solomon, marcjohlic, KimD, Katie_Haritos-Shea, 16:32:25 ... MichaelC, jeanne, moekraft, Mike_Elledge, Lisa_seeman, alastairc, jon_avila, shadi, steverep, Davidmacdonald, Wayne, Judy, Elledge, kirkwood, Sarah_Swierenga, agarrison, 16:32:25 ... SarahHorton, MacDonald 16:32:30 RRSAgent, please draft minutes 16:32:30 I have made the request to generate http://www.w3.org/2016/08/09-wai-wcag-minutes.html trackbot 16:32:31 RRSAgent, bye 16:32:31 I see no action items