16:50:02 RRSAgent has joined #silver-conf 16:50:02 logging to https://www.w3.org/2022/02/10-silver-conf-irc 16:50:27 Meeting: Silver Conformance Options Subgroup 16:50:35 date: 10 feb 2022 16:50:39 chair: janina 16:50:45 rrsagent, make log public 16:50:49 agenda? 16:51:08 regrets: Todd_Libby 16:52:35 Agenda+ Agenda Review & Administrative Items 16:52:35 agenda+ User Scenarios: Additional Considerations 16:52:35 agenda+ Other Business 16:52:35 agenda+ Be Done 16:52:37 16:59:13 rrsagent, make minutes 16:59:13 I have made the request to generate https://www.w3.org/2022/02/10-silver-conf-minutes.html janina 16:59:37 shadi has joined #silver-conf 16:59:54 present+ 17:00:03 present+ 17:00:27 present+ 17:01:23 DarrylLehmann has joined #silver-conf 17:01:46 PeterKorn has joined #silver-conf 17:02:01 present+ 17:02:33 present+ 17:02:38 present+ 17:03:11 Wilco has joined #silver-conf 17:03:20 Azlan has joined #silver-conf 17:03:33 present+ 17:03:38 present+ 17:03:41 scribe: Wilco 17:03:50 zakim, take up next 17:03:50 agendum 1 -- Agenda Review & Administrative Items -- taken up [from janina] 17:04:16 Janina: Had some additional comments, some from me, some from Jeanne. 17:04:24 ... Thanks to Shadi for helping to put them in. 17:05:00 ... TPAC planning continues. We'll start asking who might be there in person. 17:06:09 zakim, take up next 17:06:09 agendum 2 -- User Scenarios: Additional Considerations -- taken up [from janina] 17:07:19 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Talk:Substantial_Conformance/Example_Scenarios 17:07:25 Shadi: I dropped a summary of the comments in the talk page 17:07:44 ... Going to situation 9 heading 17:07:54 ... Would suggest lack of AT support should factor in. 17:08:25 ... Two example, one on limited support for accessibility; immersive environments. 17:08:48 ... 9.2 talks about experiences that can not easily be translated. 17:09:13 ... I'd like to suggest a 9.3 highlighting the lack of accessibility support 17:09:35 ... Graphs, there isn't really a way to visualise that. 17:10:06 ... There could also be something like music, where music notes and words are side by side that is not easily rendered by AT. 17:10:21 Would we want to use the phrase "Accessibility Supported" for this/these scenarios? 17:10:45 +1 Janina and Shadi example addition 17:10:47 ... Question to the group is do we add such example? 17:11:02 q+ 17:11:07 q- 17:11:08 q+ 17:11:18 q+ 17:11:28 Shadi: We'd have to phrase that carefully, accessibility support related to technology. 17:11:48 Janina: little nervous about accessibility support. It may get controversial. I'd rather phrase it another way. 17:12:28 ... If we get a standard for doing something. The process is usually we get a spec, and then over time we get AT support for that. 17:13:29 Darryl: Another example is WebGL, online 3D. There is basically no support. 17:13:56 ... There was a 3D model online which had labels, we replicated that with a 3D printed model with braille 17:14:19 Janina: The only place we have accessibility support built into graphics is SVG 2 17:14:26 queue= 17:14:56 Gregg: If you had graphs with lines, would it be more useful to have a table? 17:15:14 q+ 17:15:16 ... We have the ability to take a picture of a chart and give a table with the data. 17:16:31 q- 17:16:36 Janina: Tables if you concentrate well you can get the picture, but there's a reason for charts. 17:16:47 [I need to step away; be right back] 17:16:48 ... Things communicate more quickly 17:17:00 Gregg: I would suggest diagram of a heart, instead of lines on a graph. 17:17:08 Shadi: Sounds good 17:18:55 Shadi: Janina mentions an APA note on how to approach real-time calls. I had further discussions on that. 17:19:19 [I'm back] 17:19:52 ... WCAG 2 already has different requirements for live vs prerecorded media. One of the things Janina raises is synchronisation of captions, and the transition from live to prerecorded. 17:20:21 ... Suggestion is to add this to the guidance section. 17:21:22 Gregg: There's a task force looking at real-time text in ISO, which could have impact. 17:21:36 q+ 17:21:36 ... I don't think we want to add requirements, but we could have examples. 17:21:48 ... For example you can have word by word live captions. 17:22:05 ... There is also caption synchronisation software. 17:22:46 ... In life captions is behind as you won't know what someone will say, but after it should be put in sync. 17:22:58 ack jan 17:23:23 Janina: We've been living this. Many things happen on Zoom, but then are put on YouTube hours later. 17:23:47 .. We can leave it to policy how much someone needs to do. 17:24:12 Gregg: If we can put tools in the understanding docs so people can find them. 17:24:25 ... Saying they exist doesn't help, putting a link does. 17:25:29 Shadi: Hearing agreement 17:26:07 ... The next item is on situation 2. There is a new bullet from Janina. 17:27:17 ... It occurred to me that maybe framing, the question is does all content need to be accessible. 17:27:33 ... There is an upon request, but there is also content that is not essential. 17:27:43 q+ Gregg 17:28:11 ... It's not about relevance. It's under which condition can you say pieces will not follow all the requirements. 17:28:13 q+ 17:28:20 ... There is a role for policy here. 17:28:24 ack g 17:28:51 Gregg: If it's important enough to post it for anybody, it shouldn't be not important for some people. 17:29:27 q+ 17:29:52 ... If you have a huge archive, what we'll do if we need it we'll be responsive, I hate for us to say some things don't need to be accessible because they're not used much. 17:30:27 ... I'd rather we make a comment on policy. 17:31:03 Shadi: Some content won't have the highest priority. It's being phrased as relevant. 17:31:34 ack j 17:32:02 Janina: We should not perpetuate the assumption that we'll do everything for all content. It gets in the way. 17:32:43 ... This is about prioritisation. You should be able to do it. 17:32:46 ack 17:32:49 ack pko 17:32:53 q- 17:33:22 Shadi: I'll go forward and rephrase that in terms of priority. 17:34:14 Shadi: Under the heading Overall comments. Jeanne and I feel we need another section. 17:34:28 maryjom_ has joined #silver-conf 17:34:35 q 17:34:36 q+ 17:34:47 ... The key datapoint is that 98% have fewer than 100 employees. There was more in the comment here. From that I have a few suggestions. 17:34:50 present+ 17:35:17 q- 17:35:24 Peter: We have examples of this in the US today. We might note that this has already been done in accessibility laws 17:36:08 q+ 17:36:35 No objection; I think it makes a lot of sense - especially because this is already practice 17:36:38 Shadi: Also in EU legislation, EAA exempts micro organisations. Still is there any downside, would anybody object to a situation of a small business who have difficulty finding the right professionals, tooling, knowledge. 17:36:39 +1 17:37:08 Janina: I think the concern to consider, are we saying enough that a small business is likely to rely on a scripted website provider. 17:37:21 ... Are these number big enough that we need to say more? 17:37:52 ... We've covered a lot of user generated, but third-party HTML / CSS. Apparently that's been on a rapid rise. 17:38:39 q? 17:38:50 q+ 17:39:16 Shadi: This is the first of several additions to address small business. This particular suggestion on situation 11. 17:39:17 ack janina 17:40:04 ... I want to mention that policy makers should consider the size and capability of the content provider. 17:40:29 ... It's one thing to say for a small shop that they can't make all images accessible. That's a policy question. 17:40:49 ... Policies will now exempt small businesses, and sometimes have reasonability concepts built in. 17:41:24 Darryl: I agree adding this example is useful. Just the fact that there is a lack in the space to creating accessible content. 17:41:39 ... Companies should find good specialists, that'd kind of the problem as well. 17:42:26 https://almanac.httparchive.org/en/2021/third-parties 17:42:44 Shadi: There is a strong dependance on tools. In 4.1 we have an example; website that allows users to create their own website. It's written from the perspective of the tool provider. 17:43:29 ... The suggestion is to create a similar example under 5; I created a website using a tool that creates websites. That tool has limitations and I'm dependant on what that tool can provide. 17:43:36 +1 17:43:43 +1 17:43:51 +1 17:44:09 Shadi: No objections; I'll get that drafted. 17:44:36 ... Following that we can add guidance around selecting appropriate tools. 17:44:58 ... EO is working on a list of authoring tools supporting accessibility. 17:46:29 q+ 17:47:06 q- 17:47:16 Janina: There's an implicit guarantee, if you get in trouble over not being accessible. You should be able to duck out of it. 17:47:41 Peter: We have two proofs in this space, architects in the ADA, and now web business that promise overlays fix problems. 17:47:57 ... I would not go down this road other than to say this is all about policy. 17:48:16 ... This can suck our time. 17:48:28 Shadi: If we can phrase this as a consideration rather than a solution? 17:49:23 q+ 17:49:23 Azlan: It's quite the can of worms. One thing I've been working on is an authoring tool. Needing to provide enough tooling for someone to create whatever they want. I don't want to be too restrictive, but still protect them from causing issues. 17:49:33 ... Where do you draw the line of who's responsible? 17:49:42 ack azlan 17:49:53 Janina: I think this would be a win if we get this in appropriately. 17:50:10 ack jan 17:50:37 Gregg: I think we should say people need to put it in the contract. If you don't put it in the contract, you can't get out of it. 17:51:08 Janina: I'm not sure that's true. They may not know they need to think about it. 17:51:29 Gregg: That's why we need to tell people to put it in their contract, and that they have it checked. 17:51:49 q? 17:52:46 Shadi: I'll see what I can do with that. I'm hearing we don't want to get into detailed solutions, but maybe there's something on considerations for tool providers. 17:54:28 ... We have situation 6. Janina has a point where she says we need to be clear that bugs do happen, so that we make a strong case. There's no bug-free software. 17:54:45 q? 17:55:10 Peter: I wonder if we can say something between "will" and "can". Virtually all software has bugs. 17:55:56 Janina: I'd love to see us cite some things. 17:56:24 https://www.mayerdan.com/ruby/2012/11/11/bugs-per-line-of-code-ratio 17:57:57 Shadi: Situation 5 is on dependencies on other services. There's maybe more interlinking between sites than people think. 17:58:16 ... We didn't have any specific suggestion / conclusion. Maybe we can get back to it next week. 17:58:17 https://almanac.httparchive.org/en/2021/third-parties 17:59:11 Janina: I think we need to be comprehensive when we return with third-party to AGWG. We have a good start, but there is a lot more going on, but someone has to be responsible. 17:59:40 ... It goes a lot further than I had realised. Hopefully we can think more globally on how to draw lines. 18:00:58 zakim, end meeting 18:00:58 As of this point the attendees have been janina, GreggVan, shadi, PeterKorn, DarrylLehmann, MichaelC, Azlan, Wilco, maryjom_ 18:01:00 RRSAgent, please draft minutes 18:01:00 I have made the request to generate https://www.w3.org/2022/02/10-silver-conf-minutes.html Zakim 18:01:03 I am happy to have been of service, Wilco; please remember to excuse RRSAgent. Goodbye 18:01:08 Zakim has left #silver-conf