13:46:00 RRSAgent has joined #wcag2ict 13:46:04 logging to https://www.w3.org/2023/04/27-wcag2ict-irc 13:46:04 RRSAgent, make logs Public 13:46:35 please title this meeting ("meeting: ..."), maryjom 13:46:36 zakim, clear agenda 13:46:36 agenda cleared 13:46:36 chair: Mary Jo Mueller 13:46:36 meeting: WCAG2ICT Task Force Teleconference 13:46:36 zakim, please time speakers at 2 minutes 13:46:36 ok, maryjom 13:46:45 Agenda+ Announcements 13:46:51 Agenda+ Project standup and planning 13:46:57 Agenda+ Survey results and discussion on SC 2.5.1 Pointer Gestures 13:47:06 Agenda+ Do we need the Understanding Intent included in the document? 13:47:12 Agenda+ Continue last week’s discussion on 1.4.10 Reflow 13:47:19 regrets: Shawn Thompson 13:47:26 agenda? 13:57:31 PhilDay has joined #wcag2ict 13:57:40 present+ 13:58:34 mitch11 has joined #wcag2ict 13:59:17 Mike_Pluke has joined #wcag2ict 13:59:30 GreggVan has joined #WCAG2ICT 13:59:33 present+ 13:59:41 ThorstenKatzmann has joined #wcag2ict 14:00:59 present+ 14:01:05 bruce_bailey has joined #wcag2ict 14:01:27 present+ 14:01:36 present+ 14:01:55 scribe: ChrisLoiselle 14:02:01 present+ 14:02:01 shadi has joined #wcag2ict 14:02:05 Chuck has joined #wcag2ict 14:02:09 scribe+ PhilDay 14:02:09 present+ 14:02:16 present+ 14:02:28 zakim, take up next 14:02:28 agendum 1 -- Announcements -- taken up [from maryjom] 14:02:38 present+ 14:02:44 Devanshu has joined #wcag2ict 14:02:58 present+ 14:03:03 q+ 14:03:04 MaryJo: Editors working to clean up links. Limited to definitions sections. Bruce has volunteered to help getting those addressed. 14:03:06 q? 14:03:19 present+ 14:03:33 sam has joined #wcag2ict 14:03:36 FernandaBonnin has joined #WCAG2ICT 14:03:40 ... I want to give a gentle reminder , please q plus , we will try not to jump queue . 14:03:40 q? 14:03:54 BryanTrogdon has joined #wcag2ict 14:04:00 ack bruce_bailey 14:04:06 present+ Daniel 14:04:16 Bruce: Thanks Phil for putting together the list. I want to make sure I'm doing the edits in the right place. I'll follow up with you. 14:04:25 present+ 14:04:42 If we want to turn in to a checklist to go bottom to top and top to bottom and meet half way, happy to do that. 14:05:07 yes, I variety of difficulty levels to fix ! 14:05:20 present+ 14:05:25 MaryJo: I will review with Daniel and Michael C. to discuss other edits. Have to point to WCAG document and a reference anchor vs. full URL. Our document doesn't have that section. 14:05:29 agenda? 14:05:46 MaryJo: Any other announcements? 14:05:49 Phil's bug list: https://github.com/w3c/wcag2ict/issues/147#issuecomment-1523475592 14:06:03 Zakim, take up next 14:06:03 agendum 2 -- Project standup and planning -- taken up [from maryjom] 14:06:08 q? 14:06:51 present+ 14:07:19 MaryJo: Project standup status. Share's screen. We are working on SCs. 2 are in progress, issue 84 and 22 on tracker. Would like to have discussion on understanding if we can today. 14:08:45 To do, has 23 items. On issue 44, closed functionality has file added. It is there to break down analysis and is a spreadsheet . If you want to copy and then send me your copy we can break down the work that way. 14:09:13 We met on issue 45 update section background on text , command line, etc. We also have other items , no owner yet. Other issues are starting to get taken up for WCAG 2.2 work. 14:09:15 q? 14:09:37 MaryJo: Please feel free to take up work on to do column in tracker. 14:09:51 zakim, take up next 14:09:51 agendum 3 -- Survey results and discussion on SC 2.5.1 Pointer Gestures -- taken up [from maryjom] 14:10:33 MaryJo: I think we are in good shape on ideas for notes and guidance. 14:10:39 https://github.com/w3c/wcag2ict/issues/143 14:10:52 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-pointer-gestures/results 14:10:52 Proposal is in issue 143, link above. 14:11:23 survey results, there are 9 responses. 14:11:33 Bruce and Sam stated to accept as is, but we can talk to you after we go through the comments. 14:11:34 q? 14:11:35 i have not revisited since last week 14:11:58 MaryJo: There were also comments from Patrick and Detlev. Path and drag movements discussion. 14:12:19 Detlev opened a WCAG issue on the topic of path gesture vs. drag , vs. non web tech . 14:13:08 MaryJo: On survey itself, Gregg added comments. Gregg's comments around documentation , reads through his comments. Gregg also gave comment on Patrick and Detlev's comments. 14:13:10 q? 14:13:34 MaryJo: To Gregg, follow Detlev's issue to follow up on his comments within that thread. 14:13:35 q? 14:14:06 q+ 14:15:19 Gregg: I don't understand the reason for either one of the two comments re: applicability of the criteria. Talks to captioning only if you include audio and vide example. Talks to why apply exists. If I'm missing something , they can clarify. On second comment, path dependent vs. not, already covered by other SCs. Adding things in that aren't required is the main conversation around logic of not having them in there. 14:15:20 q? 14:15:46 MaryJo: I don't think WCAG2ICT will follow through on Detlev's issue. 14:16:02 That is for AGWG for issue tracking and resolving his comments. 14:16:06 q? 14:17:20 MaryJo: As far as other note, on content , the reason why we wrote the limitation is that we used similar phrasing on another SC. Non web documents don't typically handle gestures. Documents don't typically have that. Gesture based actions in a document are not usually present. Operating user agent yes, but not on a document. That is why it was phrased the way it was. 14:17:21 q? 14:17:39 MaryJo: Why have more SCs that a document author has to look at when it wouldn't apply. 14:17:39 q? 14:17:42 ack sam 14:18:14 q+ 14:18:27 Sam: I think it is helpful WCAG2ICT that it would be a clarifying , i.e. keep as is. Notes for clarifying for guidance is a good thing. 14:18:34 q? 14:18:37 ack GreggVan 14:18:42 application and doing so appropriately is important. 14:18:43 q+ 14:18:52 +1 to Sam's comment that note is helpful given WCAG2ICT audience 14:19:29 Gregg: I feel we are making it complicated and it doesn't need to be. If people are making dynamic documents , AR/VR , they may be interactive . 14:20:24 Gregg: Goal is does this apply. Adding a bunch of notes on it is overcomplicating. If you don't have to do it, you don't have to do it. How often it appears or where it appears. If it applies it applies , if it doesn't, it doesn't. 14:20:59 q? 14:21:12 ack mitch 14:21:40 Mitch: I really like the points what Sam and Gregg are raising. I think we should move on to the notes proposed on the edit. 14:21:41 q? 14:22:04 https://github.com/w3c/wcag2ict/issues/143#issuecomment-1515405576 14:22:12 MaryJo: I suggested we edit the notes similar to what we already put in re: pointer cancelation. 14:22:16 q? 14:22:56 MaryJo: Phil liked my comments. Mitch also liked my comments and added in additional comments for non web documents and non web software. We will revisit. 14:23:31 Mike P. liked my edits, same with Thorsten. Loic liked the proposal, he liked edit may by Mitch. 14:23:33 q? 14:23:58 MaryJo: Seems there is support to split non web document and non web software. 14:24:08 q+ 14:24:08 Opens to Bruce and Sam on concern on splitting? 14:24:10 q? 14:24:12 no 14:24:20 ack mitch 14:24:21 Sam: Says no per ask. 14:24:23 q? 14:24:27 +1 to split for this SC 14:24:30 Mitch: Were it makes it simpler. 14:24:40 q? 14:25:14 + to split (this is the reality in EN 301 549) 14:25:29 MaryJo: References pointer gestures note 14:25:42 first note: This requirement applies to [content] that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology). 14:25:47 q+ 14:25:57 q? 14:26:16 Bruce: This version that you are showcasing is that edited to showcase other comments? 14:26:29 ack bruce_bailey 14:26:32 MaryJo: I was going through the comments first. 14:26:34 q+ 14:26:40 q+ 14:26:47 +1 bruce 14:26:47 ack mitch 14:26:48 Bruce: I don't think there was much controversy on edits. 14:27:16 Mitch: I think on first note, there was no different version. I think on the second note, there are different versions that we need to talk through. 14:27:17 q? 14:27:26 ack GreggVan 14:27:31 Proposal 1 is: Applicability of this Success Criterion would be limited to document types where a document author can add content that interprets pointer actions and control which events are used for executing functionality. For example, prototyping tools used to design software. 14:27:36 MaryJo: I'm going to copy and paste proposals in IRC 14:27:49 Proposal 2: Multipoint and path-based gestures are less common in documents. An example where a document author could add such gestures is an interactive prototype document created in a software design tool. 14:27:50 Gregg: Was going to recommend placing them in one place for review. 14:27:52 q? 14:28:12 MaryJo : This is for non web documents. 14:28:29 Proposal 3: No note on applicability. 14:28:30 Proposal 3 is for no notes 14:28:39 q+ 14:28:49 MaryJo: Poll is which proposal you prefer ? 14:28:51 q? 14:28:53 Poll: Which proposal do you prefer? Proposal 1, 2 or 3? 14:29:18 Gregg: should you get in queue if you've raised a question about the topic? 14:29:22 ack GreggVan 14:29:53 Gregg: When you are talking about the note, we are talking about note 2? 14:29:54 2 14:29:59 MaryJo: Yes. 14:30:01 q? 14:30:05 Scribe change? 14:30:07 q+ to ask if I understood correctly, that we need a scribe change at half past? 14:30:11 2 14:30:13 ack Ch 14:30:13 Chuck, you wanted to ask if I understood correctly, that we need a scribe change at half past? 14:30:16 1 14:30:21 2 14:30:28 scribe+ PhilDay 14:30:34 thanks, Phil! 14:30:37 2 14:30:53 1, closely followed by 2 14:30:54 not 3, but neautral to 1 or 2 14:31:10 1 14:31:15 Chuck: was in queue to prompt scribe change 14:31:19 q? 14:31:33 2 14:31:43 3 or 2 14:31:48 maryjom: 5 for proposal 2, 3 for proposal 1. 2 is more acceptable 14:31:59 maryjom: Does anyone have heartburn going with 2? 14:32:34 maryjom: No response, so nobody is strongly against going with 2. Consensus, we will go with proposal 2w 14:32:50 ... proposal 2, not 2w! 14:33:14 q+ 14:33:20 maryjom: Suggest we also use similar language in SC 2.5.2, pointer cancellation. 14:33:27 q? 14:33:28 maryjom: Editors will need to handle this change 14:33:30 +1 that notes should be as close as possible 14:33:42 q? 14:33:43 q- 14:34:07 Zakim, next item 14:34:07 agendum 4 -- Do we need the Understanding Intent included in the document? -- taken up [from maryjom] 14:34:17 zakim, previous item 14:34:17 I don't understand 'previous item', PhilDay 14:34:26 zakim, take up item 3 14:34:26 agendum 3 -- Survey results and discussion on SC 2.5.1 Pointer Gestures -- taken up [from maryjom] 14:34:59 maryjom: Moving to non-web software part of this topic. 4 proposals to be considered 14:35:22 Proposal 1: SC 2.5.2 Pointer Cancellation NOTE This requirement applies to [non-web software] that interprets pointer actions (i.e. this does not apply to actions that are required to operate assistive technology). NOTE Non-web software applications are not responsible for pointer actions required to operate the underlying user agent or platform software. 14:35:43 Proposal 2: This requirement applies to [non-web software] that interprets pointer actions (i.e. this does not apply to actions that are required to operate [underlying platform software] or assistive technology). 14:36:03 Proposal 3: This requirement applies to [non-web software] that interprets pointer actions (i.e. this does not apply to actions that are required to operate platform software or assistive technology). 14:36:55 Proposal 4: Something else 14:36:55 Original WCAG note: o For reference, the original WCAG note is: This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology). 14:37:19 q+ 14:37:24 q+ 14:37:31 q+ 14:37:34 ack mitch 14:37:35 ack mitch 14:37:54 q- 14:38:05 mitch11: Only difference between 2 and 3 is platform software vs underlying platform software 14:38:06 ack bruce_bailey 14:38:17 bruce_bailey: Same question - minor difference between the 2 14:38:18 ack GreggVan 14:38:38 q+ 14:38:48 GreggVan: Correct is underlying platform software - as otherwise any platform software does not apply 14:39:06 q? 14:39:11 ack maryjom 14:39:22 +1 to Gregg's point 14:39:26 q+ 14:39:35 ack GreggVan 14:39:36 maryjom: Question - is there ever a user agent or underlying software? 14:40:18 GreggVan: The underlying software is the user agent - all the stuff that does the presentation to the user. Most people when they hear user agent think of browsers or technology, so underlying platform software is easier to understand 14:40:47 POLL: Which proposal for non-web software do you prefer: 1) 2 notes 2) Combined into one note, or 3) The edited combined note 4) something else. 14:40:49 2 14:40:55 2 14:40:57 2 14:41:03 2 14:41:08 2 14:41:08 2 14:41:26 3 14:41:27 q+ to suggest slight edit 14:41:31 2 or 3 14:42:20 BryanTrogdon: Curious if underlying software is easy to understand for non-technical user 14:42:36 q+ 14:42:37 ... underlying platform software 14:42:37 q+ 14:42:55 ack GreggVan 14:42:55 GreggVan, you wanted to suggest slight edit 14:43:05 2 or 3 also 14:43:08 q+ to suggest This requirement applies to [non-web software] that interprets pointer actions (i.e. this does not apply to actions that are required to operate ANY [underlying platform software] or assistive technology). 14:43:16 ack mitch 14:43:42 ack Mike_Pluke 14:43:44 mitch11: I have been confused in the past by that term. Underlying was not defined in Section 508 and so puzzled over it the first time I saw it. Maybe we should define it here 14:44:13 Mike_Pluke: Surely it is the common English usage - something sits on top of it. Shouldn't need any special definition 14:44:17 ack gregg 14:44:17 GreggVan, you wanted to suggest This requirement applies to [non-web software] that interprets pointer actions (i.e. this does not apply to actions that are required to 14:44:20 ... operate ANY [underlying platform software] or assistive technology). 14:44:50 GreggVan: Need the underlying otherwise it does not apply to any platform software like an operating system. 14:45:08 GreggVan: Also suggest we put the word ANY in the context 14:45:39 maryjom: Does anyone have any issues with that latest edit from GreggVan? 14:45:43 q+ to say i liked the MaryJo version which was just a word substitution ? 14:45:50 ack bruce_bailey 14:45:51 bruce_bailey, you wanted to say i liked the MaryJo version which was just a word substitution ? 14:46:12 bruce_bailey: liked Mary Jo's version which was the word substitution 14:46:15 ShawnT has joined #wcag2ict 14:46:30 q+ 14:46:49 maryjom: The one I had suggested was having 2 separate notes 14:47:21 bruce_bailey: That's where I got lost - missed that Mary Jo was talking about 2 notes instead of a combined version as per Mitch or Gregg's edits 14:47:33 q+ 14:47:55 bruce_bailey: Also like this combined version 14:47:55 q- 14:47:57 q- 14:48:03 q+ 14:48:11 he took himself out of queue 14:48:11 ack FernandaBonnin 14:48:25 FernandaBonnin: Do we need the word ANY? It was not required in original WCAG 14:49:02 q+ 14:49:19 maryjom: Don't think it hurts to add any 14:49:22 ack GreggVan 14:49:47 GreggVan: Agrees - in web you don't worry about the full software stack. But can live with or without the addition of ANY 14:49:52 q- 14:49:55 I have to leave now to join another meeting. 14:49:56 q+ 14:50:24 q+ to ask why no longer word substituion ? 14:50:28 mitch11: Believe proposal 2 is word substition 14:50:31 DRAFT RESOLUTION: Incorporate 2.5.1 into the draft with Proposal 2 for non-web documents and Proposal 2 for non-web software, as amended (adding "any") in the meeting. 14:50:40 ack Mitch 14:50:49 ack bruce_bailey 14:50:49 bruce_bailey, you wanted to ask why no longer word substituion ? 14:50:50 q+ 14:50:59 ack GreggVan 14:51:02 bruce_bailey: Also thinks it is word substitution 14:51:14 q- 14:51:19 GreggVan: To close this out, remove the word ANY and revert to proposal 2 14:51:26 DRAFT RESOLUTION: Incorporate 2.5.1 into the draft with Proposal 2 for non-web documents and Proposal 2 for non-web software. 14:51:38 +1 14:51:39 +1 14:51:41 +1 14:51:41 +1 14:51:43 +1 14:51:43 +1 14:51:45 +1 14:51:52 +1 14:51:53 +1 14:51:26 RESOLUTION: Incorporate 2.5.1 into the draft with Proposal 2 for non-web documents and Proposal 2 for non-web software. 14:52:20 zakim, next item 14:52:20 agendum 4 -- Do we need the Understanding Intent included in the document? -- taken up [from maryjom] 14:52:46 maryjom: Do we need the Understanding Intent in the document? It is not currently added 14:52:47 q+ 14:53:05 http://www.w3.org/TR/2013/NOTE-UNDERSTANDING-WCAG20-20130905/text-equiv-all.html#text-equiv-all-intent-head 14:53:11 ack GreggVan 14:53:26 https://wcag2ict.netlify.app/#guidance-when-applying-success-criterion-1-1-1-to-non-web-documents-and-software 14:53:51 GreggVan: Think you should include them. Firstly, we write something and then it doesn't make sense if you look at the original. 14:54:24 ... Also we should remember that anyone who has difficulty will read our document - so ours should have the understanding as well. Finally we are adding to the doc - so we should include like others do 14:55:31 RRSagent, draft minutes 14:55:32 I have made the request to generate https://www.w3.org/2023/04/27-wcag2ict-minutes.html bruce_bailey 14:55:40 maryjom: Just curious - understand that we should look at the intent while writing SCs, so everything aligns. 14:55:46 q+ 14:55:53 ack PhilDay 14:56:13 Phil: The formatting issue , it is getting more difficult to understand the notes formatting. 14:57:01 Q+ to SAY somewhat confusing to have understanding but benefit far outweighs con and it is important to look at them together 14:57:27 ack GreggVan 14:57:27 GreggVan, you wanted to SAY somewhat confusing to have understanding but benefit far outweighs con and it is important to look at them together 14:57:28 maryjom: This will just be a task on Michael Cooper to fix the includes/formatting issues 14:57:55 q+ to ask who note that "underlying" in 508 is not as clear as it might be 14:57:58 GreggVan: It is somewhat confusing, but benefit of seeing them in context outweigh the problems 14:57:59 ack bruce_bailey 14:57:59 bruce_bailey, you wanted to ask who note that "underlying" in 508 is not as clear as it might be 14:58:30 bruce_bailey: wanted to follow up on underlying not being defined. Will follow up with mitch offline 14:59:09 maryjom: When thinking about the intent, there are a couple of places where word substitution contradicts. 14:59:26 ... e.g. section 6 (task force makes no substitutions for this text) 14:59:43 q+ 14:59:44 ... so we should remove the word substitution suggestions for intent section as this is beyond our normal scope 14:59:45 q- 14:59:54 please keep open for next week! 15:00:18 GreggVan: We don't change the understanding document - but we can make suggestions to them to make improvements. 15:00:39 maryjom: There are currently 2 places where we have done that, so we need to remove these. Pull request to come for next week. 15:00:56 rrsagent, make minutes 15:00:57 I have made the request to generate https://www.w3.org/2023/04/27-wcag2ict-minutes.html dmontalvo 15:01:03 maryjom: Thanks. Next week we will pick up reflow which is the last WCAG 2.1 issue. 15:01:03 Great job by all 15:01:10 ... make sure you look at all the proposed changes 15:01:42 zakim, bye 15:01:42 leaving. As of this point the attendees have been PhilDay, Mike_Pluke, ThorstenKatzmann, maryjom, mitch, ChrisLoiselle, shadi, Chuck, bruce_bailey, Devanshu, GreggVan, Daniel, 15:01:42 Zakim has left #wcag2ict 15:01:45 ... FernandaBonnin, sam, BryanTrogdon 15:01:58 rrsagent, make minutes 15:01:59 I have made the request to generate https://www.w3.org/2023/04/27-wcag2ict-minutes.html dmontalvo 15:02:50 zakim, end meeting