16:53:35 RRSAgent has joined #silver-conf 16:53:35 logging to https://www.w3.org/2021/03/04-silver-conf-irc 16:53:49 Meeting: Silver Conformance Options Subgroup 16:53:55 Date: 4 Mar 2021 16:53:59 Chair: sajkaj 16:54:02 present+ 16:54:05 agenda? 16:54:12 Agenda+ Agenda Review & Administrative Items 16:54:12 agenda+ Assigned github issues 16:54:12 agenda+ Use Cases Discussion (Continued) 16:54:12 agenda+ Other Business 16:54:12 agenda+ Be Done 17:00:00 Regrets: Bruce 17:01:14 PeterKorn has joined #silver-conf 17:01:16 Wilco has joined #silver-conf 17:01:29 Present+ 17:03:59 JF has joined #silver-conf 17:04:04 present+ 17:04:07 agenda? 17:04:50 Azlan has joined #silver-conf 17:04:53 Bryan has joined #silver-conf 17:05:03 present+ 17:05:10 scribe: PeterKorn: 17:05:15 John_Northup has joined #silver-conf 17:05:18 sarahhorton has joined #silver-conf 17:05:23 present+ 17:05:31 present+ 17:05:37 zakim, next item 17:05:37 agendum 1 -- Agenda Review & Administrative Items -- taken up [from sajkaj] 17:06:05 zakim, who is here? 17:06:05 Present: sajkaj, PeterKorn, JF, Bryan, John_Northup, Azlan 17:06:07 On IRC I see sarahhorton, John_Northup, Bryan, Azlan, JF, Wilco, PeterKorn, RRSAgent, Zakim, sajkaj, jeanne, MichaelC, Rachael, trackbot 17:06:07 present+ 17:06:23 present+ 17:06:47 sajka: administrative note: we will be out of sync US to the rest of the world on DST. 17:07:41 ToddLibby has joined #silver-conf 17:07:45 sajka: in two weeks (March 18th, March 25th) we will be out of sync DST. We will retain the US time. 17:07:48 present+ 17:08:03 zakim, next item 17:08:03 agendum 2 -- Assigned github issues -- taken up [from sajkaj] 17:08:09 present+ 17:08:24 present+ 17:08:24 topic: Issue 219 17:08:28 https://github.com/w3c/silver/issues/219 17:09:37 Peter reads 17:09:49 Q+ to comment on Sailesh's comments 17:11:11 q+ 17:11:27 q? 17:11:33 ack jf 17:11:33 JF, you wanted to comment on Sailesh's comments 17:11:57 JF: I think that Sailesh is echoing something that Gregg Vanderheiden said as well. When we have "partial", how do we measure that? How good is good enough? 17:12:10 q? 17:12:17 q? 17:12:23 JF: On specific requirements, even though we may get to the point where we accept less than perfect, the ability to do that measurement... I see that as being a concern, and one I've been sharing. That's how I read. 17:12:28 q+ 17:12:43 ack jo 17:12:46 John: I agree it is a slippery slope, but sliding toward greater conformance. I th ink with our approach, we are encoring that and giving them waypoints. 17:12:54 ack jea 17:13:38 q? 17:13:41 q+ 17:13:44 Jeanne: think Sailesh is misunderstanding what we are going for with "Substantial Conformance". So far for WCAG 3, have strict definitions for how much they can stray from perfection, being defined for each outcome of each guideline. 17:13:45 q+ 17:14:55 Jeanne: We can say what is critical, what isn't. For his example, that could be written as a critical failure if crucial for completing the task. Believe we have started addressing his concerns. [Note too, his comment is from November] 17:15:10 Jeanne: Feels it is a misunderstanding of the term "substantially conformant" 17:15:11 ack wil 17:15:38 Wilco: Thinks this is exactly Judy's concern, and the response is in that same line. Intent is not to let people off with sloppy a11y. 17:15:40 q? 17:15:51 ack pe 17:16:31 q? 17:16:35 peter: because we haven't spoken to substantially conformant, i want to ask Sailesh to review what we have to say about substantially conformant when its's ready. 17:16:52 Jemma has joined #silver-conf 17:16:57 q? 17:17:10 present+ 17:17:12 ... Until we have a rough consensus on how to deal with this is it premature to say anything other than we'll take his concerns into consideration. 17:17:27 +!, WFM 17:17:42 s+!/+1 17:17:52 q? 17:18:40 [agreement on how we will respond to this issue: close it as we haven't addressed substantially conformant yet; it isn't yet something in FPWD] 17:18:42 topic: Issue 277 17:18:44 https://github.com/w3c/silver/issues/277 17:19:07 Peter reads... 17:19:54 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Procedure_for_Processing_Comments -> See the Draft Answer Templates 17:20:13 q+ 17:24:40 q? 17:24:59 q+ 17:24:59 ack pet 17:25:19 q+ to say that he is a manager in Trusted Tester 17:26:13 q? 17:26:38 Peter: Thank the submitter, possibly add a link to issue 217 that we just talked about. Common question is if an organisation for some reason lets a significant number of bugs exist for some time, it's an open question, do we recognize that in some way in conformance 17:26:43 ack wil 17:27:26 q? 17:27:27 Wilco: Comment looks a lot like one from Deque. Key point: industry is collecting issue data & prioritizing them. If we use the metrics already in use & widely adopted, we don't have to change entire industry & how they are working. We also don't have to collect a lot of different info 17:27:34 q? 17:27:43 ack pe 17:27:44 Wilco in systems widely adopted. And there are ways around "Spoons" problem. 17:28:02 ack jea 17:28:02 jeanne, you wanted to say that he is a manager in Trusted Tester 17:28:45 q+ to ask aboud industry sop 17:29:05 q? 17:29:10 Jeanne: Want to clarify - Bruce didn't file this issue. He filed on behalf of Drew Nielson. Came from a very good discussion. Caution is how we handle cumulative issues - "Spoons problem". We must solve spoons problem first. 17:29:42 Jeanne: Point system provides a solution, may not be best or final. Wouldn't want us to recommend going forward without that. 17:29:50 ck saj 17:29:51 +1, that needs a solve, for sure 17:30:33 Sajka: candidate answer - people making reference to standard industry practice. We should certainly examine SOP on this (outside of a11y). Are they codified somewhere? A document somewhere? 17:30:34 q+ 17:30:37 ack saj 17:30:37 sajkaj, you wanted to ask aboud industry sop 17:31:13 Sajka: thinks a response is great - if we can make it work, but where are standards? Don't think this is in ISO 9001 17:31:19 ack pet 17:31:54 q? 17:32:54 q? 17:33:18 q+ 17:33:35 https://www.getzephyr.com/insights/agile-strategies-managing-bug-fixes 17:33:40 https://michaellant.com/2010/05/25/a-simple-agile-defect-management-process/ 17:33:46 q+ to say over time, versus snapshot 17:33:47 https://www.linkedin.com/pulse/testing-agile-quick-tutorial-defects-bugs-everything-between-sherman/ 17:33:58 ack br 17:35:09 Bryan: Likes what Peter said about Agile. Strong correlation in way we approach a11y could benefit from Agile methodologies. Another approach: Underwriters Lab on safety: How do you determine something is safe? Meets a certain level of support? Anything we can pull from there? 17:35:09 q? 17:35:10 Q+ 17:35:15 ack jea 17:35:15 jeanne, you wanted to say over time, versus snapshot 17:35:16 +1 to bryan 17:36:38 Jeanne: 2 things developing. A snapshot in time, and a process by which issues are fixed. In many ways, our approach has been a snapshot in time. Meets at this moment, and so conforms. But what we've been talking about @ Silver & Gold levels is looking at a system over time. 17:37:14 Jeanne: What do we want to encourage people to do with a system over time. Is this something that is measurable that could go to Silver level (how does a company address problems as found) 17:37:17 ack pet 17:37:17 Q+ 17:37:19 +1 to jeanne 17:37:26 good summary of challenges we have 17:37:57 q+ 17:38:59 +1 to Peter 17:39:54 ack jf 17:39:55 I like the subtle distinction between badge and medal 17:40:40 JF: want to riff on Peter's comments. "Mechanical a11y" and "editorial a11y". Codebase may be great. Then someone writes "Click the red button on the left". Concerned about snapshots for recording these issues. 17:40:51 I think Peter has an interesting idea of separating out a mechanical level 17:41:15 JF: Struggling to figure out how we record / measure over time. 17:41:25 ack wil 17:41:36 JF: maybe we should revisit badges/multiple currencies idea from before 17:41:47 I think the "multiple currencies" is Silver and Gold level 17:42:07 Wilco: definitely automation part... Things aren't black and white: "This can be automated, this cannot". Tools make quite a few assumptions about what they are doing. Tools that assume more can automate more. 17:42:30 Wilco: also, the more you know about the site/tool, the more you can automate. 17:42:43 Wilco: making decisions on what can be automated today or not isn't the way to go 17:43:26 Wilco: Also want to revisit the idea of making WCAG 3 multiple standards. One is snapshot "this is a requirement". Another "as the whole - website or app - how do you test the whole thing"? As Peter said, can't have 1m humans testing every page update. 17:43:41 q? 17:43:42 q+ to talk about WAI-CooP and the plan for workshops for Sampling and Scoring 17:43:46 Wilco: also, did you organize yourself to address a11y in your development processes. 17:43:47 q+ 17:43:50 ack jea 17:43:50 jeanne, you wanted to talk about WAI-CooP and the plan for workshops for Sampling and Scoring 17:43:50 q+ 17:44:32 Jeanne: New WAI group funded by EU "WAI-COOP" [Wilco is in it]. In meeting with Shadi, who was suggesting 2 workshops. One on sampling, one on scoring. 17:44:36 q? 17:44:56 Jeanne: Could present some of our / WCAG 3 ideas on scoring, get expert feedback from such a workshop. 17:45:02 ack pet 17:46:57 ack jem 17:47:15 q? 17:47:18 Jemma: returning to how to respond to issue... will hold her thoughts. 17:48:48 Peter [attempting to scribe himself a few moments after the comments were made]: Shall we return to the GitHub issue? Respond thanking them for this idea, sharing our appreciate for it & that we will think about it. Then linking to the previous issues (#217) 17:49:12 q? 17:49:13 q+ to say that I do 17:49:28 Peter: (continuing), and without suggesting a solution, noting that there are organizations that allow some number of Critical bugs for some short amount of time. If there are critical a11y bugs, what then? 17:49:38 ack jea 17:49:38 jeanne, you wanted to say that I do 17:49:45 Jeanne: don't think we should link to 217. They are different enough, they might confuse things. 17:50:50 Jeanne: suggest we will get back to him when we have a specific proposal for him to look at (speaking of issue #277). 17:51:20 Sajka: we might also ask him to point us to documentation on the severity levels we can cite? 17:52:43 q? 17:52:44 peter: Suggest we add label. 17:53:05 Jeanne: cannot close the issue. When ready to close, needs to be in a survey that goes to AGWG, is closed by AGWG. 17:53:24 peter: good enough for in the subgroup, so we can track it 17:54:19 Peter: keep it in the group, looking at use cases. 17:54:41 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Procedure_for_Processing_Comments 17:54:55 q? 17:55:20 Jeanne: This has the draft answer templates. 17:56:00 Janina: looking for more information before we want to finalise 17:56:28 Jeanne: Could divide into separate issues. 17:57:13 rrsagent, make minutes 17:57:13 I have made the request to generate https://www.w3.org/2021/03/04-silver-conf-minutes.html jeanne 17:57:50 Janina: Not ready for a response. Will ask for more information on industry practices. 17:58:51 rrsagent, make minutes 17:58:51 I have made the request to generate https://www.w3.org/2021/03/04-silver-conf-minutes.html jeanne 17:59:08 ToddLibby has left #silver-conf 17:59:22 zakim, bye 17:59:22 leaving. As of this point the attendees have been sajkaj, PeterKorn, JF, Bryan, John_Northup, Azlan, sarahhorton, Wilco, ToddLibby, jeanne, Jemma 17:59:22 Zakim has left #silver-conf 17:59:27 rrsagent, make minutes 17:59:27 I have made the request to generate https://www.w3.org/2021/03/04-silver-conf-minutes.html sajkaj 18:00:16 rrsagent, make log public 18:00:24 rrsagent, make minutes 18:00:24 I have made the request to generate https://www.w3.org/2021/03/04-silver-conf-minutes.html sajkaj 20:09:12 jeanne has joined #silver-conf 21:29:43 jeanne has joined #silver-conf