12:50:26 RRSAgent has joined #silver 12:50:26 logging to https://www.w3.org/2021/07/09-silver-irc 12:50:29 RRSAgent, make logs Public 12:50:30 Meeting: Silver Task Force & Community Group 12:51:25 agenda? 12:51:32 Meeting: Silver Task Force & Community Group 12:51:32 present: 12:51:32 chair: Shawn, jeanne 12:51:32 present+ 12:51:32 zakim, clear agenda 12:51:32 agenda cleared 12:51:32 rrsagent, make minutes 12:51:32 I have made the request to generate https://www.w3.org/2021/07/09-silver-minutes.html jeanne 12:51:32 q? 12:51:44 q- Jennifer 12:52:48 agenda+ new Method format proposal from joint ACT-Silver group 12:52:48 agenda+ updated proposal on Third Party content 12:52:48 agenda+ Subgroup update and schedule for August heartbeat 13:49:51 sajkaj has joined #silver 13:49:56 agenda? 13:50:00 present+ 13:54:37 jeanne has joined #silver 13:55:10 https://www.w3.org/2017/08/telecon-info_silver-fri 13:58:34 Jemma has joined #silver 13:58:48 Hi 13:59:10 Lauriat has joined #silver 14:00:00 PeterKorn has joined #silver 14:00:16 Present+ 14:00:19 Wilco has joined #silver 14:00:26 present+ 14:00:36 mgarrish has joined #silver 14:00:40 present+ 14:01:28 present+ 14:01:33 Francis_Storr has joined #silver 14:01:58 Makoto has joined #silver 14:02:06 agewnda? 14:02:11 scribe: sajkaj 14:02:11 agenda? 14:02:20 present+ 14:02:38 present+ 14:02:43 jeanne: Report on redesign from aCT to make rules less ambiguous 14:02:43 https://docs.google.com/document/d/1JVmquc7mLJaxZhypPbBhR99fEFBmc0YDn1Wz2Jcl_oY/edit?usp=sharing 14:03:07 Wilco: Trying to combine Silver Methods with ACT Rules 14:03:14 Wilco: Shares screen ... 14:03:19 JF has joined #silver 14:03:19 jenniferS has joined #silver 14:03:24 present+ 14:03:38 Wilco: Worked on updating decorative images methods 14:03:40 Present+ 14:03:54 Wilco: had rules that were close, which was reason for starting with this one 14:04:03 Wilco: more complicated items will come later 14:04:25 Wilco: tried to work out what a method needs in order to get a score 14:04:50 Wilco: reads what is needed ... 14:04:56 sarahhorton has joined #silver 14:05:06 Wilco: illustrates what we're trying to create 14:05:07 present+ 14:05:20 Wilco: this particular method turned out to be pretty straight forward 14:05:41 Wilco: notes a summary now within description 14:06:02 Wilco: two additions from ACT rule into method -- explain what must be present before testing 14:06:23 Wilco: also explanation of scope of test -- what's being tested 14:06:34 Wilco: e.g. testing the images aren't actually informative 14:06:44 Wilco: next come examples 14:06:53 Wilco: used ACT examples 14:07:12 Wilco: ACT examples include failing and passing examples 14:07:16 https://www.w3.org/WAI/standards-guidelines/act/rules/image-not-in-acc-tree-is-decorative-e88epe/#test-cases 14:07:20 Wilco: including why pass or fail 14:07:43 ToddLibby has joined #silver 14:08:08 q+ to comment on usability and what aspects that mostly apply to the test tool developers should be in accordions 14:08:26 Wilco: includes what to do with pass/fail paths 14:09:02 Wilco: notes applicability added to method; also some definitions 14:09:13 Wilco: definitions point into a glossary 14:09:17 +1 about glossary 14:09:39 q? 14:09:42 q+ 14:10:06 Wilco: proposing to add section on accessibility support -- things that might not work in all screen readers, browsers, etc; edge cases not considered 14:10:19 Wilco: lastly, new glossary section 14:10:53 wilco: q? 14:11:02 ack jeanne 14:11:02 jeanne, you wanted to comment on usability and what aspects that mostly apply to the test tool developers should be in accordions 14:11:10 present+ 14:11:33 jeanne: notes that many details could be hidden in expandable structures 14:11:38 ack Peter 14:11:38 ack PeterKorn 14:12:03 "Note: It is relatively common for an informative image such as an icon to be marked up as decorative, if the text alternative is adjacent to the image. This is a conforming alternative version for the image. This fails the rule but meets conformance requirement 1 of WCAG 2.1." 14:12:19 PeterKorn: curious note about some informative images with alt text adjacent -- that fail -- 14:12:41 Wilco: definitely one rule different from methods; something we'll have to sync 14:13:00 Wilco: probably new def of purely decorative; but currently out of scope of what we're trying to achieve 14:13:10 Wilco: trying to make methods more consistently testable 14:13:44 PeterKorn: suggests we might collect what's programatically testable, and what isn't for later examination; this seems one not testable today 14:13:50 Q+ 14:14:07 q? 14:14:36 sajkaj: On the glossary, would this fit into a central glossary so all WAI groups would reference? 14:15:15 W3C does have https://www.w3.org/2003/glossary/ 14:15:19 +1 for consistent reference mechanism 14:15:45 ack JF 14:16:00 [general approval for global glossary but may still have need for specific glossaries in some situations] 14:16:03 Full glossary https://www.w3.org/2003/glossary/subglossary/All/ 14:16:09 and priority in using authorative reference resources 14:17:00 jf: asks about cross referencing 14:17:27 jeanne: also not wanting to replicate same info in multiple locations that could vary because we restate, as opposed to include 14:17:29 +1 to JF 14:17:44 jeanne: notes that should be part of info display when we build the Silver db 14:18:01 Wilco: notes that will look at other methods; will this go in August? 14:18:32 jeanne: On AG schedule for the 13th; approval would mean would possibly go to subgroups and moving designs into WD 14:18:47 jeanne: will be a few "to be developed" editor's notes 14:19:06 agenda? 14:19:14 it would be great if this is using more plain language. 14:19:19 zakim, next item 14:19:19 agendum 1 -- new Method format proposal from joint ACT-Silver group -- taken up [from jeanne] 14:19:23 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Proposal_on_Third_Party_Content 14:19:29 Scribe: Lauriat 14:19:36 zakim, take up item 2 14:19:36 agendum 2 -- updated proposal on Third Party content -- taken up [from jeanne] 14:19:47 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Proposal_on_Third_Party_Content 14:20:14 sajkaj: Same link as before, but updated. New section on "What is Third Party Content?" 14:20:57 sajkaj: With sub-heading to clarify that this does not propose to specify exemptions for third party content 14:22:09 sajkaj: So much more third party content on the web today that it makes sense to define third party and what would fall under first party, but overall trying to improve the accessibility of third party content. 14:23:32 sajkaj: Includes a pointer to a page in the Library of Congress that isn't accessible as an example of the many things that can't be made accessible, but as a way of differentiating between what you can and can't do something about. 14:24:27 sajkaj: Lots of notes of explanation to help clarify things, rather than notes that we would want to put into the document itself. 14:25:11 sajkaj: Many examples of third party content documented (author-arranged, user-generated, etc.). 14:26:08 sajkaj: Given the range of quality of the third party content, we cannot require policing all of the content, but we can provide guidance of how to better support and make this content more accessible. 14:26:45 jeanne: Also guidance that belongs in a specific guideline vs. general guidance 14:27:23 sajkaj: We include some additional proposed guidance for alternative text, for instance. 14:27:53 sajkaj: Makoto already includes guidance on authoring tools. 14:28:14 (jeanne, not sajkaj, whoops) 14:28:37 qv? 14:28:55 q+ 14:29:06 q+ 14:29:09 JF: Example of hand-written document? 14:29:24 Digitized image archives of content predating the web. Examples of such legacy archives include portions of major national libraries such as the U.S. Library of Congress, the U.K. British Museum, and The Bibliothèque nationale de France Catalogue Général. A specific example is this Image of a handwritten 19th Century document at the U.S. Library of Congress. 14:29:26 https://www.loc.gov/resource/mss26526.002_0866_0888/?st=gallery 14:29:32 sajkaj: Yes, included that example. 14:29:40 A specific example is this Image of a handwritten 19th Century document at the U.S. Library of Congress. 14:30:02 ack Peter 14:30:37 PeterKorn: Process question, I have a collection of small edits, how can we best handle those? Post-survey or now? 14:30:45 q+ 14:30:51 jeanne: Post-survey, we already have people answering. 14:30:56 https://www.w3.org/2002/09/wbs/35422/3rdparty2/ 14:31:33 q+ 14:31:57 Jemma: Working on content from medical records system, with inaccessible things coming from there. Would that fall under this? 14:32:24 jeanne: Yes, under author-arranged. 14:33:19 PeterKorn: If the hospital takes an x-ray and digitizes it, they have the responsibility, so first party. If one organization gets it from the hospital, then third party content for the organization. 14:33:21 q- 14:33:27 ack Jemma 14:33:34 brb 14:33:59 q+ If the owner of the medical record is the vendor EPIC System , is it the EPIC system that talks to other doctor's offices or hospitals, is it then the EPIC system generator rather than the doctor that authored the note in the system? 14:34:15 jeanne: Another use case example we can document. 14:34:32 sajkaj: For those defining the records format, as well. 14:35:27 jenniferS: An example that came up recently, PDFs considered too laborious to make accessible and the organization considered it a "nice to have". 14:35:54 Jeanne is correct that university is responsible for this case 14:36:43 yes, exampe of redcap medical record system 14:36:48 jeanne: For organizations who are the consumer of data, we need to establish the producer as responsible. 14:36:55 s/exampe/example 14:37:06 q? 14:37:15 yes, EPIC is another example 14:37:41 q? 14:37:45 q+ 14:37:53 ChrisLoiselle: From a third party vendor, if a doctor produces content within a third party vendor's system, then the system itself would have the responsibility vs. the doctor themselves. 14:38:02 ack sarahhorton 14:38:02 ack sar 14:38:12 agreed, thanks Shawn. 14:38:21 q- 14:38:50 sarahhorton: On the point that it's not an exemption, how does this work exactly in WCAG3? 14:39:32 sajkaj: Trying to make conformance on this point that you've done everything that you can do vs. requiring everything to conform regardless of who produced the content. 14:39:43 sarahhorton: Critical errors? 14:41:07 jeanne: Yes, and we envisioned having third party outcomes as a way of documenting how to handle these cases (old movies without captions which can't have captions for whatever reason, etc.). 14:41:11 can we add EPIC/REDCAP use cases to the third party content? 14:41:25 q+ 14:41:28 +1 Sarah 14:41:35 (in queue for services example) 14:42:17 sarahhorton: Content vs. services, we don't have services examples, which would help. A third party authentication module used in place of an existing module, which then causes problems. 14:43:36 sajkaj: I don't think that example would conform. Mixes of the two also enter into things. 14:44:15 sarahhorton: An organization that chooses to use third party modules to avoid having to conform, in this case. 14:44:37 jeanne: A really good example that we should document. 14:45:21 sarahhorton: Third party payment gateway as another example, where it doesn't matter to me as a user who has the responsibility. 14:45:34 ack PeterKorn 14:47:25 PeterKorn: When, where, and how is it most effective for WCAG to drive change. If I want to accept a credit card, few credit card processing services exist to use. I may have little ability to drive change and also little ability to create my own alternative. 14:47:47 PeterKorn: The content examples come easily, but the services aspect becomes more difficult. 14:48:00 sarahhorton: Have you tried not addressing services as a part of this? 14:48:05 PeterKorn: Good question. 14:48:07 Why? Avoidance just kicks the problem down the road 14:49:10 PeterKorn: We could also try addressing it differently. (gives some examples of critical errors in services) 14:50:01 sajkaj: An example I've hit, where some of the service is inaccessible due to images with no alt text, but I still have a way to make it through to the end. 14:50:15 q+ to talk about profiles 14:50:48 PeterKorn: Maybe alt text guidance could include documenting things acceptable first-vs-third party. 14:50:54 ack jeanne 14:50:54 jeanne, you wanted to talk about profiles 14:50:55 ack jeanne 14:50:56 Would it be useful to distinguish by use case, too? 14:50:57 q- 14:51:18 For example, as the error criteria spells out health, finance, etc.? 14:51:46 jeanne: We could approach it that way and we could also approach it as a profile (from JF's proposal), so we can keep putting responsibility back on the service providers. 14:52:32 + 1 Jeanne 14:53:14 jeanne: In the U.S., today, typically people would bring lawsuits to the organization using the service, rather than the service provider. The organization could have an accessibility statement documenting what they've tried to do to provide an accessible path, pointing to the failures in the service provider. 14:53:35 +1 14:53:36 Q+ 14:53:41 In an A11y Statement, you could imagine: "We canvassed all 3rd party payment processors, and none met a11y requirements" 14:53:46 q+ 14:53:49 ack JF 14:54:24 q+ 14:54:25 JF: The concept of profiles hasn't really been fleshed out for everyone in the WG, but the assertions part could also provide a way of handling this. 14:54:30 +1 to JF 14:54:45 ack PeterKorn 14:54:59 ack peter 14:55:36 PeterKorn: One other thing, third party services can change. Accessible services can become inaccessible (iframe-rendered makes this common). 14:56:07 ack jenniferS 14:56:08 q? 14:56:09 +1 to that important wrinkle 14:56:31 jenniferS: And context, like health and finance. 14:57:09 that could be another example of a profile -- health care and finance 14:57:19 q+ 14:57:35 PeterKorn: It comes back to how we handle scoring, where maybe regulators could say health care needs to hit this particular level. 14:57:39 q+ to say I would rather see profiles with higher standards than different medals 14:57:41 ack PeterKorn 14:58:04 ack jeanne 14:58:04 jeanne, you wanted to say I would rather see profiles with higher standards than different medals 14:58:06 ack 14:58:30 jeanne: I'd rather see this handled with profiles, rather than adding different currencies. 14:58:51 Present+ 14:59:23 present+ 14:59:28 https://www.w3.org/WAI/GL/task-forces/silver/wiki/Project_Plan_for_Q3_Working_Draft 14:59:36 jeanne: Subgroup members, please look at plans for the August draft and email me with what you think you'll have for the August draft, with dates so I can get you scheduled for the joint AG WG meetings. 14:59:58 - If courts require WCAG compliance, and WCAG compliance can include inaccessible 3rd party content and services, are we undermining its value as a measure of accessibility, and way to prevent exclusion and discrimination? 15:01:05 ToddLibby has left #silver 15:01:19 Zakim, make minutes 15:01:19 I don't understand 'make minutes', Lauriat 15:01:31 RRSAgent, make minutes 15:01:31 I have made the request to generate https://www.w3.org/2021/07/09-silver-minutes.html Lauriat 15:03:03 Zakim, end meeting 15:03:03 As of this point the attendees have been jeanne, sajkaj, Lauriat, Wilco, PeterKorn, Jemma, Makoto, mgarrish, jenniferS, JF, sarahhorton, ToddLibby, Francis_Storr 15:03:06 RRSAgent, please draft minutes v1 15:03:06 I have made the request to generate https://www.w3.org/2021/07/09-silver-minutes.html Zakim 15:03:08 I am happy to have been of service, Lauriat; please remember to excuse RRSAgent. Goodbye 15:03:13 Zakim has left #silver 15:17:33 rrsagent, make minutes 15:17:33 I have made the request to generate https://www.w3.org/2021/07/09-silver-minutes.html jeanne 16:48:30 jeanne has joined #silver 23:18:59 jeanne has joined #silver