13:41:21 RRSAgent has joined #wcag2ict 13:41:25 logging to https://www.w3.org/2023/06/15-wcag2ict-irc 13:41:25 RRSAgent, make logs Public 13:41:26 please title this meeting ("meeting: ..."), maryjom 13:41:28 zakim, clear agenda 13:41:28 agenda cleared 13:41:33 chair: Mary Jo Mueller 13:41:39 meeting: WCAG2ICT Task Force Teleconference 13:41:46 Zakim, please time speakers at 2 minutes 13:41:46 ok, maryjom 13:41:55 Agenda+ Announcements 13:42:03 Agenda+ Project standup and planning 13:42:09 Agenda+ Survey results: 2.5.8 Target Size (Minimum) draft review 13:42:17 Agenda+ CSS pixel definition 13:54:31 Regrets: Shawn Thompson, Sam Ogami, Phil Day 13:57:03 loicmn has joined #wcag2ict 13:57:05 bruce_bailey has joined #wcag2ict 14:01:16 Mike_Pluke has joined #wcag2ict 14:02:14 present+ 14:02:38 mitch11 has joined #wcag2ict 14:02:43 present+ 14:02:52 present+ 14:02:56 present+ 14:03:08 Chuck has joined #wcag2ict 14:03:11 present+ 14:03:11 present+ 14:03:22 scribe+ loicmn 14:03:40 Zakim, next item 14:03:40 agendum 1 -- Announcements -- taken up [from maryjom] 14:03:40 Devanshu has joined #wcag2ict 14:03:58 btrogdon has joined #wcag2ict 14:04:26 FernandaBonnin has joined #WCAG2ICT 14:04:37 present+ 14:05:09 present+\ 14:05:12 maryjom: Work has started in the review of EN 301 549 for the European Accessibility Act 14:05:13 present+ 14:05:31 Mike_Pluke: Yes. But not really the first working item, but a preparatory meeting of the team 14:05:48 olivia has joined #wcag2ict 14:05:50 present+ 14:05:55 +1 to having Mike involved with both activities ! 14:06:00 present+ 14:06:04 shadi has joined #wcag2ict 14:06:11 present+ 14:07:08 maryjom: pull request for target size has been created. Will review it later. 14:07:19 present+ 14:08:09 maryjom: sub-groups meetings. Closed functionality has met yesterday (not all could attend) and prepared useful input for the TF 14:08:25 Q+ 14:08:56 q+ 14:08:59 ack Mike_Pluke 14:09:03 maryjom: text-command line group will convene tomorrow. They will be discussing the possibility of adding a list of SC criteria related to that topic. 14:09:34 Mike_Pluke: When will closed functionality be proposed? Interested due to EN update. 14:10:04 maryjom: worried that EN takes non reviews TF content. 14:10:12 +1 to Mikes concern for Closed Functionality 14:10:28 Mike_Pluke: EN group interested in see the direction of the ideas, rather than the specific content. 14:10:58 q? 14:11:07 ack bruce_bailey 14:11:14 maryjom: the discussion of the closed functionality group is creating interesting topics that migh not be notes for any specific SC 14:11:29 LauraBMiller has joined #WCAG2ICT 14:11:32 present+ 14:11:37 bruce_bailey: asking clarification of difference between closed functionality and command line 14:11:46 maryjom: they are two different groups 14:12:25 q? 14:12:27 +1 that it is a lot of work ! 14:12:38 Zakim, next item 14:12:38 agendum 2 -- Project standup and planning -- taken up [from maryjom] 14:13:18 maryjom: asks Daniel about document formatting 14:13:38 dmontalvo: no news yet 14:14:07 maryjom: there has been an email sent today 14:14:21 q+ 14:14:22 dmontalvo: is about formatting of "inserted" content. 14:15:04 maryjom: Has gone through the issues. Picture is good so far. Some issues that were not part of the original WCAG2ICT note 14:15:36 q+ 14:15:39 maryjom: These could be interesting for today meeting. 14:15:48 ack bruce_bailey 14:16:33 ack Chuck 14:16:41 bruce_bailey: suggests to follow the approach of WCAG 3 - publish what we've got making clear that some issues (closed functionality, command-line) are not finished 14:17:22 Chuck: agrees to look at these topics is we cannot work on the CSS pixel definition survey 14:18:43 maryjom: To finish WCAG 2.1 SC we need Reflow (and CSS definition) plus closed-functionality and command-line. Could we publish before these parts (CF and CL)? 14:18:52 Chuck: as the TF decides 14:19:33 zakim, take up next 14:19:33 agendum 3 -- Survey results: 2.5.8 Target Size (Minimum) draft review -- taken up [from maryjom] 14:20:09 agenda+ Issue triage discussions 14:20:09 maryjom: survey was sent late. No responses before today's meeting. Will be discussed next week 14:20:16 q+ if we should be looking for late survey on CSS pixel ? 14:20:34 ack bruce_bailey 14:21:04 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-CSS-pixels/ 14:21:39 bruce_bailey: asks about the availability of surveys and which ones we need to answer for next week 14:22:05 maryjom: the CSS pixel definition (ready and open) and Reflow (has to be prepared) 14:22:16 Zakim, next item 14:22:16 agendum 4 -- CSS pixel definition -- taken up [from maryjom] 14:22:27 shadi_ has joined #wcag2ict 14:23:02 zakim, next item 14:23:02 agendum 4 was just opened, loicmn 14:23:19 zakim, close item 4 14:23:19 agendum 4, CSS pixel definition, closed 14:23:20 I see 1 item remaining on the agenda: 14:23:20 5. Issue triage discussions [from maryjom] 14:23:23 zakim, next item 14:23:23 agendum 5 -- Issue triage discussions -- taken up [from maryjom] 14:23:51 https://github.com/w3c/wcag2ict/issues/77 14:24:04 maryjom: There are several issues. First one issue 77 14:25:13 maryjom: There has been a request to include in TF the supplements, specifically the one on cognitive and learning disabilities. 14:25:33 q+ to say AAA are in scope 14:25:37 q+ 14:25:39 maryjom: her first answer is that this is out of scope for the TF. What does the group think? 14:25:39 ack bruce_bailey 14:25:39 bruce_bailey, you wanted to say AAA are in scope 14:25:49 q+ 14:26:03 bruce_bailey: This time we will work on AAA? 14:26:15 https://www.w3.org/TR/coga-usable/ 14:26:20 maryjom: Yes. But this is a supplemental guidance (linked) 14:26:37 q? 14:26:46 ack mitch 14:27:27 https://www.w3.org/TR/WCAG22/#wcag-2-layers-of-guidance 14:27:27 mitch11: First, A and AA do have some cognitive. Question: does WCAG non-normative content refers to COGA 14:28:03 maryjom: It does in the section on "layers of guidance" 14:28:05 q+ to say i understood our work to consider Understanding 14:28:25 q? 14:28:30 ack Ch 14:28:30 ack Chuck 14:29:20 Chuck: yes, there is a reference... but not a "hard reference". It seems clearly not normative. His interpretation is that "advisory" is out of scope for TF 14:29:29 ack bruce_bailey 14:29:29 bruce_bailey, you wanted to say i understood our work to consider Understanding 14:30:10 bruce_bailey: In our work we are considering content from "understanding", but any other guidance seems out of scope 14:30:10 q+ 14:30:42 q+ could they point to ours instead? 14:30:46 q+ 14:31:07 ack mitch 14:31:09 maryjom: We are just taking input from "intent" to make sure the word substitutions meet the original intent. 14:31:14 i agree that word substitutions might not work throughout all of Understanding 14:31:47 mitch11: confused about us focusing on "normative parts of WCAG" in a non-normative document? 14:32:08 Chuck: yes. Our scope is to deal with normative content of WCAG to create our note. 14:33:14 mitch11: suggest it might fit in introductory text or other sections (as a pointer to additional guidance). 14:33:15 ack ChrisLoiselle 14:33:49 ChrisLoiselle: is there anything prohibiting us to take content from COGA in our results? 14:33:58 q+ 14:34:13 q+ 14:34:24 ack Chuck 14:34:27 more if COGA wanted to point to WCAG2ICT, they could if they wanted to, per their context 14:34:47 https://www.w3.org/TR/coga-usable/ 14:35:00 maryjom: not sure about the content inside COGA 14:35:05 q+ that reply to Lisa could mention we have every expectation of address AAA sc with the present activity. 14:35:37 dmontalvo: Not sure about the possibility of adding content from COGA (bad sound quality) 14:35:59 If COGA wanted to add this to https://www.w3.org/TR/coga-usable/#business-considerations as to why as a reference point to WCAG2ICT and leave it at that 14:35:59 q? 14:36:09 ack FernandaBonnin 14:36:14 Chuck: Not here to put rules. Suggests to do it on an item by item case. To use if we agree to 14:36:46 FernandaBonnin: not for or against adding. But then we should consider other additional guidance 14:37:14 q+ to suggest that reply to Lisa could mention we have every expectation of address AAA sc with the present activity. 14:37:22 maryjom: agrees. Adding one additional source would require us to add more 14:37:30 q+ 14:37:54 ack me 14:37:54 bruce_bailey, you wanted to suggest that reply to Lisa could mention we have every expectation of address AAA sc with the present activity. 14:38:03 maryjom: Will see if there is a place to add a reference to COGA, but we are not developing techniques? 14:38:34 Cannot fix my mic uality fo today. Will speak to this later via email. 14:38:41 bruce_bailey: would recommend us to answer that this time we are dealing with AAA, meaning there will be more congnitive-related content. 14:38:45 q? 14:38:45 q+ to say that there is nothing preventing content authors from themselves referencing WCAG2ICT from within their supplementary content 14:38:50 ack ChrisLoiselle 14:39:26 ack Chuck 14:39:26 Chuck, you wanted to say that there is nothing preventing content authors from themselves referencing WCAG2ICT from within their supplementary content 14:40:02 ChrisLoiselle: COGA has business considerations that might be interesting to think. Maybe they could do them the reference to WCAG2ICT. 14:40:20 Chuck: Agrees. COGA could link to WCAG2ICT. Might be more useful that way. 14:40:28 topic: Issue 145 Add info/content on the WCAG exemptions in regulatory work 14:40:42 https://github.com/w3c/wcag2ict/issues/145 14:41:11 +1 to Bruces idea of answering Lisa regarding our AAA expectations. 14:41:21 maryjom: New issue. 145 on adding information of the WCAG exemptions in regulatory (section 508, EN 301 549). 14:41:39 maryjom: Examples are SC dealing with "set of" documents and software 14:41:49 q+ to mention 508 preamble discussed WCAG2ICT 14:41:51 https://www.access-board.gov/ict/#preamble 14:41:55 maryjom: we could add in WCAG2ICT a reference back to those 14:42:19 q+ 14:42:20 Q+ 14:42:41 ack bruce_bailey 14:42:41 bruce_bailey, you wanted to mention 508 preamble discussed WCAG2ICT 14:43:31 bruce_bailey: section 508 points to WCAG2ICT in its preamble. 14:43:33 q+ 14:43:41 ack mitch 14:44:45 mitch11: there is some wording in the prior WCAG2ICT that "implies" exceptions. And then regulation took from there 14:44:48 shadi has joined #wcag2ict 14:45:03 mitch11: whatever we do it will not have a real impact 14:45:05 ack Mike_Pluke 14:45:45 ack Chuck 14:45:48 Mike_Pluke: explains why EN ommited these SC as they were not sufficiently defined to enable testing. 14:46:36 Chuck: doesn't see us to make big changes to the language we already used in these SC. 14:46:37 FWIW, i like "omitted" better than "exempted" 14:47:22 maryjom: The issue is about if we want to recognise why regulation ommited those and maybe WCAG2ICT could do the same 14:47:30 q? 14:47:35 i heard MJ say "does not make sense to apply" which i agree with 14:47:42 q+ 14:47:50 ack mitch 14:48:04 +1 14:48:08 +1 14:48:26 mitch11: we could ask Sam to ellaborate on that topic 14:48:26 +1 to voluntarying someone not online 14:48:45 at my office, we use "voluntold" 14:48:49 poll: Ask Sam to draft the change in content for the exempted criteria 14:48:50 :) 14:48:56 +1 to bruce :-) 14:48:58 +1 14:48:59 +1 14:49:01 +1 14:49:02 +1 14:49:04 +1 14:49:07 +1 14:49:08 +1 14:49:20 +1 14:50:12 topic: Issue 54 Making the WCAG2ICT approach to the four "set of Web pages" SCs acceptable 14:50:21 https://github.com/w3c/wcag2ict/issues/54 14:50:25 maryjom: new topic. Issue 54. 14:51:39 all comments thus far summarized into comment: https://github.com/w3c/wcag2ict/issues/54#issuecomment-1309534677 14:52:08 q? 14:52:27 Q+ 14:52:35 maryjom: explains the topic proposed by Mike, to rething WCAG approach to the "set of" SC 14:52:39 ack Mike_Pluke 14:53:24 Mike_Pluke: worried about important accessibility isssues related to these SC that could be lost if EN or 508 ommits them 14:53:45 +1 to Mike's observations 14:54:01 Mike_Pluke: even if knowing that WCAG does not refer to the "within a page" equivalents issues 14:54:03 q+ 14:54:12 ack mitch 14:54:56 +1 to that 14:55:23 mitch11: some SC )3.2.4) make a lot of sense in non-web documents and software. We need to look at them 14:55:25 q+ 14:55:26 q? 14:55:32 q+ 14:56:13 maryjom: 3.2.4 makes sense in a single document. Others such as bypass blocks (2.4.1) not so much. 14:56:15 q? 14:56:51 ack Chuck 14:57:06 q+ to double check that we have more liberty this time around to assert "does not apply" ? 14:57:19 maryjom: suggests that Mike ellaborates on the SC that are more relevant from the "set of" list 14:57:36 ack loicmn 14:57:48 Chuck: agrees this in our scope. We need to define priority for that. 14:58:16 Q+ 14:59:11 ack bruce_bailey 14:59:11 bruce_bailey, you wanted to double check that we have more liberty this time around to assert "does not apply" ? 14:59:28 loicmn: Doesn't think we can improve on these SC without modifying WCAG to cover "in a page" 14:59:30 literal wording in charter did not change much 14:59:57 ack Mike_Pluke 15:00:00 bruce_bailey: maybe we can be more specific this time and we can identify "does not apply"? 15:00:05 +1 to loic 15:00:41 +1 to Mike 15:00:43 +1 to mike 15:01:02 rrsagent, draft minutes 15:01:03 I have made the request to generate https://www.w3.org/2023/06/15-wcag2ict-minutes.html bruce_bailey 15:01:10 Mike_Pluke: his suggestion to remove "set of " in WCAG2ICT... but it migh imply that we say that WCAG is missing something 15:01:54 rrsagent, make minutes 15:01:55 I have made the request to generate https://www.w3.org/2023/06/15-wcag2ict-minutes.html maryjom 15:02:11 zakim, end meeting 15:02:11 As of this point the attendees have been loicmn, mitch, maryjom, bruce_bailey, Mike_Pluke, Chuck, FernandaBonnin, \, ChrisLoiselle, btrogdon, olivia, shadi, Devanshu, LauraBMiller 15:02:14 RRSAgent, please draft minutes 15:02:16 I have made the request to generate https://www.w3.org/2023/06/15-wcag2ict-minutes.html Zakim 15:02:22 I am happy to have been of service, maryjom; please remember to excuse RRSAgent. Goodbye 15:02:22 Zakim has left #wcag2ict 15:02:25 rrsagent, bye 15:02:25 I see no action items