15:00:27 RRSAgent has joined #wcag2ict 15:00:31 logging to https://www.w3.org/2024/02/15-wcag2ict-irc 15:00:38 RRSAgent, make logs Public 15:00:39 Meeting: WCAG2ICT Task Force Teleconference 15:00:39 zakim, clear agenda 15:00:39 agenda cleared 15:00:39 chair: Mary Jo Mueller 15:00:43 meeting: WCAG2ICT Task Force Teleconference 15:00:45 olivia has joined #wcag2ict 15:00:48 LauraBMiller has joined #WCAG2ICT 15:00:48 Zakim, please time speakers at 2 minutes 15:00:48 ok, maryjom 15:01:37 loicmn has joined #wcag2ict 15:01:38 shadi has joined #wcag2ict 15:01:45 present+ 15:01:48 present+ 15:01:59 Regrets: Shawn Thompson, Bruce Bailey, Fernanda Bonnin 15:02:04 mitch11 has joined #wcag2ict 15:02:07 present+ 15:02:26 present+ 15:02:26 present+ 15:02:32 present+ 15:02:33 Present+ 15:02:34 present+ 15:02:53 GreggVan has joined #wcag2ict 15:03:08 scribe+ olivia-hogan-stark 15:03:10 present+ 15:03:15 zakim, next item 15:03:15 I see nothing on the agenda 15:03:23 agenda? 15:03:32 Agenda+ Announcements 15:04:03 present+ Daniel 15:04:04 Agenda+ Survey results for the Review of 3.3.8 Accessible Authentication notes and SC problematic for closed guidance 15:04:05 Announcements Survey results regarding responses to public comments - Group 1, starting at question 4 - Issue 216 Survey results for public and TF comments Survey results for the Review of 3.3.8 Accessible Authentication notes and SC problematic for closed guidance 15:04:24 Agenda+ Survey results regarding responses to public comments - Group 1, starting at question 4 - Issue 216 15:04:34 Agenda+ Survey results for public and TF comments 15:04:45 zakim, next item 15:04:45 agendum 1 -- Announcements -- taken up [from maryjom] 15:05:11 Bryan_Trogdon has joined #WCAG2ICT 15:05:18 present+ 15:05:19 maryjom: With Laura's help, we have pulled together conversations around closed functionality 15:05:28 https://github.com/w3c/wcag2ict/wiki/Work-left-for-second-public-draft 15:05:52 maryjom: Have people made progress on self-assigned items? 15:07:08 laurabmiller: Reach out if anyone wants me to to chat about an item 15:08:08 maryjom: Let me know so I can create surveys. No more open surveys for this week. We are waiting on content for a few things. 15:08:12 zakim, next item 15:08:12 agendum 2 -- Survey results for the Review of 3.3.8 Accessible Authentication notes and SC problematic for closed guidance -- taken up [from maryjom] 15:08:30 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Accessible-auth-round3/results 15:08:44 https://docs.google.com/document/d/1op2IO_LEUr9hafvX1doPkwZ2iV1928o_dKgBVl5UYQk/edit?usp=sharing 15:08:58 Topic: SC 3.3.8: Note 3 15:09:09 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Accessible-auth-round3/results#xq4 15:10:32 maryjom: 4 said to incorporate as is, Loïc had some edits. 15:11:11 q+ 15:11:13 q? 15:11:16 maryjom: Any concerns with adding Loïc's text? 15:11:16 ack GreggVan 15:12:14 +1 for Loic's proposal 15:12:31 +1 15:12:40 DRAFT RESOLUTION: Incorporate Note 3 by adding “If the non-web software is an application” to the beginning of the sentence. 15:12:44 +1 15:12:49 +1 15:12:50 Sam has joined #wcag2ict 15:12:59 present+ 15:13:10 +1 15:13:13 +1 15:13:18 RESOLUTION: Incorporate Note 3 by adding “If the non-web software is an application” to the beginning of the sentence. 15:13:40 Topic: SC 3.3.8: Note 4 15:13:42 Updated language should therefore be: Note 3: If the non-web software is an application, passwords used to unlock the underlying platform software are out of scope for this requirement as these are not up to a software application’s author. 15:13:51 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Accessible-auth-round3/results#xq5 15:14:27 maryjom: All 5 said to incorporate as proposed in google doc 15:14:51 DRAFT RESOLUTION: Incorporate Note 3 by adding “If the non-web software is an application” to the beginning of the sentence. 15:14:57 +1 15:15:08 DRAFT RESOLUTION: Incorporate Note 4 as proposed in the survey. 15:15:14 +1 15:15:16 +1 15:15:16 +1 15:15:18 +1 15:15:34 RESOLUTION: Incorporate Note 4 as proposed in the survey. 15:15:36 Note 4: See also the Comments on Closed Functionality. 15:15:55 +1 15:15:58 Topic: SC 3.3.8: Part 1 - content in SC problematic for closed functionality 15:16:12 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Accessible-auth-round3/results#xq6 15:16:55 maryjom: 5 preferred option 2, as is 15:17:06 https://docs.google.com/document/d/1op2IO_LEUr9hafvX1doPkwZ2iV1928o_dKgBVl5UYQk/edit#heading=h.g5mgm937pv8c 15:17:17 Option 2 (replaces “methods” with “mechanisms” in the text): 3.3.8 Accessible Authentication (Minimum) - There are situations where meeting this success criterion is problematic: ... 15:17:17 ... 15:17:20 Systems that are designed for shared use (such as in a public library) or have closed functionality might block mechanisms typically used to assist the user, such as copying authentication information from a password manager. Instead, an alternative authentication method might be helpful, such as an identity card scanner. 15:17:25 q+ 15:17:30 ack GreggVan 15:17:32 ack GreggVan 15:17:47 q+ 15:18:13 GreggVan: Methods is better than mechanisms because mechanisms applies to a physical thing. 15:18:37 ack PhilDay 15:18:38 GreggVan: I would go with option 1 15:18:57 q+ 15:19:04 philday: I disagree, mechanisms is used in the SC 15:19:30 GreggVan: Both are used, and it is only in the exceptions 15:19:36 For reference, https://www.merriam-webster.com/dictionary/mechanism#:~:text=%3A%20a%20process%2C%20technique%2C%20or,or%20by%20accident%20Richard%20Bentley 15:20:04 Poll: Use 1) "method" or 2) "mechanism in the language? 15:20:20 2 15:20:23 1 but could live with 2 15:20:30 2, but would accept 1 15:20:32 2 15:20:33 2 15:20:34 2 but can accept 1 15:20:44 oops on the language 15:21:18 can accept 2 15:21:24 q- 15:21:31 loicmn has joined #wcag2ict 15:21:38 present+ 15:21:48 DRAFT RESOLUTION: Incorporate part 1 of the SC problematic for closed functionality for SC 3.3.8 as proposed in Option 2 in the Google doc 15:21:51 2 15:22:02 +1 15:22:04 +1 15:22:17 +1 15:22:28 q+ to ask if we can fix the language 15:22:33 +1 15:22:33 +1 15:22:36 =1 15:22:37 +1 15:22:55 https://w3c.github.io/wcag2ict/#accessible-authentication-minimum 15:23:23 RESOLUTION: Incorporate part 1 of the SC problematic for closed functionality for SC 3.3.8 as proposed in Option 2 in the Google doc 15:23:24 +1 15:23:35 Option 2 (replaces “methods” with “mechanisms” in the text): 3.3.8 Accessible Authentication (Minimum) - There are situations where meeting this success criterion is problematic: 15:23:42 ... Systems that are designed for shared use (such as in a public library) or have closed functionality might block mechanisms typically used to assist the user, such as copying authentication information from a password manager. Instead, an alternative authentication method might be helpful, such as an identity card scanner. 15:24:09 Topic: SC 3.3.8: Part 2 - Content in SC problematic for closed functionality 15:24:21 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Accessible-auth-round3/results#xq7 15:24:31 https://docs.google.com/document/d/1op2IO_LEUr9hafvX1doPkwZ2iV1928o_dKgBVl5UYQk/edit#heading=h.l241pv9zuirv 15:24:52 maryjom: 1 said as is, 4 said with edits 15:25:40 +1 to Olivia & Mary Jo's edits 15:25:51 q+ 15:26:03 Where standards for banking or security have authentication requirements that are regulated or strictly enforced, those requirements may take legal precedence over Success Criterion 3.3.8 Accessible Authentication (Minimum). 15:26:17 ack PhilDay 15:26:17 PhilDay, you wanted to ask if we can fix the language 15:26:27 ack GreggVan 15:27:54 GreggVan: Soon as we say "take precedence" people will take advantage of that 15:28:14 Minor edit to include Gregg's suggestion: Where standards for banking or security have authentication requirements that are regulated or strictly enforced, those requirements may be judged to take legal precedence over Success Criterion 3.3.8 Accessible Authentication (Minimum). 15:28:38 +1 to last proposal 15:28:47 +1 to Gregg's edit 15:28:53 +1 15:28:56 +1 15:28:58 +1 15:28:59 Poll: Are you OK with Gregg's edit? +1, -1 or 0 15:29:03 +1 15:29:03 +1 15:29:03 +1 15:29:07 +1 15:29:07 +1 15:29:12 +1 15:29:16 +1 15:29:19 +1 15:29:25 Suggested content therefore becomes: Where standards for banking or security have authentication requirements that are regulated or strictly enforced, those requirements may be judged to take legal precedence over Success Criterion 3.3.8 Accessible Authentication (Minimum). 15:29:52 RESOLUTION: Incorporate part 2 of the SC problematic for closed functionality for SC 3.3.8 as edited in the text shown in IRC (Phil's entry). 15:30:33 Resolved language: Where standards for banking or security have authentication requirements that are regulated or strictly enforced, those requirements may be judged to take legal precedence over Success Criterion 3.3.8 Accessible Authentication (Minimum). 15:31:30 woo hoo 15:31:50 √ 15:32:09 zakim, next item 15:32:10 agendum 3 -- Survey results regarding responses to public comments - Group 1, starting at question 4 - Issue 216 -- taken up [from maryjom] 15:32:41 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-Jan-public-responses/results#xq6 15:34:00 https://github.com/w3c/wcag2ict/issues/216 15:34:12 Option 1 [For non-web documents or software] content [implemented using markup languages or software in a way that supports modification of] the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: 15:34:20 Option 2 [For non-web documents or software] content [implemented using markup languages, or that supports modification of] the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: 15:35:16 maryjom: Most liked option 2 as is. Mitch had concerns with language. Gregg had editorial change. 15:35:44 q+ 15:36:28 ack mitch 15:37:21 +1 to mitch 15:37:48 mitch11: We don't have to make them the same because WCAG doesn't have them the same. No reason we can't look at them differently. 15:38:51 Option 2 (attempt to insert Mitch's conditional) [For non-web documents or software] content [implemented using markup languages that supports modification of] the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: 15:38:59 q+ 15:39:37 q 15:39:41 q+ 15:40:02 ack GreggVan 15:40:43 greggvan: It's not just the software, it has to be the platform. 15:40:59 https://w3c.github.io/wcag2ict/#text-spacing 15:42:17 Option 2 (attempt to insert Mitch's conditional, with typo corrected) [For non-web documents or software] content [implemented using markup languages that support modification of] the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: 15:42:21 ack PhilDay 15:42:22 maryjom: This one is for general guidance 15:42:47 q+ to ask if these are listed in the closed functionality section 15:42:56 I would support Phil's edit 15:43:48 q+ 15:43:56 Q+ 15:44:13 ack GreggVan 15:44:14 GreggVan, you wanted to ask if these are listed in the closed functionality section 15:45:03 maryjom: to respond to Gregg's question, this is listed. 15:45:14 q? 15:45:18 ack mitch 15:46:40 q+ 15:46:40 Option 3 (attempt to insert Mitch's new broader coverage) [For non-web documents or software] content [that support modification of] the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: 15:46:52 ack LauraBMiller 15:47:09 mitch: I noticed that Phil's edit reverts it back to no change. 15:49:52 q? 15:49:57 ack GreggVan 15:50:01 laurabmiller: do we agree that it should be expanded? 15:51:44 need to drop, I will review editor responsibilities with Mary Jo and Phil. Great work all! 15:51:51 GreggVan: we expanded to beyond mark up languages. If we go there, we are expanding on WCAG. 15:52:35 Poll: Should both SC 4.1.3 Status Messages and 1.4.12 Text Spacing be scoped only to content implemented in markup languages in WCAG2ICT? 1) Yes, 2) No or 3) I don't know 15:53:12 1 15:53:14 1 15:53:26 3. I'm tempted to say 1, so we don't go beyond the scope of WCAG. But, it is nice to give guidance when we can... 15:53:34 3 15:53:34 2, if the language allows it. Otherwise it must be 1. 15:53:41 q+ 15:54:05 ack GreggVan 15:54:24 Now 1! 15:54:39 q+ 15:54:44 1 15:54:49 1 15:55:26 q+ to say Would this proposal work? 15:55:26 Option 2 (attempt to insert Mitch's conditional, with typo corrected) [For non-web documents or software] content [implemented using markup languages that support modification of] the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: 15:56:10 q? 15:56:11 ack mitch 15:57:11 1 because everything else (programmatic access to status messages) is covered by other SC 15:57:19 https://w3c.github.io/wcag2ict/#applying-sc-4-1-3-status-messages-to-non-web-documents-and-software 15:57:38 Above link is the "Applying SC 4.1.3" in latest draft 15:57:43 ack PhilDay 15:57:43 PhilDay, you wanted to say Would this proposal work? 15:59:41 q+ 15:59:51 maryjom: with Parsing we did not expand outside of mark up languages 16:00:21 maryjom: with status messages we did. This will be a Friday conversation. 16:01:43 rrsagent, make minutes 16:01:44 I have made the request to generate https://www.w3.org/2024/02/15-wcag2ict-minutes.html olivia 16:01:53 thank you, hope you feel better Mary Jo 16:02:31 zakim, bye 16:02:31 leaving. As of this point the attendees have been shadi, olivia, mitch, maryjom, loicmn, ChrisLoiselle, LauraBMiller, PhilDay, GreggVan, Daniel, Bryan_Trogdon, Sam 16:02:31 Zakim has left #wcag2ict 16:08:47 rrsagent, bye 16:08:47 I see no action items