13:49:44 RRSAgent has joined #wcag3-protocols 13:49:44 logging to https://www.w3.org/2022/03/04-wcag3-protocols-irc 13:50:46 agenda+ Pick 2-3 protocols to work with 13:51:07 agenda+ How to evaluate whether the protocol was done 13:52:00 agenda+ How well the protocol was followed 13:52:28 agenda+ How to evaluate the quality of the results (if possible) 13:54:34 present+ 14:01:59 JakeAbma_ has joined #wcag3-protocols 14:03:03 ShawnT has joined #wcag3-protocols 14:03:22 present+ 14:03:28 present+ 14:03:39 zakim, take up item 1 14:03:39 agendum 1 -- Pick 2-3 protocols to work with -- taken up [from Rachael] 14:03:42 julierawe has joined #wcag3-protocols 14:03:44 present+ 14:05:19 scribe: JakeAbma 14:05:44 https://docs.google.com/presentation/d/1b5xHQWBzoYdKp7BfPgIUBCpz-yaDOx_kSq_HlQxcFh0/edit#slide=id.p 14:06:16 agenda? 14:06:42 RM: start with couple of ideas on what a protocol might be, maybe 1, 2, or 3 14:06:53 RM: try to evaluate them 14:07:14 RM: see if it works, and if not why? 14:07:18 +1 14:08:00 Rachael: What protocols? 14:08:18 Jake: Not really new. Not for me and not as an approach. Its been discussed for years in the Netherlands. 14:09:27 Jake: The fastest way to explain it is if we can do a mapping in the way you might embed a protocol. It is up to the organization who makes the claim. So if we start from that approach. Then figure out if we think differently. Similar to maturing or approaching from protocol perspective. 14:09:47 ...We might for instance say "material Design" or "BBC Gel design" or "Engineering Culture document" 14:10:07 ...One guidance document (material design) 14:10:08 q+ 14:11:06 ...Something completely different and bigger and more structured. More ways to annotate design in the BBC Gel. And within our company, an internal week old engineering culture document. Or an ISO standard or internal standard. There is a broad perspective. 14:11:35 ...Do you need to use your own protocol or use an existing one. 14:12:15 q+ to say we need to define what makes a good protocol before we tell others to start doing it 14:12:20 +1 to plain language 14:12:27 q+ 14:12:29 ack Rachael 14:12:32 ack MichaelC 14:12:32 MichaelC, you wanted to say we need to define what makes a good protocol before we tell others to start doing it 14:13:06 ack JakeAbma_ 14:13:23 Current options: Plain Language, Material Design, BBC Gel, Engineering Culture 14:14:07 q+ 14:14:08 Jake: Chicken and Egg problem. What is the definition? Are we hijacking the word "protocol?" If we define its easy. A "protocol" can be anything. 14:14:12 jennifer_ has joined #wcag3-protocols 14:14:15 present+ 14:14:27 was in the wrong irc, #wcag-protocols 14:14:35 ...I think its very complicated if we narrow it down. Then its up to us to define which is and which isn't a protocol. 14:14:40 q+ 14:15:59 If we have a way to measure it, then suddenly that measurement doesn't count anymore. It fits in the other spectrum because we have the regular WCAG 3 way of measuring. I don't think we have a consensus. Clear words? The document proposed here in this group is different than arabic or from netherlands. Its a very local thing. 14:16:38 ...for specifically for US. I know that last year I had questions about clear words. 14:17:26 ack MichaelC 14:18:34 +1 MichaelC 14:18:38 ack Rachael 14:18:42 Current options: Plain Language, Material Design, BBC Gel, Engineering Culture 14:19:30 q+ 14:19:37 ack JakeAbma_ 14:19:37 Plain Language, BBC Gel, and then no vote for the other two 14:20:42 Plain Language, Material 14:20:47 JakeAbma_: I forgot exercise. Rachael reviewed 14:21:12 q+ 14:21:14 Plain Language 14:21:17 Rachael: Plain Language, Material, BBC Gel 14:21:27 ack jennifer_ 14:21:47 Rachael revised: Plain Language, BBC Gel 14:22:24 another example 14:22:24 https://ux.visma.com/ux-in-visma/ux-best-practices/ 14:22:44 +1 to adding UX 14:22:49 Could we put the links for all of them? I can do it and share right now 14:22:53 q+ 14:23:16 https://www.bbc.co.uk/gel 14:23:17 Jake: Suggests another option. 14:23:24 [BBC GEL | Homepage](https://www.bbc.co.uk/gel) 14:23:29 https://material.io/design 14:23:30 q+ 14:23:31 Jaunita_George has joined #wcag3-protocols 14:23:34 Present+ 14:23:54 Proposal: Plain Language, BBC Gel, UX Best Practices 14:24:08 ack jennifer_ 14:24:14 +1, any decision is the best decision :) 14:24:44 q+ 14:24:55 q+ 14:25:00 Key question: Is a protocol a document, part of hte document, and how do we handle overlap with WCAG 14:25:16 ack julierawe 14:25:54 For example, for BBC Gel, this is the section that I would propose: https://www.bbc.co.uk/gel/guidelines/how-to-design-for-accessibility 14:26:00 ack MichaelC 14:26:17 q+ 14:26:35 An alt Decision Tree? 14:26:37 ack JakeAbma_ 14:26:49 https://www.w3.org/WAI/tutorials/images/decision-tree/ 14:28:40 JakeAbma_: Agree. Important point. UX might be too big. Gel may be too big. Maybe we should use inclusive design principles. Its small. 14:28:45 https://inclusivedesignprinciples.org/ 14:28:50 https://inclusivedesignprinciples.org 14:28:59 Proposal: Plain Language, Inclusive Design Princples, UX Best Practices 14:29:14 ack Jaunita_George 14:29:43 JG: lots of guidance already has WCAG parts 14:30:51 Option 1: Plain language, UX Best Practices 14:30:59 Option 2: Plain language, BBC Gel 14:31:05 2 14:31:08 q+ 14:31:08 Option 2: Plain language, BBC Gel, UX Best Practices 14:31:26 (but specific to the accessibility area of BBC Gel) 14:31:28 Inclusive Design Principles 14:31:50 https://ux.visma.com/ux-in-visma/ux-best-practices/ 14:32:11 https://inclusivedesignprinciples.org 14:32:20 https://www.bbc.co.uk/gel/guidelines/how-to-design-for-accessibility 14:32:41 Please write your preference for the second document 14:33:15 UX 14:33:20 +1 to UX 14:33:30 I voted for #2, and scoped Gel to just the a11y section 14:34:03 UX 14:34:40 proposed proposals: Plain Language, Visma UX 14:34:55 proposed proposals: Plain Language, Visma UX, (BBC Gel A11y section if 3rd is needed) 14:35:11 proposed protocols for use in exercise: Plain Language, Visma UX, (BBC Gel A11y section if 3rd is needed) 14:35:23 +1 14:35:23 +1 14:35:41 zakim, take up next item 14:35:41 I see a speaker queue remaining and respectfully decline to close this agendum, Rachael 14:35:45 q? 14:35:49 ack JakeAbma_ 14:36:07 zakim, take up next item 14:36:07 agendum 2 -- How to evaluate whether the protocol was done -- taken up [from Rachael] 14:36:22 q+ 14:36:42 ack JakeAbma_ 14:38:44 JakeAbma_: Explain emails. First question is do you apply to WCAG? Answer is no. Been a no for the last 12 years. Now need to say whether you comply with EN 301 509 but if not, you have to do something about it. You have to make sure that you work on something to make sure your product will become more accessible. 14:39:01 ...instead of saying you ahve to do this or that. There is a set of extra rules to follow. Its left open. 14:39:39 q+ 14:40:55 ...Its up to org to say what to do. But its completely open. The government says you need to tell us what protocol. MAke a statement that you do not comply, state what protocol you took, also must provide proof. Example: You say you follow material design, state % teams that follow material design, what improvement, and by what date. 14:41:22 ...you say what you follow and provide proof. What part of protocol did you follow? How is that embeded? ?How can we see it? By what date? 14:41:32 q+ 14:41:53 ack Jaunita_George 14:42:01 Jaunita_George: akin to a VPAT in US. 14:42:17 q+ 14:42:29 JG: not sure if it works in US 14:43:02 JG: no one will ever get to the point that they have to prove 14:43:50 q+ to say following a protocol is continuous; measurement is discrete; protocol might define measurement frequency and acceptable improvement between measurements 14:43:56 JG: we need to build in objectivity 14:44:04 q+ 14:44:38 ack Rachael 14:44:38 JG: otherwise it might become something like a VPAT which does not work well 14:46:48 agenda? 14:47:02 What part of protocol did you follow? How is that embeded? ?How can we see it? By what date? 14:47:19 ack MichaelC 14:47:19 MichaelC, you wanted to say following a protocol is continuous; measurement is discrete; protocol might define measurement frequency and acceptable improvement between measurements 14:48:20 MC: your measureing effort for a protocol, not wcag compliance 14:48:20 an "as of" date would be fine MichaelC 14:48:52 ack JakeAbma_ 14:49:46 Jake: Purpose of protocols is for use on more subjective content. 14:50:37 ...Jeanne spoke 3-4 years ago with lawyers there was the possibility to add more subjectiveness. I'm not sure that's true or not. Its about measuring the effort. 14:50:56 q+ 14:52:22 JG: don't want protocols to move us backwards 14:52:38 q+ 14:52:40 ack j 14:52:50 JG: if we introduce subjectivity, it feels like it might collapse 14:52:58 q+ 14:53:19 ack MichaelC 14:53:20 ack me 14:53:29 JG: would like to see contact with people who know about how far we can introduce subjectivity 14:53:43 +1 to MichaelC 14:53:54 q+ 14:54:04 ack JakeAbma_ 14:55:02 JakeAbma_: I have read different blog posts about law suites. One of hte most well known was target. My recollection was it was not specifically that they complied with WCAG 100% but refused to do the effort of adding accessible names to images. They just refused to fix it. 14:55:18 q+ 14:55:20 ...they were blamed for that. If that is the case, then it is about effort and willingness to do something. 14:55:57 ...very objective, but often about the effort and willing to do adjustments. 14:56:06 ack Jaunita_George 14:56:48 i/+1 to MichaelC/mc: protocols can have non-subjective measures, such as % of FTE; having subjective measures as well goes beyond what I considered but it´s interesting to explore 14:57:15 ack Rachael 15:00:19 Suggestions for evaluating whether the protocol was done: What part of protocol did you follow? How is that embeded in content or organization? ?How can we see it? By what date? 15:00:35 zakim, make minutes 15:00:35 I don't understand 'make minutes', Rachael 15:00:42 rrsagent, make minutes 15:00:42 I have made the request to generate https://www.w3.org/2022/03/04-wcag3-protocols-minutes.html Rachael 15:00:58 rrsagent, make log world 15:02:19 zakim, end meeting 15:02:19 As of this point the attendees have been Rachael, ShawnT, MichaelC, julierawe, jennifer_, Jaunita_George 15:02:21 RRSAgent, please draft minutes 15:02:21 I have made the request to generate https://www.w3.org/2022/03/04-wcag3-protocols-minutes.html Zakim 15:02:24 I am happy to have been of service, Rachael; please remember to excuse RRSAgent. Goodbye 15:02:28 Zakim has left #wcag3-protocols 15:24:38 ShawnT has joined #wcag3-protocols 15:37:37 ShawnT has joined #wcag3-protocols 16:02:12 ShawnT has joined #wcag3-protocols