13:46:25 RRSAgent has joined #wcag2ict 13:46:29 logging to https://www.w3.org/2024/08/15-wcag2ict-irc 13:46:29 RRSAgent, make logs Public 13:46:30 Meeting: WCAG2ICT Task Force Teleconference 13:46:45 zakim, clear agenda 13:46:45 agenda cleared 13:46:49 chair: Mary Jo Mueller 13:46:57 Zakim, please time speakers at 2 minutes 13:46:57 ok, maryjom 13:47:06 Agenda+ Announcements 13:47:14 Agenda+ Survey results: (Group 1) Review changes due to comments on second public draft 13:47:21 agenda? 13:47:27 rrsagent, make minutes 13:47:28 I have made the request to generate https://www.w3.org/2024/08/15-wcag2ict-minutes.html maryjom 13:52:44 PhilDay has joined #wcag2ict 13:59:40 present+ 13:59:44 agenda? 13:59:53 scribe+ PhilDay 13:59:54 regrets: Fernanda Bonnin, Daniel Montalvo 14:01:03 Mike_Pluke has joined #wcag2ict 14:01:29 present+ 14:01:35 present+ 14:01:44 Chuck has joined #wcag2ict 14:02:02 FernandaBonnin has joined #WCAG2ICT 14:02:05 agenda? 14:02:15 maryjom has joined #wcag2ict 14:02:40 zakim, next item 14:02:40 agendum 1 -- Announcements -- taken up [from maryjom] 14:02:52 olivia has joined #wcag2ict 14:02:55 mitch11 has joined #wcag2ict 14:03:01 Still a number of issues that we are working on - approx 15 issues 14:03:17 About half are not yet assigned or started 14:03:36 present+ 14:03:47 Rest have some action - e.g. Daniel's have some PRs that need review. 14:03:58 No other WCAG2ICT announcements. 14:04:11 We are working in Google doc for the proposed changes in response to the open issues. 14:04:16 zakim, next item 14:04:16 agendum 2 -- Survey results: (Group 1) Review changes due to comments on second public draft -- taken up [from maryjom] 14:04:26 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comments-july/results 14:04:33 (Group 1) Review changes due to comments on second public draft 14:04:41 Devanshu has joined #wcag2ict 14:04:47 We got through 2 questions last week, as the discussion with Jan Jaap took some time. 14:04:54 present+ 14:05:04 Bryan_Trogdon has joined #WCAG2ICT 14:05:15 present+ 14:05:32 maryjom: Question: I have documented the decisions on "sets of" but still have to discuss with lots of people in issues and direct emails. Should we just put this in the wiki? 14:05:43 bruce_bailey has joined #wcag2ict 14:05:58 q+ 14:05:58 Q+ 14:06:09 ack mitch11 14:06:12 ack mitch 14:06:33 present+ 14:06:35 ack Mike_Pluke 14:06:43 mitch11: Useful - don't present as "we decided in 2013, and have never touched it" - instead "desktop software still exists, and still has the same constraints" 14:06:50 Mike_Pluke: Also agree that it would be useful 14:07:00 zakim, agenda? 14:07:00 I see 1 item remaining on the agenda: 14:07:01 2. Survey results: (Group 1) Review changes due to comments on second public draft [from maryjom] 14:07:25 present+ 14:07:33 present+ 14:07:35 Poll: Is documenting the decisions made in 2013 (and thought through again recently) for handling of "sets of" criteria (5 of them) in the WIKI a good idea? 1) Yes 2) No. 14:07:42 1 14:07:43 +1 14:07:44 1 14:07:46 1 14:07:50 1 14:07:50 1 14:07:54 1 14:08:11 q- 14:08:11 maryjom to take existing content and make wiki page on "sets of". Link will be shared with TF for input and review. 14:08:50 Back to the survey 14:08:58 Link to survey results: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comments-july/results 14:09:15 We will be skipping around in the survey - do quick things first 14:09:28 TOPIC: Question 6, Issue 431 – 2.5.2: An example has been inserted into a WCAG Note and not listed as a substitution 14:09:40 Issue 431 link: https://github.com/w3c/wcag2ict/issues/431 14:09:49 Google doc: https://docs.google.com/document/d/1o6ruxbOKxAU6aWWz9Ac7P8DMi7lrIwXCy5DgvRzQZA4/edit#heading=h.686paq75g6ka 14:09:51 Question link: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comments-july/results#xq6 14:10:05 \Pull request 454: https://github.com/w3c/wcag2ict/pull/454/files 14:10:42 s/\Pull request/Pull request 14:10:45 Survey results. 4 said option 2 ready as is, 1 said option 3 ready as is 14:11:29 Option 2: Move the added example below Note 4, and explain in word substitution 14:11:29 Move the added example out of the WCAG note. Keep issue #414 in mind, which also affects this SC's notes. 14:11:29 Update the word substitution to read: 14:11:29 This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.2, making changes to the notes for non-web documents by replacing “web content” with "content", for non-web software applications by replacing "web content that interprets" with "user agents and other software applications that interpret", 14:11:30 andreplacing "user agent" with "underlying platform software", and adding an example; and for non-web platform software by replacing "web content" with "platform software". 14:11:30 Option 3: Move the added example below all the notes 14:11:30 This has the disadvantage of separating the information about essential exceptions, but it has the advantage of the example not getting inserted in the middle of WCAG content. 14:12:13 q+ to say go with consensus 14:13:36 Option 2 - cleaned up with deleted text removed 14:13:37 Option 2: Move the added example below Note 4, and explain in word substitution 14:13:37 Move the added example out of the WCAG note. Keep issue #414 in mind, which also affects this SC's notes. 14:13:37 Update the word substitution to read: 14:13:37 This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.2, making changes to the notes for non-web documents by replacing “web content” with "content", for non-web software applications by replacing "web content that interprets" with "user agents and other software applications that interpret", 14:13:39 replacing "user agent" with "underlying platform software", and adding an example; and for non-web platform software by replacing "web content" with "platform software". 14:14:39 q+ 14:14:49 ack PhilDay 14:14:49 PhilDay, you wanted to say go with consensus 14:14:56 ack bruce_bailey 14:15:01 PhilDay: Happy to go with consensus 14:15:28 bruce_bailey: Think the original writing was semantically correct ,but looked strange. So it would be good to see the fully rendered version. 14:15:52 ... example looked like it was part of the original. 14:16:03 ... Mary Jo is screen sharing the rendered version from the PR 14:16:30 DRAFT RESOLUTION: Move the example out of the note in SC 2.5.2 as demonstrated by Option 2 in PR 454. 14:16:34 +1 14:16:36 +1 14:16:40 +1 14:16:46 +1 14:16:55 +1 14:16:57 +1 14:16:58 +1 14:17:11 +1 14:17:17 RESOLUTION: Move the example out of the note in SC 2.5.2 as demonstrated by Option 2 in PR 454. 14:17:24 Bryan_Trogdon has joined #WCAG2ICT 14:17:42 TOPIC: Question 4, Issue 419 – Definition of ‘style properties’ needs different word substitution 14:18:01 Google doc: https://docs.google.com/document/d/1o6ruxbOKxAU6aWWz9Ac7P8DMi7lrIwXCy5DgvRzQZA4/edit#heading=h.spkm7vty5ouc 14:18:10 Issue: https://github.com/w3c/wcag2ict/issues/419 14:18:10 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comments-july/results#xq4 14:18:42 Survey results. 6 stated option 2 was ready to merge as is, 1 as is with edits 14:19:06 Edit was a minor editorial. e.g. via user agent, platform software, or other software interface settings, user style sheets) becomes e.g. via user agent, platform software, other software interface settings, or user style sheets) 14:19:20 Mary Jo then thought this changed the meaning - so exploring further in the Google doc 14:20:22 2 proposed changes to discuss. 14:20:38 1) getting rid of interface or not (in software interface settings). 14:20:48 2) whether to move or add an OR 14:20:50 q+ 14:20:56 ack mitch 14:21:07 mitch11: Note in WCAG does not have any OR - just has a comma 14:21:13 Rendered version (using anchor) from PR 454: https://deploy-preview-454--wcag2ict.netlify.app/#applying-sc-2-5-2-pointer-cancellation-to-non-web-documents-and-software 14:21:21 mitch11: Just follow WCAG 14:21:46 maryjom: WCAG did have the word interface. Some of the versions we discussed dropped this word 14:22:35 +1 to option 3 with additional or 14:22:58 POLL: Can we use Option 3, as edited in the Google doc? 14:23:02 +1 14:23:04 +1 14:23:04 +1 14:23:04 +1 14:23:06 +1 14:23:10 +1 14:23:16 +1 14:23:19 +1 14:23:26 User styles: Style property values that are set by the user (e.g. via [user agent, platform software, or other software interface settings], or] user style sheets) 14:23:33 q+ 14:23:42 q+ 14:23:54 s/settings]/settings 14:24:06 q- 14:24:12 q- 14:24:17 RESOLUTION: Update the definition of “user style sheets,” with the modifications as shown in Option 3 in the google doc (copied above in the minutes). 14:24:35 TOPIC: Question 7, Issue 446 – Privacy considerations 14:24:45 Issue 446 link: https://github.com/w3c/wcag2ict/issues/446 14:24:47 Google doc: https://docs.google.com/document/d/1YfD_Rxeg72vLZXBuV05BDvlKFCjwy5KZEOeeJSTtfLY/edit#heading=h.313sck9d6uae 14:24:51 RRSagent, draft minutes 14:24:52 I have made the request to generate https://www.w3.org/2024/08/15-wcag2ict-minutes.html bruce_bailey 14:24:58 Question link: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comments-july/results#xq7 14:25:41 Survey results were mixed. 2 preferred proposal 2 as is, 3 preferred proposals 2 & 3 as is, 1 preferred proposals 2 & 3 with edits 14:26:14 Proposal 3 included WCAG references on privacy 14:27:35 Clean version of Proposal 2: This Working Group Note does not introduce any new privacy considerations. However, when implementing WCAG 2 success criteria in the context of non-web ICT, information about a user’s accessibility needs or preferences might be exposed; a user could be harmed by disclosure and misuse of that information. It is best 14:27:35 practice to choose implementations that reduce the potential for fingerprinting or other identification and tracking of users, and that the only data collected is data necessary to enable the accessibility features. 14:27:35 Proposal 3: Add a note to proposal 1 or 2 linking to WCAG 2.2 privacy section 14:27:35 NOTE: The WCAG 2 Privacy Considerations section also notes specific success criteria that are identified to have possible implications for privacy that could also exist for non-web ICT. 14:27:58 Bryan_Trogdon has joined #WCAG2ICT 14:28:32 Proposal 4: Gregg’s edit 14:28:32 This Working Group Note does not introduce any new privacy considerations. However, when implementing WCAG 2 success criteria in the context of non-web ICT, information about a user’s accessibility needs or preferences might be exposed; a user could be harmed by disclosure and misuse of that information. It is best practice to choose 14:28:32 implementations that reduce the potential for fingerprinting or other identification and tracking of users, and that the only data collected is data necessary to enable the accessibility features and the data should not be used for any other purpose. 14:28:34 q+ 14:28:41 ack mitch 14:29:06 mitch11: Can accept either with or without Gregg's addition. Would favour Gregg's addition, but without the use the word "should" 14:29:31 present+ Sam 14:30:11 Sam: Fine with options. Not sure about adding the last statement - it sounds like an additional requirement. 14:30:34 Sam: Better to add to WCAG if that requirement is needed - rather than only adding for non-web ICT 14:30:36 q+ 14:30:41 q+ 14:30:46 ack mitch 14:31:05 I have to drop for another meeting. Bye all! 14:31:06 ack bruce_bailey 14:31:13 mitch11: Still accept either. Disagree that privacy has the same requirements for privacy -non-web has access to more data 14:31:30 bruce_bailey: Agree we shouldn't be fixing problems in WCAG, but we can point out gaps 14:31:47 maryjom: WCAG doesn't cover privacy in requirements 14:32:10 Q+ 14:32:19 ack Mike_Pluke 14:32:49 Mike_Pluke: On the other hand - it is about applying to non-web ICT - so risk of exposing more user information that may not be available in web, so extra bit on the end could be useful 14:33:10 q 14:33:13 q+ 14:33:18 ack PhilDay 14:34:10 PhilDay: Think the extra bit is probably not needed - already implicitly covered in Proposal 2 14:34:10 q+ 14:34:14 ack mitch 14:34:25 mitch11: Like the observation that it is already implied 14:34:29 Q+ 14:34:38 ack Mike_Pluke 14:34:46 Mike_Pluke: Can accept it too 14:35:24 Now need to consider whether we also add proposal 3 (to the clean version of proposal 2) 14:35:30 POLL: Should we include Proposal 3 in the Privacy Considerations – which points to the WCAG 2.2 Privacy section? +1, 0, -1 14:36:00 0 14:36:12 +1, can accept either 14:36:16 +1 14:36:24 0 had stated to include originally but either way is fine 14:36:34 q- 14:36:36 +1 14:36:46 +1 14:37:25 Proposal 3: Add a note to proposal 1 or 2 linking to WCAG 2.2 privacy section 14:37:25 NOTE: The WCAG 2 Privacy Considerations section also notes specific success criteria that are identified to have possible implications for privacy that could also exist for non-web ICT. 14:37:32 4 +1's, 2 0's 14:37:55 RESOLUTION: Update the Privacy Considerations using Proposal 2 and Proposal 3 as-is. 14:38:30 All stated answer sufficient as is 14:38:42 TOPIC: Question 8, Issue 446 – Proposed TF answer for a comment in the issue 14:38:46 https://docs.google.com/document/d/1YfD_Rxeg72vLZXBuV05BDvlKFCjwy5KZEOeeJSTtfLY/edit#heading=h.3jxen2anaonz 14:38:51 All stated answer sufficient as is 14:38:52 Issue 397 link: https://github.com/w3c/wcag2ict/issues/397 14:39:13 DRAFT RESOLUTION: Answer issue 446 as proposed in the Google doc, substituting the agreed text changes into the answer where noted. 14:39:19 +1 14:39:20 +1 14:39:24 +1 14:39:26 +1 14:39:28 Draft answer proposal 1: comment to put in Issue 446 14:39:28 Thank you for your review of the privacy considerations. The WCAG2ICT TF has updated the Privacy considerations in the editor’s draft with the following text: 14:39:28 @@Text of proposal 2 (with potential edits approved by the TF) 14:39:28 ** If we also approve proposal 3 add the following** 14:39:30 The task force also added a reference to the WCAG 2 privacy considerations section as we thought it provided additional information that is also pertinent to non-web documents and software. The following text was added for that reference: 14:39:30 @@Text of proposal 3 (possibly with edits) 14:39:56 +1 14:40:00 +1 14:40:00 Q+ 14:40:34 https://docs.google.com/document/d/1YfD_Rxeg72vLZXBuV05BDvlKFCjwy5KZEOeeJSTtfLY/edit#heading=h.3jxen2anaonz 14:41:03 RESOLUTION: Answer issue 446 as proposed in the Google doc, substituting the agreed text changes into the answer where noted. 14:41:12 TOPIC: Question 1, Issue 397 – Key terms: “virtual keyboard” proposed rephrasing of examples 14:41:21 Issue 397 link: https://github.com/w3c/wcag2ict/issues/397 14:41:29 Question link: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-public-comments-july/results#xq1 14:41:31 Google doc: https://docs.google.com/document/d/1o6ruxbOKxAU6aWWz9Ac7P8DMi7lrIwXCy5DgvRzQZA4/edit#heading=h.c6e0rn523jst 14:42:08 Mixed results. 1 preferred option 1 as is, 1 option 3 as is, 1 option 3 with edits, 2 preferred option 4 as is 14:42:40 Proposals link in Google doc: https://docs.google.com/document/d/1o6ruxbOKxAU6aWWz9Ac7P8DMi7lrIwXCy5DgvRzQZA4/edit#heading=h.bzxhof1q3vxx 14:42:58 Considering options 1, 3, 4 14:43:15 Option 1 would ignore the issue - she asked for the order to be changed 14:44:22 Option 1: Do not change the text. It is clear enough as-is. 14:44:22 NOTE: Speech, eye-gaze, sip-and-puff, sounds, switches, and codes have all been used by virtual keyboards as input that generates "keystroke" output. 14:44:22 Clean Option 3: Example: Some ways to generate "keystroke" output include virtual keyboards that take input from various sources such as speech, eye-gaze, sip-and-puff (and other kinds of switches), sounds, morse code, and so on. 14:44:22 Clean option 4: NOTE: Some of the many ways to generate keystroke input include speech, eye-gaze, sip-and-puff (and other kinds of switches), sounds, morse code, and, of course, keyboards (small, large, physical, on-screen, floating in the air, etc.) 14:44:48 Option 5a: Proposal from Olivia - reword Option 3, put list in alphabetical order 14:44:48 Example: Some common ways to generate "keystroke" output for virtual keyboards include eye-gaze, morse code, sounds, speech, and switches (e.g., sip-and-puff). 14:44:48 Option 5b: Should be input from keyboards -- since that is what the SC is about. So 5a becomes 5b 14:44:48 Example: Some common ways to generate "keystroke" input from virtual keyboards include eye-gaze, morse code, sounds, speech, and switches (e.g., sip-and-puff). 14:45:24 Q+ 14:45:30 ack bruce_bailey 14:45:46 ack Mike_Pluke 14:45:48 ack Mike_Pluke 14:46:29 Mike_Pluke: 5a and 5b. 5b is more correct as it refers to input from virtual keyboards 14:46:44 maryjom: Need to match language to definition 14:47:35 https://w3c.github.io/wcag2ict/#virtual-keyboard 14:47:49 The term virtual keyboard, as used in WCAG2ICT, has the meaning below: 14:47:49 virtual keyboard (as used in WCAG2ICT) 14:47:49 any software that acts as a keyboard and generates output that is treated by other software as keystrokes from a keyboard 14:47:49 NOTE 14:47:50 Speech, eye-gaze, sip-and-puff, sounds, switches, and codes have all been used by virtual keyboards as input that generates "keystroke" output. 14:48:10 Q+ 14:48:22 ack Mike_Pluke 14:48:39 Mike_Pluke: Agree. We should match the definition 14:49:01 q+ Sam 14:49:04 ack Sam 14:49:06 ack sam 14:49:20 Sam: Do we need to change from the original. Is this better than the original? 14:49:55 maryjom: It was somebody from the COGA task force who said that it read backwards. Their proposal was not usable, but we tried to make changes to address the input 14:50:00 s/input/issue 14:50:28 Sam: Think the original is easier to read than the current proposals with output & input 14:51:08 q+ 14:51:09 ... Only change would be to say EXAMPLE instead of NOTE 14:51:21 q+ 14:51:26 ack bruce_bailey 14:51:51 bruce_bailey: Agree to change the word to EXAMPLE, but think we also tend to have the word example in the text in this case 14:52:52 q+ 14:52:52 q? 14:52:57 ack mitch 14:53:24 mitch11: Agree with Sam - prefer no change, also agree with Mary Jo that these are not examples of virtual keyboard 14:53:24 ack PhilDay 14:53:31 i am okay with not making a change 14:54:12 PhilDay: Changing around with examples is possible, but it makes it more difficult to read 14:55:11 poll: Which do you prefer? 1) No change to the note, 2) Option 5a, 3) Option 5b, or something else 14:55:21 1 14:55:36 (Less confusing trying to parse system input/output chains!) 14:55:37 1 14:55:46 1 Sam 14:55:46 Sam: 1 (original)( 14:55:49 0 14:55:51 1 14:55:54 1 14:55:57 i am okay with all 14:56:03 s/)(/) 14:56:15 6 1's , 1 zero 14:56:19 q+ 14:56:32 ack PhilDay 14:57:26 PhilDay: suggest we include examples of what we tried with changing ordering - it introduced more complications - so we ended up reverting 14:57:38 ... In the response to the public comment 14:57:48 RESOLUTION: Issue 397: Make no changes to the note on "virtual keyboard" definition 14:58:20 i volunteer to write proposed response if they that would be helpful 14:58:26 Topic: Question 2 - Issue 397 - Review proposed TF answer for a comment in the issue 14:58:37 Issue: https://docs.google.com/document/d/1o6ruxbOKxAU6aWWz9Ac7P8DMi7lrIwXCy5DgvRzQZA4/edit#heading=h.u60z11j99ywv 14:58:45 s/Issue/Google doc 14:59:17 q 14:59:19 q+ 15:00:26 Thanks to bruce_bailey for volunteering to draft this response - and will include some of the ways that we tried in restating it, but these ended up introducing more complications 15:01:19 DRAFT RESOLUTION: Answer the issue stating the "virtual keyboard" definition's Note will not be changed and that we tried several iterations to attempt to reword. Provide some examples of what we tried in the anser. 15:01:31 +1 15:01:33 +1 15:01:39 +1 15:01:46 answer not anser * 15:01:57 s/anser/answer/ 15:02:18 +1 15:02:19 +1 15:02:27 +1 15:02:36 Unanimous +1 15:02:49 RESOLUTION: Answer the issue stating the "virtual keyboard" definition's Note will not be changed and that we tried several iterations to attempt to reword. Provide some examples of what we tried in the answer. 15:03:17 q+ 15:03:19 Quick question: do we want to restart a Friday session to get other issues picked up and started? 15:03:23 I'm available as needed. 15:03:30 Would be 1 hour earlier than the Thursday meeting 15:03:33 q+ 15:03:41 q+ 15:03:44 q+ 15:03:44 ack PhilDay 15:03:46 Need to drop. 15:03:52 q- 15:03:53 ack Chuck 15:04:11 Chuck: Not able to attend on Fridays, but happy for others to go ahead. 15:04:15 ack mitch 15:04:28 I must depart. 15:04:40 mitch11: We should choose the ones that actually need work - need to choose carefully 15:05:02 maryjom: Agree with mitch - focus on substantive changes with no proposals currently available 15:06:07 +1 for tomorrow 15:06:12 +1 tomorrow 15:06:16 i am available 15:06:21 +1 for tomorrow 15:06:43 rrsagent, draft minutes 15:06:44 I have made the request to generate https://www.w3.org/2024/08/15-wcag2ict-minutes.html PhilDay 15:07:22 regrets: Daniel Montalvo 15:07:32 zakim, bye 15:07:32 leaving. As of this point the attendees have been PhilDay, ChrisLoiselle, Mike_Pluke, olivia, Devanshu, Bryan_Trogdon, bruce_bailey, FernandaBonnin, mitch, Sam 15:07:32 Zakim has left #wcag2ict 15:07:34 zakim, end meeting 15:07:41 rrsagent, bye 15:07:41 I see no action items