13:49:55 RRSAgent has joined #wcag2ict 13:49:59 logging to https://www.w3.org/2023/05/04-wcag2ict-irc 13:49:59 RRSAgent, make logs Public 13:50:30 please title this meeting ("meeting: ..."), maryjom 13:50:30 zakim, clear agenda 13:50:30 agenda cleared 13:50:30 chair: Mary Jo Mueller 13:50:30 meeting: WCAG2ICT Task Force Teleconference 13:50:30 Zakim, please time speakers at 2 minutes 13:50:30 ok, maryjom 13:50:30 Agenda+ Announcements 13:50:36 Agenda+ Project standup and planning 13:50:51 Agenda+ Approve Pull request 152 to remove word substitution suggestions for the WCAG Intent sections 13:51:00 Agenda+ Approve adjustments to 2.5.2 Pointer Cancellation language to be consistent with 2.5.1 Pointer Gestures 13:51:08 Agenda+ Continue the 20 April discussion on 1.4.10 Reflow 13:57:49 PhilDay has joined #wcag2ict 13:58:24 olivia-hs has joined #wcag2ict 13:58:54 present+ 14:00:50 bruce_bailey has joined #wcag2ict 14:01:00 present+ 14:01:13 present+ 14:01:21 present+ 14:02:47 present+ 14:02:53 scribe+ olivia-hs 14:02:59 Devanshu has joined #wcag2ict 14:02:59 present+ 14:03:10 present+ 14:03:12 mitch11 has joined #wcag2ict 14:03:18 present+ 14:03:38 zakim, next item 14:03:38 agendum 1 -- Announcements -- taken up [from maryjom] 14:03:45 FernandaBonnin has joined #wcag2ict 14:03:46 shadi has joined #wcag2ict 14:03:50 present+ 14:03:57 BryanTrogdon has joined #wcag2ict 14:04:41 q+ 14:05:00 maryjom: 2.5.1 incorporated into editors draft. Have not incorporated intent yet. One issue with PhilDay 's list of broken links- get with Michael Cooper to fix 14:05:06 ack bruce_bailey 14:05:34 bruce_bailey: Would like orientation - set up outside of meeting 14:05:45 zakim, next item 14:05:45 agendum 2 -- Project standup and planning -- taken up [from maryjom] 14:06:16 present+ 14:07:10 maryjom: A lot we are reviewing. One is word substitutions. Another is to adjust pointer cancelation language - proposal PR created 14:07:49 maryjom: Holding out on "in progress" 14:08:26 q+ 14:08:38 https://github.com/w3c/wcag2ict/issues/44 14:08:45 maryjom: "Todo" - tomorrow group meeting on text command line. Closed functionality analysis spreadsheet added (link above) 14:08:46 ack PhilDay 14:09:09 philday: Should each person individually populate? 14:09:37 ThorstenKatzmann has joined #wcag2ict 14:09:41 maryjom: Each person does a quick analysis - see what each person thinks. 14:10:07 q+ 14:10:15 maryjom: Approach best for discussion - everyone on that issue should look at 14:10:15 present+ 14:10:16 ack mitch 14:11:02 mitch11: Questions: spreadsheet attached in Github instead of cloud hosting. Can we do both ways to allow collaboration? 14:11:02 Sam has joined #wcag2ict 14:11:12 present+ 14:11:28 q+ 14:11:43 ack bruce_bailey 14:11:45 maryjom: Start this way for the "analysis" stage 14:12:08 bruce_bailey: Nice to add +1 to columns 14:12:26 maryjom: I'll create google sheet 14:13:16 maryjom: People can start taking open issues 14:14:40 maryjom: comment in issue if ready to review 14:15:24 q+ 14:15:34 ack sam 14:15:42 maryjom: Few more SCs that use CSS pixels. We may need for someone to make sure definition works across all with Pixels. 14:16:05 Sam: Created a list. 14:16:34 q+ 14:16:45 maryjom: when we think we have arrived at a good definition we want someone to look at to make sure it works consistently 14:16:59 ack mitch 14:17:03 Sam: Focus appearance and target size are the two 14:17:37 Mitch11: Question on timing: since it is a criteria for 2.0 does it come up in later efforts? 14:17:56 q+ to ask if we memorialized our direction with CSS pixels ? 14:18:12 maryjom: Timing no significant. Good to get things off books. 14:18:23 SC with CSS Pixcel [2.4.11 Focus Appearance (AA)](https://www.w3.org/TR/WCAG22/#focus-appearance), 14:18:23 [2.5.8 Target Size (Minimum) (AA)](https://www.w3.org/TR/WCAG22/#focus-appearance) 14:18:59 good catch on flash 14:19:11 mitch11: Responding to issues involving pixel size. If pixel size depends on viewing angle - Level A and AAA flash criteria. Only refers to viewing angle. 14:19:23 mitch11: see as related 14:19:27 q? 14:19:38 greggvan: it is related 14:19:45 ack bruce_bailey 14:19:45 bruce_bailey, you wanted to ask if we memorialized our direction with CSS pixels ? 14:20:18 bruce_bailey: memorialized our direction with CSS pixels? 14:21:01 maryjom: conclusion last time: that was the way to go. Will get into later in this meeting. We did make a decision. 14:22:37 q+ 14:22:44 https://www.w3.org/WAI/WCAG22/Understanding/three-flashes-or-below-threshold has some of the discussion on viewing angles 14:22:54 ack Sam 14:22:54 greggvan: All language is really old and non-normative (note on definition). So it can be changed. More work is going to need to be done. Different monitor sizes could impact safety 14:23:41 Sam: device independent pixels discussion could be have now. Larger screen/ smaller screen. 14:23:45 zakim, next item 14:23:46 agendum 3 -- Approve Pull request 152 to remove word substitution suggestions for the WCAG Intent sections -- taken up [from maryjom] 14:24:30 https://github.com/w3c/wcag2ict/pull/152/files 14:24:39 https://github.com/w3c/wcag2ict/issues/104 14:24:50 q- 14:25:14 maryjom: Last week - a couple of spots with word substitutions. This request is to remove it. 14:25:56 +1 14:25:56 maryjom: want to get pull request approved by group 14:26:03 Poll: Do you agree with the proposed changes to 2.5.2 Pointer Cancellation? 14:26:12 +1 14:26:39 Poll: Do you agree with the proposed changes in PR 152 to remove word replacements for Intent. 14:26:50 +1 14:26:52 +1 14:26:52 +1 14:26:53 +1 14:26:53 +1 14:26:54 +1 14:26:54 +1 14:26:55 +1 14:26:58 +1 14:27:02 q+ 14:27:05 maryjom: Going to incorporate 14:27:17 ack bruce_bailey 14:27:43 bruce_bailey: Worried that when this is rendered it will look circular. The replacements in 2.2, not ICT 14:28:26 bruce_bailey: It seems to be this is a paragraph to appear in ICT, not clear in 2.2 14:28:37 q+ 14:28:57 maryjom: have other descriptions elsewhere about substitutions 14:29:52 maryjom: this is in the definitions and more obvious language. 14:29:55 ack GreggVan 14:30:54 greggvan: It didn't get caught the first time. Try to describe what we did, not telling them what to do. 14:31:38 yes, change "should be" with "has been" -- because context is wcag2ict doc and NOT wcag 2.2 doc 14:32:05 greggvan: Original language tried to echo back Access Board language. We should double check the intent. 14:32:07 Should it read, "Within WCAG2ICT wherever “content” or “web content” appears in a success criterion it has been replaced with “content” using the definition above. 14:32:23 +q 14:32:36 ack mitch 14:32:50 Should it read, "Within WCAG2ICT wherever “content” or “web content” appears in a success criterion it is replaced with “content” using the definition above. 14:32:59 +1 to present tense 14:32:59 mitch11: Yes, that improves it with "is" rather than "was" 14:33:09 +1 14:33:14 +1 14:33:15 +1 14:33:17 +1 14:33:17 +1 14:33:19 +1 14:33:19 +1 14:33:31 maryjom: will be incorporated as edited 14:33:46 zakim, next item 14:33:47 agendum 4 -- Approve adjustments to 2.5.2 Pointer Cancellation language to be consistent with 2.5.1 Pointer Gestures -- taken up [from maryjom] 14:34:00 https://github.com/w3c/wcag2ict/issues/151 14:34:23 Comment with proposed changes: https://github.com/w3c/wcag2ict/issues/151#issuecomment-1529916562 14:34:55 maryjom: Comment discussed bringing pointer cancelation language in alignment with pointer gestures 14:35:26 maryjom: In comment, modification shows the spilt 14:35:33 This applies directly as written, and as described in Intent from Understanding Success Criterion 2.5.2 (also provided below), making changes to the notes for non-web documents by replacing “web content” with "content" and for non-web software by replacing "web content" with "non-web software" and "user agent" with "underlying platform software". 14:35:36 q- 14:36:11 Content that interprets pointer actions and controls which events are used for executing functionality is less common in documents. An example where a document author could add such functionality is an interactive prototype document created in a software design tool. 14:36:23 maryjom: For non-web made language similar 14:36:24 Above note is for non-web documents 14:36:58 (for non-web software) 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 the [underlying platform software] or assistive technology). 14:37:17 q+ 14:37:22 maryjom: Any concerns? 14:37:26 ack mitch 14:37:45 mitch11: Did we remove the second note from non-web documents? 14:37:58 maryjom: no, these are just the changes 14:38:55 greggvan: comma needed after "actions" 14:39:01 Content that interprets pointer actions, and controls which events are used for executing functionality is less common in documents. 14:39:19 Content that interprets pointer actions, and controls which events are used for executing functionality, is less common in documents. 14:39:19 q+ 14:39:26 ack mitch 14:39:48 mitch11: Unclear how it will land 14:39:50 thanks for the commas ! 14:41:14 maryjom: For pointer cancelation non-web documents first note will remain, second note will remain, third one was edited (changed applicability language) 14:42:00 maryjom: for non-web software the first note remains, the last two combine similar to one we settled on last week 14:42:40 Poll: Do you agree with the proposed changes to 2.5.2 Pointer Cancellation? 14:42:44 +1 14:42:48 +1 14:42:52 +1 14:42:55 +1 14:43:01 +1 14:43:13 +1 14:43:46 maryjom: Will incorporate as discussed with comma changes 14:43:54 zakim, next item 14:43:54 agendum 5 -- Continue the 20 April discussion on 1.4.10 Reflow -- taken up [from maryjom] 14:44:47 maryjom: Stated last week talking about edits for non-web docs 14:45:01 maryjom: Did not settle 14:45:09 https://github.com/w3c/wcag2ict/issues/98#issuecomment-1512900536 14:45:24 maryjom: Want to talk about comment from mitch11 and proposed changes 14:46:42 mitch11: Pointed out "user agent" isn't quite right. Proposed rephrasing. 14:47:04 q+ 14:47:05 maryjom: any concerns with note? 14:47:10 q+ 14:47:20 ack mitch 14:47:57 q+ 14:48:02 ack bruce_bailey 14:48:06 mitch11: After I wrote, I have my doubts. Don't know what meant by "document type." Seems true that an entire document format couldn't reflow. I think the edit is good. 14:49:01 bruce_bailey: giving exception to platform instead of author controlled content. 14:49:05 q? 14:49:09 ack sam 14:50:02 sam: Tiff would be document type that can't do the reflow 14:50:08 q+ 14:50:15 maryjom: Does there need to be an example? 14:50:16 ack mitch11 14:50:22 ack mitch 14:50:56 mitch11: Example just for this conversation 14:51:17 q+ 14:51:21 ack bruce_bailey 14:51:40 bruce_bailey: A few places where we talk about "file types" 14:51:55 q+ 14:52:01 ack PhilDay 14:52:03 maryjom: Do we need to change the language? 14:52:38 PhilDay: Could Bruce explain what he meant by "we're giving exception rather than platform"? 14:53:20 q+ 14:53:28 ack mitch 14:54:41 q+ 14:54:41 mitch11: When it says "parts of the content" - parts of page can reflow and some exceptions. With Tiff document all one part. Exceptions do not contradict for me. 14:54:41 ack bruce_bailey 14:55:47 bruce_bailey: Better approach that there is less support with documents. Not convinced exceptions map well to this success criteria. 14:56:31 +1 to MJ spoken note 14:56:48 maryjom: Note for document authors. Whatever format they are using doesn't reflow doesn't make them responsible. Should we let fly and see if we get any other feedback? 14:56:56 q+ 14:57:04 bruce_bailey: Can we drop bit about user agents? 14:57:22 q+ 14:57:31 bruce_bailey: author doesn't have control over user agent. Exception to file type. 14:57:41 ack mitch 14:57:44 maryjom: because no doc reflows on its own 14:58:50 ack sam 14:58:57 mitch11: Point in history when this was true with PDF tagging. No user agent exists that reflows it. In support of keeping exception narrow. 14:59:12 q+ 14:59:36 q+ 14:59:36 Sam: Think first note is fine 14:59:48 ack GreggVan 15:01:22 q+ 15:01:25 q+ 15:01:29 GreggVan: That approach is opposite of what WCAG stands for. Example: when PDF came out and couldn't meet guidelines, PDF went back to allow to support. You don't give exceptions. It's not accessible. 15:01:35 ack mitch 15:01:49 q- 15:02:15 mitch11: agree with Gregg. The fact is there is currently an exception and trying to find what it applies to. 15:02:33 ack sam 15:02:42 mitch11: There are open issues, better to say something or community will 15:02:48 i would rather note mention that not all formats support this SC 15:03:09 software is a different issue and reflow is a completley different topic we need to examine 15:03:26 for software 15:03:28 and a tough one 15:03:31 maryjom: Please read through 1.4.10 definition and weigh in 15:03:56 rrsagent, make minutes 15:03:58 I have made the request to generate https://www.w3.org/2023/05/04-wcag2ict-minutes.html olivia-hs 15:04:25 zakim, bye 15:04:25 leaving. As of this point the attendees have been PhilDay, ChrisLoiselle, bruce_bailey, olivia-hs, maryjom, GreggVan, Devanshu, mitch, shadi, BryanTrogdon, ThorstenKatzmann, Sam 15:04:25 Zakim has left #wcag2ict 15:04:45 q- 15:30:39 Sam has joined #wcag2ict 15:36:55 Sam has joined #wcag2ict 16:40:19 Sam has joined #wcag2ict