14:56:11 RRSAgent has joined #wcag2ict 14:56:15 logging to https://www.w3.org/2024/01/04-wcag2ict-irc 14:56:16 RRSAgent, make logs Public 14:56:17 Meeting: WCAG2ICT Task Force Teleconference 14:56:18 zakim, clear agenda 14:56:19 agenda cleared 14:56:24 chair: Mary Jo Mueller 14:56:30 meeting: WCAG2ICT Task Force Teleconference 14:56:36 Zakim, please time speakers at 2 minutes 14:56:36 ok, maryjom 14:56:42 Agenda+ Announcements 14:56:52 Agenda+ Project status and standup 14:57:04 Agenda+ Status of AG WG comments on our content review 14:57:12 Agenda+ Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2 15:00:58 Mike_Pluke has joined #wcag2ict 15:01:01 Chuck has joined #wcag2ict 15:01:35 shadi has joined #wcag2ict 15:02:28 present+ 15:02:39 present+ 15:02:43 present+ 15:02:43 scribe: bruce_bailey 15:03:11 maryjom: Apologies for late agenda 15:03:18 present+ 15:03:28 Bryan_Trogdon has joined #WCAG2ICT 15:03:35 present+ 15:03:45 Agenda also posted at: https://lists.w3.org/Archives/Public/public-wcag2ict-tf/2024Jan/0000.html 15:03:46 present+ 15:03:55 zakim, agenda 15:03:55 I don't understand 'agenda', bruce_bailey 15:03:58 present+ Daniel 15:03:59 zakim, agenda? 15:03:59 I see 4 items remaining on the agenda: 15:04:00 1. Announcements [from maryjom] 15:04:00 2. Project status and standup [from maryjom] 15:04:00 3. Status of AG WG comments on our content review [from maryjom] 15:04:01 4. Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2 [from maryjom] 15:04:05 zakim, take up item 1 15:04:05 agendum 1 -- Announcements -- taken up [from maryjom] 15:04:42 maryjom: I am process of taking inventory of WCAG2ICT left... 15:05:03 there is a lot, but I think we can conclude timely... 15:05:05 Devanshu has joined #wcag2ict 15:05:10 present+ 15:05:19 In surveys, please propose responses and complete early... 15:05:40 ... if early, I have been able to incorporated edits into most recent PRs. 15:06:20 maryjom: At out last meeting, 12/14, there was some openess to having a second weekly call. 15:06:43 I could do Friday 15:06:43 What is folks availablility Wed or Friday? 15:06:47 q+ 15:06:53 I could do Friday, not Wednesday. 15:06:54 ack Chuck 15:07:20 Friday works for me. 15:07:21 Chuck: Friday better 15:07:29 Friday is OK, Wednesday at this time out for me. 15:07:57 Friday 9am ET is available 15:08:02 Friday works for me 15:08:13 maryjom: It might be a subgroup working on some issues between weeks and grist for surveys. 15:08:45 maryjom: I feel like I am a gating factor at this point, but I need some more input. 15:09:10 maryjom: i will set up something for the hour before, fri 9:00 to 10:00 Eastern 15:09:27 ...we have to get content in if we are to publish in March 15:09:51 ...will be short term, maybe just January. 15:10:20 I think we have good handle on remaining content, but need some more live calls. 15:10:36 ack chuck 15:10:37 q? 15:11:02 Chuck clarifies, we will even try for tomorrow. 15:11:20 q+ for other announcement 15:11:26 ack bruce_bailey 15:11:26 bruce_bailey, you wanted to discuss other announcement 15:11:58 bruce_bailey: Mention for feds, some stuff between holidays, guidance from OMB for federal agencies. 15:12:15 bruce_bailey: GSA published reporting for conformance across govt. 15:12:29 bruce_bailey: I will paste in the links. 15:12:50 zakim, take up item 2 15:12:50 agendum 2 -- Project status and standup -- taken up [from maryjom] 15:13:23 maryjom: I have been going through list of issues, assessing status of item in progress... 15:13:51 ...before vacation I was looking particularly for public comments which might be surveyed. 15:14:06 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comment-responses/ 15:14:11 ... there are a couple surveys open, due 2/11, but reply asap 15:14:46 ... 2nd one following up on closed functionality, so i lpulled in those changes 15:14:46 survey: closed functionality - https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-SC-problematic-last-5/results 15:15:18 ShawnT has joined #wcag2ict 15:15:31 present+ 15:15:39 ... other thing is survey on Consistent Help, that is almost done. 15:15:41 q+ 15:15:52 maryjom: keep look out for that, I will send out email 15:16:30 maryjom: there are also a couple surveys which have been completed, but we have not discussed on a call... 15:16:37 ... will get to some of those today. 15:17:10 maryjom: The other status item is a few folks working on changes from feedback survey. 3.3.8 Accessible Authentication (Minimum)... 15:17:40 ... few folks were working on note, and I have reached out to refresh that deliverable. 15:18:12 maryjom: We have also previously dicussed 2.5.8 Target Size minimum... 15:18:31 ... a couple people were going to take another look at CSS pixel. 15:19:23 maryjom: Another item in progress is the AGWG review. I wanted to update on status, as deadline was extended a week. 15:19:48 ... We did get a couple down votes on 4.1.1 Parsing.... 15:20:17 ... this will be coming befor AGWG on 1/9 tuesday, please attend that portion of the call if you can... 15:20:54 ... Concern is around how we provide guidance around 2.0 and 2.1 -- 2.2 specific guidance is okay. 15:21:26 ... I am not sure there is anymore we can do, since if markup is wrong, barrier will surface from other SC fails. 15:22:31 maryjom: For Dragging Movements, there was also conversation which was significant. I will consolidate the responses and choices around user agents in survey proposal. 15:23:01 ... Hopefully this will address all issues from AG review... 15:23:32 ...We do have public comments needing response, which is my priority for Friday meetings. 15:23:34 q? 15:23:46 ack bruce_bailey 15:24:16 Bruce asks about Closed Functionality survey 15:24:26 Open survey on closed functionality: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-closed-more-to-review/ 15:25:47 maryjom: Not seeing anyone on call with open issues assigned other than Mike, but I do think we will be consensing on those. 15:26:09 maryjom: I would love to have proposed answers to public comments. 15:26:12 q+ 15:26:33 maryjom: We cannot publish again without closing those. 15:26:57 q+ 15:27:04 maryjom ask chuck about Public Comments with responses. Do I need to contact person? 15:27:32 Chuck: The answer which you have provide with the @ is sufficient. 15:28:01 maryjom: That is helpful, since hard to track duplicative via email. 15:28:06 ack Ch 15:28:23 chuck: Some feedback is anonymous, so there is no other option. 15:28:30 q? 15:28:35 maryjom: not seeing replies on GitHub 15:28:36 q? 15:28:41 ack bru 15:29:06 bruce_bailey: I was going to say, I just engaged with someone this morning. Q came from github. If she gets back to me, my idea is to ask her to close the issue. 15:29:11 q+ 15:29:25 ack Chuck 15:29:32 +1 to bruce_bailey 15:30:01 Chuck: We can close, and not dependent of person opening issue to close... 15:30:09 ask them to close it, give them a time frame, if not closed after X days close it for them 15:30:35 ...our main responsibility is to the working group. But we do want to satisfy the person raising the question. 15:31:11 q+ 15:31:12 maryjom: I am having people respond to issues which the original question has a satisfactory answer. 15:31:42 maryjom: Issues turning into discussion thread results not being able to close. 15:31:44 q+ 15:32:11 maryjom: I did try and reply on issue to this minor conflict. 15:32:13 ack Ch 15:32:13 ack Chuck 15:32:45 Chuck: Not only do we have right to keep threads scoped, it is also our responsibility to do so. 15:32:50 ack bruce_bailey 15:33:11 bruce_bailey: I was going to suggest that you can turn issues into discussions and they can be more free flowing. 15:33:20 maryjom: Yes, I have asked OP to that effect. 15:33:47 maryjom: Original thread really went off topic from orignal question raised in issue. 15:34:01 maryjom: Any other concerns? 15:34:29 maryjom: We will start tomorrow morning with new replies to public comments. 15:34:38 zakim, agenda? 15:34:39 I see 4 items remaining on the agenda: 15:34:39 1. Announcements [from maryjom] 15:34:39 2. Project status and standup [from maryjom] 15:34:40 3. Status of AG WG comments on our content review [from maryjom] 15:34:40 4. Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2 [from maryjom] 15:34:53 Zakim, take up item 4 15:34:53 agendum 4 -- Survey results: Closed functionality bullets for SCs 2.1.2, 2.1.4, 2.4.7, 2.5.2, 3.1.1, 3.1.2, 3.2.3 and 4.1.2 -- taken up [from maryjom] 15:35:09 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-SC-problematic-last-5/results 15:35:19 Maryjo: Skipping to 4, since we already covered 3 at the top of the call. 15:36:02 maryjom: This is the closed survey on Closed Functionality, but we had not discussed. 15:36:31 Pointer Cancellation: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-SC-problematic-last-5/results#xq1 15:37:13 7 respondants, 6 okay with as-is. Mitch had an alternative, as he would prefer to remove. 15:37:56 maryjom: I don't have objections to restating as Mitch suggests. 15:38:03 Option 1: Proposed draft as-is 2.5.2 Pointer Cancellation—There are cases in closed functionality software where there are essential features that would meet the exception to this success criterion. Examples include features for meeting environmental energy usage requirements (like waking a device from sleep, power saver mode, and low power state). 15:38:22 Option 2: 2.5.2 Pointer Cancellation—As noted in the section [Applying SC 2.5.2 Pointer Cancellation to Non-Web Documents and Software], examples of 'essential' functionality are features for meeting environmental energy usage requirements (like waking a device from sleep, power saver mode, and low power state). 15:38:39 Which do you prefer? Option 1 or Option 2? or something else? 15:38:54 option 2 15:39:07 Option 2 15:39:11 2 15:39:16 2 15:39:33 2 15:40:00 bruce_bailey: There is only one example, not multiple examples. 15:40:33 Mary Jo check current draft... 15:41:53 RESOLUTION: Incorporate 2.5.2 Pointer Cancellation option 2, as above as-is, into the SC problematic for Closed Functionality section 15:42:26 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-SC-problematic-last-5/results#xq2 15:43:52 Language of Page, 3.1.1 15:44:12 7 respondants, 3 as-is 15:44:19 Option 1: Updated version: 3.1.1 Language of Page—Requires language information in a programmatically determinable form intended to drive correct pronunciation. Self-voicing is already required for closed functionality software to support, with the correct pronunciation of language(s) supported by the software. 15:45:13 Option 2: Loic's edit: 3.1.1 Language of Page—Requires language information in a programmatically determinable form intended to drive correct pronunciation. Accessible systems with closed functionality are required to provide speech output and to use the correct pronunciation of language(s) supported by the software. 15:45:37 Option 3: Mitch's proposed update: Requires language information in a programmatically determinable form intended to drive correct pronunciation. Where another mechanism achieves correct pronunciation for closed functionality, such as self-voicing, this criterion does not apply. 15:45:58 Poll: Which do you prefer? Option 1, 2 or 3, or something else? 15:46:50 3 15:46:53 3 15:46:57 3 15:46:59 3 15:47:07 3 15:47:56 RESOLUTION: Incorporate 3.1.1 Language of Page bullet using Option 3 as-is into the SC problematic for closed functionality section. 15:48:48 Language of parts question - https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-SC-problematic-last-5/results#xq3 15:49:29 7 responses, 1 as is. 5 for option 2 or option 2 with edits. 15:50:55 maryjom: Bruce prefered option 1, but with an edit and was okay with option 2... 15:51:16 Option 1: Proposed update, as-is 3.1.2 Language of Parts—Requires information in a programmatically determinable form. Support for correct pronunciation of other languages embedded in other content would require alternate means to produce correct pronunciation and can be difficult for closed functionality software to support. 15:51:22 Mitch had a succinct edit, which migh also be applicable to 3.1.1 15:51:25 Option 2: With suggested edits 3.1.2 Language of Parts—Requires language information in a programmatically determinable form intended to drive correct pronunciation. Where another mechanism achieves correct pronunciation for closed functionality, such as self-voicing, this criterion does not apply. 15:51:50 Option 3: 3.1.2 Language of Parts—Requires language information in a programmatically determinable form intended to drive correct pronunciation. Where another mechanism achieves correct pronunciation for closed functionality, such as self-voicing, the intent of this success criterion would be met. 15:52:01 Maryjo: I think option 3 incorporates survey feedback. Poll please. 15:52:19 Poll: Which do you prefer? Option 1, 2, or 3, or something else? 15:52:32 3 15:52:33 3 15:52:35 3 15:52:36 3 15:53:00 3 15:53:38 maryjom: I also propose we update note for 3.1.1, but take that up after this one. 15:53:51 UTION: Incorporate 3.1.2 Language of Parts bullet using Option 3 as-is into the SC problematic for closed functionality section. 15:54:03 s/UTION/RESOLUTION/ 15:54:12 rrsagent, make minutes 15:54:13 I have made the request to generate https://www.w3.org/2024/01/04-wcag2ict-minutes.html maryjom 15:55:27 maryjom: I also want to poll updating previous resolution. 15:55:45 Poll: Do you agree to change the last phrase for SC 3.1.1 above from "this criterion does not apply" to "the intent of this success criterion would be met". Yes or no. 15:56:01 yes 15:56:12 Yes 15:56:16 yes 15:56:40 RESOLUTION update the text for 3.1.1 bullet to replace the phrase "this criterion does not apply" to "the intent of this success criterion would be met". 15:56:56 s/RESOLUTION/RESOLUTION:/ 15:57:47 rrsagent, make minutes 15:57:48 I have made the request to generate https://www.w3.org/2024/01/04-wcag2ict-minutes.html dmontalvo 15:57:56 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-SC-problematic-last-5/results#xq4 15:58:12 3.2.3 Consistent Navigation AND 3.2.4 Consistent Identification 15:58:26 7 replies, 4 and 3 15:58:47 Do we keep bullets or not? 15:59:28 Poll: Do we keep bullets in for SC's that have the "sets of" in the SC Problematic for Closed FUnctionality? Yes or no 16:00:17 Remove bullets if only one option, keep if more than one 16:00:54 Bruce: Plug for 508 report i mentioned at top of call: https://www.section508.gov/manage/section-508-assessment/2023/ 16:01:15 Olivia: I think bullets might need some editorial 16:01:33 maryjom: There are four SC which present use bullets. 16:01:42 ... will address tomorrow 16:01:57 rrsagent, make minutes 16:01:58 I have made the request to generate https://www.w3.org/2024/01/04-wcag2ict-minutes.html dmontalvo 16:02:04 maryjom: We do have a lot of work over the next few weeks 16:07:37 PhilDay has joined #wcag2ict