13:47:40 RRSAgent has joined #wcag2ict 13:47:40 logging to https://www.w3.org/2022/10/06-wcag2ict-irc 13:47:43 RRSAgent, make logs Public 13:47:44 please title this meeting ("meeting: ..."), maryjom 13:47:55 zakim, clear agenda 13:47:55 agenda cleared 13:48:08 meeting: WCAG2ICT Task Force Teleconference 13:48:43 agenda+ Announcements 13:48:53 agenda+ Continue discussion on survey results from the work statement review 13:49:02 agenda+ Review/approve Pull Request 2682 13:49:14 agenda+ Next steps for the WCAG2ICT Work Statement 13:49:26 agenda+ As time allows, begin learning GitHub 13:49:37 regrets: Daniel Montalvo 13:49:40 MichaelC has joined #wcag2ict 13:49:48 agenda? 13:54:41 Chuck has joined #wcag2ict 13:54:49 agenda? 13:57:29 lmiller has joined #wcag2ict 13:58:10 BryanTrogdon has joined #wcag2ict 13:58:17 shadi has joined #wcag2ict 13:58:33 Devanshu has joined #wcag2ict 13:58:35 present+ 13:58:59 present+ 13:59:05 scribe: shadi 13:59:11 present+ 13:59:24 present+ 13:59:46 present+ 14:00:27 present+ 14:00:34 agenda? 14:00:37 present+ 14:00:52 ShawnT has joined #wcag2ict 14:01:32 Rachael has joined #wcag2ict 14:01:37 FernandaBonnin has joined #WCAG2ICT 14:02:04 present+ 14:02:09 Zakim, please time speakers at 2 minutes 14:02:09 ok, maryjom 14:02:13 bruce_bailey has joined #wcag2ict 14:02:23 present+ 14:02:36 present+ 14:02:46 present+ 14:02:47 present+ 14:03:25 AnastasiaLanz has joined #wcag2ict 14:03:39 present+ 14:03:44 present+ 14:03:48 present+ 14:03:57 zakim, take up agendum 1 14:03:57 agendum 1 -- Announcements -- taken up [from maryjom] 14:03:59 olivia-hogan-stark has joined #wcag2ict 14:04:30 Judy has joined #wcag2ict 14:04:37 present+ 14:04:39 maryjom: we have some volunteers for editors 14:04:43 present+ 14:04:58 ...need to discuss process with leadership 14:05:08 MichaelC: no hard and fast rules 14:05:10 present+ 14:05:19 ...sometimes good to have multiple editors 14:05:31 ...helps bridge availability gaps 14:05:50 ...and to balance out each other 14:06:00 ...this document had several editors 14:06:15 q+ to ask if we have co-facilitator 14:06:18 ...need to keep track, also to acknowledge 14:06:38 maryjom: will discuss with leadership and update the group 14:07:03 maryjom: hope we can finalize Work Statement today 14:07:18 ...let's focus on big issues that must be resolved 14:07:43 ...so that we can get closure this meeting 14:07:57 maryjom: I tried an approach with email thread on previous comments 14:08:02 ack bruce 14:08:02 bruce_bailey, you wanted to ask if we have co-facilitator 14:08:02 ack Bru 14:08:11 ...that didn't work very well, we will change that approach 14:08:20 q+ 14:08:30 bruce_bailey: is there a co-facilitator from a different sector? 14:08:48 maryjom: no, this position is still open 14:08:59 ...but we want to move on 14:09:01 ack Ch 14:09:08 [jb: notes that Chuck is acting co-facilitator for now] 14:09:09 ...while trying to recruit for this position 14:09:20 q+ 14:09:38 Chuck: my role is only temporary until someone is found 14:09:57 ...Judy is actively looking at potential candidates 14:10:13 ack Ch 14:10:15 Judy: yes, working on that, also on geographical diversity 14:10:16 Mary Jo and Chuck doing a great job! 14:10:35 zakim, take up next 14:10:35 I see a speaker queue remaining and respectfully decline to close this agendum, shadi 14:10:38 q? 14:10:41 ack j 14:10:42 ack Judy 14:10:44 q- 14:10:44 zakim, take up next 14:10:45 agendum 2 -- Continue discussion on survey results from the work statement review -- taken up [from maryjom] 14:10:56 https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2002_09_wbs_55145_WCAG2ICT-2Dwork-2Dstatement_results&d=DwMFAg&c=jf_iaSHvJObTbx-siA1ZOg&r=O4GqIExuqcdLwnUGEjvgSq08AYAj0SMVYacBFPfUo5Y&m=ZyQJj55-ohhfkVxnP5cFKGr_1dwxJbBbNRWxCGinZERXbr7RnYsq4t4D0uZ6RHIA&s=a3fPzdbRm7IkbK50sHN87gcRWhaSj3YuF4JjeaZSuiQ&e= 14:11:07 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-work-statement/results 14:11:23 maryjom has changed the topic to: Recap and actions from last meeting 14:12:19 subtopic: Recap and actions from last meeting 14:13:20 subtopic: Questions 9. Patent Policy section 14:13:23 maryjom: addressed comments 14:13:46 Draft RESOLUTION: Accept Patent policy section. 14:13:48 maryjom: no changes proposed to this section, propose resolution to accept it 14:13:51 +1 14:13:54 +1 14:13:54 +1 14:13:54 +1 14:13:56 +1 14:13:56 +1 14:13:58 +1 14:13:59 +1 14:13:59 +1 14:13:59 +1 14:13:59 +1 14:14:03 +1 14:14:06 +1 14:14:17 RESOLUTION: Accept Patent policy section. 14:14:39 subtopic: Question 2. Scope of Work section 14:15:10 maryjom: three themes here 14:15:34 ...1 definition of non-web ICT mentioned in the note but not in the Work Statement 14:15:46 ...seems to be consensus to keep the definition 14:17:15 Applying WCAG to hardware aspects of products, non-user interface aspects of platforms, or user-interface components as individual items, because the basic constructs on which WCAG 2.0 is built do not apply to these. 14:18:10 q+ 14:18:22 q? 14:18:25 ack gregg 14:18:25 ack Gregg 14:18:35 +1 to shadi's suggestion 14:18:43 GreggVan: is there are reason to stick that in the scope? 14:19:02 ...will that dictate potential edits later on? 14:19:32 +1 to substituting WCAG 2.0 to WCAG 2 14:19:33 ...things changing while we're working 14:19:51 ...rather than tying us from the start 14:20:08 maryjom: there were several suggestions in favor 14:20:27 GreggVan: don't feel strongly, just wondering about the reason 14:20:54 ...do we then have to use these exact words in the final? 14:21:13 ...don't understand the reasons for that but fine either way 14:21:34 maryjom: don't think it limits us from adjusting later on if we need to 14:21:45 q+ 14:21:46 q+ 14:21:58 q+ to speak to the editorial change of WCAG 2.0 to WCAG 2 14:22:01 ...suggestion to exclude BIOS or such aspects? 14:22:17 ack Gr 14:22:17 ...not sure we need to do that here in the scope but need to keep in mind 14:22:19 ack gregg 14:22:37 GreggVan: actually BIOS should not be out of scope 14:23:03 ...there are systems where you can adjust the BIOS while the system is starting up 14:23:23 ...can't just say BIOS, we need to separate this 14:23:39 ...also, might have login before assistive technology is loaded 14:23:49 ack thorsten 14:23:52 ...not true of the systems today 14:24:05 ThorstenKatzmann: agree we need to work on the wording 14:24:19 ...possibly BIOS is not precise enough 14:24:45 ...but still think we need recognize there are areas where this is not possible 14:25:06 q+ 14:25:07 ...we also need to put it in the scope to signal to other parallel efforts 14:25:18 ack chuck 14:25:18 Chuck, you wanted to speak to the editorial change of WCAG 2.0 to WCAG 2 14:25:24 ...we have dependencies back and forth 14:25:48 Chuck: there was a suggestion to change WCAG 2.0 to WCAG 2 or WCAG 2.x 14:25:56 ...minor editorial change 14:25:59 ack bryan 14:26:09 maryjom: will include that 14:26:13 +1 for "WCAG 2" versus "WCAG 2.x" 14:26:32 BryanTrogdon: examples would help understand what is in and out of scope 14:26:44 G+ to say suggest 2.x or WCAG series and not just WCAG 2 because that can be interpreted as 2.0 14:26:53 ...not suggesting for this particular section but need to understand 14:27:03 q+ 14:27:09 q? 14:27:14 q+ to say suggest 2.x or WCAG series and not just WCAG 2 because that can be interpreted as 2.0 14:27:24 ack lmiller 14:27:25 ...for example, is a thermostat an ICT? if so, what makes it an ICT? 14:27:55 q+ to make a general comment on the discussion 14:28:00 lmiller: asking us to agree now? 14:28:02 q+ 14:28:22 BryanTrogdon: yes, would help solidify understanding 14:28:41 ...especially what makes something in or out of scope? 14:28:47 ack GreggVan 14:28:47 GreggVan, you wanted to say suggest 2.x or WCAG series and not just WCAG 2 because that can be interpreted as 2.0 14:29:35 GreggVan: should speak specifically about WCAG 2.2 14:30:14 ...regarding the definition of ICT, this is regulatory or policy and not for us to say 14:30:21 q+ 14:30:43 ack Judy 14:30:43 Judy, you wanted to make a general comment on the discussion 14:30:45 ...gets dangerous to define what is ICT and what isn't 14:30:51 q+ to say definition of ICT 14:31:00 ...shouldn't try to limit, just cover it 14:31:43 Judy: WCAG is the starting point 14:31:55 ...agree that defining ICT could be an endless task 14:32:08 ...and can change according to jurisdiction 14:32:21 ack Ch 14:32:22 ack chuck 14:32:32 ...voting on what is and what isn't ICT might not help the group come together 14:32:36 ack lmiller 14:32:37 lmiller, you wanted to say definition of ICT 14:33:36 lmiller: so we agree that there is no clear definition for ICT? 14:33:48 q? 14:33:54 ...and that we include everything that could be ICT? 14:33:58 Judy: no 14:33:59 q+ 14:34:05 ack GreggVan 14:34:26 lmiller: then we need to define or at least some boundaries 14:34:33 q+ 14:34:48 GreggVan: we will need to consider it and scope our wording 14:34:58 ...but not define it from the start 14:35:27 +1 to MJ 14:35:35 +1 to Maryjom 14:35:48 +1 to MaryJo 14:35:53 maryjom: don't think we can cover all what can and cannot be in scope until we start working 14:36:00 +1 to MaryJo 14:36:02 also +1 to @maryjom that we dont need ict def for work statement 14:36:09 +1 to MaryJo 14:36:11 +1 14:36:17 q? 14:36:21 ack pday 14:36:38 pday: agree with the discussion 14:36:48 +1 to Phil 14:36:48 +1 pday 14:36:56 ...we need to keep this in mind as we get into the work but not define it upfront 14:37:11 q+ on examples 14:37:18 ack ChrisLoiselle 14:37:18 ChrisLoiselle, you wanted to comment on examples 14:37:26 ...also examples of what we mean for the individual clauses of the document would be helpful 14:37:28 https://ictbaseline.access-board.gov/glossary/ 14:37:41 ChrisLoiselle: one potential definition 14:37:54 q+ 14:38:37 ack Ch 14:38:53 Poll: Do we need to add the out-of-scope statement that I had in the email to the Work statement? 14:39:03 Applying WCAG to hardware aspects of products, non-user interface aspects of platforms, or user-interface components as individual items, because the basic constructs on which WCAG 2.0 is built do not apply to these. 14:39:32 +1 if statement should be added, -1 if not 14:39:51 -1 14:39:51 +1 or +0 14:39:53 -1 14:39:53 +1 14:39:54 -1 14:40:00 +1 if we adjust the WCAG 2.0 14:40:04 -1 14:40:13 +1 14:40:17 +1 14:40:25 change to +0 14:40:27 q+ 14:40:49 ack Gregg 14:40:59 +1 14:41:07 +1 14:41:11 GreggVan: [thinking out loud] 14:41:32 Like Laura, I'm changing mine, but from +1 to 0. 14:41:34 q+ 14:41:35 ...some hardware aspects in which it can apply 14:41:52 ...not all apply, that's clear but some may apply 14:41:54 q> 14:41:56 q? 14:41:57 q+ to say "user-interface components as individual items" i find awkward 14:42:17 ...so suggest going on provision level rather than global 14:42:22 ack lmiller 14:42:33 q+ 14:43:37 ack bruce_bailey 14:43:37 bruce_bailey, you wanted to say "user-interface components as individual items" i find awkward 14:43:46 lmiller: does ICT include a screen reader to read the content, and if so do we require a hardware jack or similar? 14:44:03 +1 to Bruce 14:44:07 bruce_bailey: suggest changing as little as possible from last time 14:44:13 +1 to Bruce 14:44:14 q? 14:44:21 ack Rachael 14:44:23 ...also find the current wording quite awkward 14:45:27 q+ 14:45:29 Rachael: I am mostly concerned with the same phrase as Bruce but I find the entire statement a bit unclear and am concerned about accidentally moving something out of scope that should not be. 14:45:35 maryjom: wording is from the current note 14:45:36 This document does not comment on hardware aspects of products, non-user interface aspects of platforms, or user-interface components as individual items, because the basic constructs on which WCAG 2.0 is built do not apply to these. 14:46:06 ack Rachael 14:46:06 q? 14:46:15 maryjom: if we remove it, then we are opening the scope to many more situations 14:46:21 ack GreggVan 14:46:23 Rachael: I will not object if consensus leans the other way 14:46:47 GreggVan: the question is why put it in the scope? 14:47:00 ...we can't add any provisions in this document anyway 14:47:18 ...not sure what the concerns are about requiring new things 14:47:32 q? 14:48:04 Poll: Do we need to add the out-of-scope statement that I had in the email to the Work statement? 14:48:16 -1 14:48:20 -1 (but will not object) 14:48:25 -1 14:48:29 bruce_bailey_ has joined #wcag2ict 14:48:49 +1 but will not object if removed 14:48:51 +1 14:48:56 +0 14:48:57 +0 14:49:08 Poll: Do we need to add the out-of-scope statement that I had in the email to the Work statement? 14:49:18 0 14:49:22 -1 14:49:43 -1 14:49:44 bruce_bailey: strong -1 14:49:53 q+ 14:50:13 ThorstenKatzmann: think it would be useful to have the statement in that prominent place 14:50:23 ...happy to work on the wording if needed 14:50:42 -1 14:51:32 Chuck: would you object to keeping it in the note but not add to the Work Statement? 14:51:39 https://www.w3.org/TR/wcag2ict/ and 1.1. Excluded from Scope is where we had this in prior version , which was in the note 14:51:39 We have consensus! 14:51:44 ThorstenKatzmann: fine for me if it is written down 14:52:07 maryjom: so conclusion is what we will not add it to the Work Statement 14:52:34 RESOLUTION: The scope of ICT covered will remain in the note and not in the work statement. 14:53:09 subtopic: Whether to include AAA requirements 14:53:38 maryjom: general agreement seems to be OK to include but with clear warning 14:53:46 Sorry to not mention earlier, but 508 definition for ICT is here: https://www.access-board.gov/ict/#E103.4 14:53:50 ...and only if time allows us to work on this 14:53:58 +1 to including AAA but prioritizing A and AA 14:54:03 +1 14:54:11 q+ 14:54:14 q+ 14:54:14 ack Ch 14:54:19 ack pday 14:54:21 We included examples, but as @GreggVan noted -- examples are problematic 14:54:36 From Mary Jo's email - The WCAG2ICT document itself could include WCAG’s conformance note: 14:54:36 It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA Success Criteria for some content. 14:54:50 +1 14:54:53 pday: concerned about others using this work later on in other contexts 14:54:53 but better than NOT including examples 14:55:03 ack FernandaBonnin 14:55:14 ...and the terms informative and normative are sometimes difficult to distinguish 14:55:18 q+ 14:55:27 ...so a clear warning is essential 14:55:49 q? 14:55:50 q+ 14:55:59 ack ChrisLoiselle 14:56:00 FernandaBonnin: not sure if time will be sufficient to address all AAA requirements 14:56:16 ChrisLoiselle: echoing Fernanda and others 14:56:25 ack maryjom 14:56:30 ...alignment with A & AA is far more important 14:56:51 maryjom: have seen AAA added to VPAT 14:57:08 ...also EN 301 549 has it in a different section 14:57:21 ...so can potentially see a similar approach 14:57:23 +1 to having it be separate 14:57:44 ...where it is clearly distinguished with a warning 14:57:46 q+ 14:57:51 ack GreggVan 14:58:03 +1 to AAA as separate table (i.e., status quo) 14:58:23 q+ 14:58:23 GreggVan: maybe clearly say it will be in a separate section 14:58:30 ...because that is raising concerns 14:58:37 ack Fern 14:58:40 Poll: We will keep AAA in scope, keep it separate with WCAG's strong warning, and address later after A and AA are addressed. 14:58:47 q+ 14:59:01 q_ 14:59:03 FernandaBonnin: how separate is separate? 14:59:04 I have a hard stop as well. 14:59:05 q- 14:59:13 ...maybe appendix or such 14:59:18 ...needs to be defined 14:59:32 +1 14:59:32 +1 14:59:37 +1 14:59:37 +1 14:59:38 +1 14:59:39 +1 14:59:40 +1 14:59:41 +1 14:59:42 +1 14:59:45 +1 14:59:46 +0 14:59:51 +1 15:00:11 RESOLUTION: We will keep AAA in scope, keep it separate with WCAG's strong warning, and address later after A and AA are addressed. 15:00:14 I think "WCAG's strong waring" is previous WCAG2ICT warning 15:00:27 MaryJo: No more changes for work statement. 15:00:40 proposed RESOLUTION: Agree to scope statement as ammended. 15:00:49 +1 15:00:56 draft RESOLUTION: Agree to Scope section with any amendments in the pull request 15:00:58 +1 15:00:59 +1 15:01:02 +1 15:01:02 +1 15:01:03 +1 15:01:05 +1 15:01:07 +1 15:02:02 q+ 15:03:29 RESOLUTION: Agree to Scope section with any amendments in pull request 2682. 15:03:45 thanks 15:04:11 rrsagent, make minutes 15:04:11 I have made the request to generate https://www.w3.org/2022/10/06-wcag2ict-minutes.html maryjom 15:39:45 maryjom has joined #wcag2ict 16:43:04 maryjom has joined #wcag2ict 17:09:49 maryjom has joined #wcag2ict 19:04:09 maryjom has joined #wcag2ict