13:53:01 RRSAgent has joined #WCAG2ICT 13:53:06 logging to https://www.w3.org/2026/05/28-WCAG2ICT-irc 13:53:06 RRSAgent, make logs Public 13:53:07 Meeting: WCAG2ICT Task Force Teleconference 13:53:18 zakim, clear agenda 13:53:18 agenda cleared 13:53:36 chair: LauraM 13:53:46 meeting: WCAG2ICT Task Force Teleconference 13:53:57 rrsagent, make minutes 13:53:59 I have made the request to generate https://www.w3.org/2026/05/28-WCAG2ICT-minutes.html LauraM 13:54:06 zakim, please time speakers at 2 minutes 13:54:06 ok, LauraM 13:54:13 agenda+ Announcements 13:54:18 agenda+ 3.1.4 Abbreviations - Proposed content to review 13:54:23 agenda+ 3.1.5 Reading Level - Proposed content to review 13:54:30 agenda+ 3.1.6 Pronunciation - Discussion, Laura 13:54:36 agenda+ 3.3.5 Help - Discussion, Bruce 13:54:42 scribe+ PhilDay 13:54:42 agenda+ Update on adding note to 4.1.1 - Request feedback from Mitch Input on Issue - Laura 13:54:48 present+ 13:54:49 present+ 13:54:58 regrets: PhilDay 13:56:07 regrets - PhilDay 13:56:11 present+ 13:56:15 regrets/ 13:56:34 rrsagent, make minutes 13:56:35 I have made the request to generate https://www.w3.org/2026/05/28-WCAG2ICT-minutes.html PhilDay 13:57:35 Link for agenda: https://github.com/w3c/wcag2ict/wiki/Agendas 13:57:47 Work for the week: https://github.com/w3c/wcag2ict/wiki/Work-for-the-week 13:58:03 present+ 13:58:07 agenda? 13:59:45 bbailey has joined #wcag2ict 14:00:36 loicmn has joined #wcag2ict 14:00:42 present+ 14:00:43 present+ 14:00:47 present+ 14:01:01 q+ 14:01:04 zakim, take up item 1 14:01:04 agendum 1 -- Announcements -- taken up [from LauraM] 14:02:38 W3C: current CEO has resigned, so there is a transition period to find a new CEO. For now Dominque is the interim CEO 14:02:59 Nothing to indicate a change in direction. 14:03:28 https://urldefense.com/v3/__https://www.w3.org/press-releases/__;!!D5WlZnHMtQ!UWJcwKwqTxoWQUn3_q8B_oXL-w6obW-SDuYuph2sv64A2FL5IGhlITgVqm4YCOP_OLUdJr5Lj_z7trPo$ 14:03:43 https://www.w3.org/press-releases/2026/w3c-leadership-transition/ -> Press Release 14:04:00 zakim, next item 14:04:00 I see a speaker queue remaining and respectfully decline to close this agendum, PhilDay 14:04:04 ack bbailey 14:04:15 GreggVan has joined #wcag2ict 14:04:19 https://www.w3.org/press-releases/2026/w3c-leadership-transition/ 14:04:24 present+ 14:04:33 q? 14:04:38 zakim, next item 14:04:38 agendum 2 -- 3.1.4 Abbreviations - Proposed content to review -- taken up [from LauraM] 14:04:55 https://github.com/w3c/wcag2ict/issues/559 14:05:39 Proposed content (from issue). 14:05:39 Applying SC 3.1.4 Abbreviations to non-web documents 14:05:39 This success criterion is problematic to apply directly to non-web documents because not all document formats provide support for a mechanism to provide the expanded form or meaning of abbreviations. Where the non-web document format provides such a mechanism, the non-web document should work with these features to the extent the format provides. 14:05:39 Doing so would still address the user needs identified in Intent from Understanding Success Criterion 3.1.4. 14:05:41 Applying Applying SC 3.1.4 Abbreviations to non-web software 14:05:41 This success criterion is problematic to apply directly to non-web software because not all platforms provide support for a mechanism to provide the expanded form or meaning of abbreviations. Non-web software needs to work with platform capabilities where they exist, but when the platform does not provide capabilities, it is unreasonable for all 14:05:41 apps on a particular platform to build in their own mechanism to provide the expanded form or meaning of abbreviations. Where the platform does provide a suitable mechanism, the non-web software should work with these features to the extent the platform provides. Doing so would still address the user needs identified in Intent from Understanding 14:05:42 Success Criterion 3.1.4. 14:05:42 NOTE (FOR NON-WEB SOFTWARE) 14:05:42 See also the Comments on Closed Functionality. 14:05:43 And in SC problematic for closed: 14:05:43 3.1.4 Abbreviations - This success criterion is problematic to apply to ICT with closed functionality as they may not provide support for a mechanism to provide the expanded form or meaning of abbreviations. 14:05:55 q+ 14:06:18 ack GreggVan 14:06:39 GreggVan: Makes sense for documents. Software - if there isn't a mechanism, you should just add it. 14:06:53 q+ to say it is about the platform 14:07:08 ack PhilDay 14:07:08 PhilDay, you wanted to say it is about the platform 14:08:06 PhilDay: It's about the platform - if it is not in the platform, then it may be unreasonable to expect apps to add this feature 14:08:17 q+ 14:08:31 GreggVan: Think you could still expect apps to add some support for abbreviations. You could at least describe the abbreviations 14:08:42 q? 14:08:43 q+ to ask which criterion we are dealing with 3.1.3 or 3.1.4 14:08:59 agenda? 14:09:14 q? 14:09:17 ack bbailey 14:09:20 ack bbailey 14:09:34 bbailey: Think it applies as written to software 14:10:26 ack Loicmn 14:10:27 loicmn, you wanted to ask which criterion we are dealing with 3.1.3 or 3.1.4 14:10:29 bbailey: Most of the time you are relying on software to pick up what is an abbreviation 14:10:52 loicmn: Which SC? 3.1.4 or 3.1.3 14:11:26 For 3.1.3 we agreed that it was not reasonable for apps to implement their own mechanism. So it makes sense to use the same approach for 3.1.4 if we have already agreed 3.1.3 14:11:42 q+ 14:12:02 ack GreggVan 14:12:27 https://w3c.github.io/wcag2ict/#unusual-words 14:12:37 GreggVan: Think we should say it applies as written (for software). Then put a note to say help could be a mechanism to explain an abbreviation. 14:12:55 q+ 14:13:10 ... It doesn't need to be provided inline - just offer some mechanism like hel 14:13:12 s/hel/help 14:13:40 Daniel: Agree with Gregg's - providing feature another way like a help feature is appropriate. 14:14:06 +1 to Gregg, but we must do the same for 3.1.3 14:14:25 ACTION: Editors to rework both 3.1.4 and 3.1.3 to maintain consistency 14:14:42 I am not loving what we have for 3.1.3... 14:15:10 LauraM clarifying that we should agree content for 3.1.4, and then go back and edit 3.1.3 14:15:16 q+ to ask when we did 3.1.3 ? 14:16:33 ack bbailey 14:16:33 bbailey, you wanted to ask when we did 3.1.3 ? 14:18:10 Proposed text for 3.1.4: 14:18:10 Applying Applying SC 3.1.4 Abbreviations to non-web software 14:18:10 This success criterion applies as written as described in Intent from Understanding Success Criterion 3.1.4. 14:18:10 NOTE 14:18:11 Help is a mechanism for software that can provide explanations of abbreviations. This would address the user needs identified in Intent from Understanding Success Criterion 3.1.4. 14:18:15 3.1.4 Abbreviations - This success criterion applies as written for software (with no note about closed functionality) 14:18:15 NOTE: Help is a mechanism for software that can provide explanations of abbreviations 14:18:52 (Use PhilDay version) 14:19:09 +1 14:19:10 +1 14:19:10 +1 14:19:11 +1 14:19:13 +1 14:19:17 +1 14:19:18 +1 14:21:49 DRAFT RESOLUTION: For 3.1.4 Abbreviations to non-web software Applying Applying SC 3.1.4 Abbreviations to non-web software 14:21:49 This success criterion applies as written as described in Intent from Understanding Success Criterion 3.1.4. 14:21:49 NOTE: Help is a mechanism for software that can provide explanations of abbreviations. This would address the user needs identified in Intent from Understanding Success Criterion 3.1.4. 14:21:49 3.1.4 Abbreviations - This success criterion applies as written for software (with no note about closed functionality) 14:21:51 NOTE: Help is a mechanism for software that can provide explanations of abbreviations 14:22:01 +1 14:22:03 +1 14:22:12 +1 14:22:50 +1 14:22:51 RESOLUTION: For 3.1.4 Abbreviations to non-web software Applying Applying SC 3.1.4 Abbreviations to non-web software 14:22:51 This success criterion applies as written as described in Intent from Understanding Success Criterion 3.1.4. 14:22:51 NOTE: Help is a mechanism for software that can provide explanations of abbreviations. This would address the user needs identified in Intent from Understanding Success Criterion 3.1.4. 14:22:51 3.1.4 Abbreviations - This success criterion applies as written for software (with no note about closed functionality) 14:22:53 NOTE: Help is a mechanism for software that can provide explanations of abbreviations 14:22:54 rrsagent, draft minutes 14:22:55 I have made the request to generate https://www.w3.org/2026/05/28-WCAG2ICT-minutes.html bbailey 14:23:15 rrsagent,draft minutes 14:23:16 I have made the request to generate https://www.w3.org/2026/05/28-WCAG2ICT-minutes.html Daniel 14:24:56 DRAFT RESOLUTION: Proposed edits to 3.1.3 to make consistent with above 3.1.4 14:25:00 +1 14:25:00 +1 14:25:08 +1 14:25:12 +1 14:25:15 +1 14:25:21 +1 14:25:28 +1 14:25:30 RESOLUTION: Proposed edits to 3.1.3 to make consistent with above 3.1.4 14:25:53 zakim, next item 14:25:53 I see a speaker queue remaining and respectfully decline to close this agendum, PhilDay 14:25:55 q? 14:26:01 q- 14:26:07 zakim, next item 14:26:07 agendum 3 -- 3.1.5 Reading Level - Proposed content to review -- taken up [from LauraM] 14:26:38 https://github.com/w3c/wcag2ict/issues/560 14:26:50 Proposed content for review by TF: 14:26:50 3.1.5 Reading Level 14:26:50 (Level AAA) 14:26:50 When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. 14:26:52 Applying SC 3.1.5 Reading Level to non-web documents 14:26:52 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5. 14:26:52 Applying SC 3.1.5 Reading Level to non-web software 14:26:53 This success criterion may be problematic to apply directly to non-web software because not all platforms provide support for providing supplemental content, or alternative versions of content (such as a version that does not require reading ability more advanced than the lower secondary education level). Non-web software needs to work with 14:26:53 platform capabilities where they exist, but when the platform does not provide capabilities, it is unreasonable for all apps on a particular platform to build in their own mechanism to provide supplemental content or alternative versions. Where the platform does provide a suitable mechanism, the non-web software should work with these features to 14:26:53 the extent the platform provides. Doing so would still address the user needs identified in Intent from Understanding Success Criterion 3.1.5. 14:26:54 NOTE (ADDED) (NON-WEB SOFTWARE) 14:26:54 See also the Comments on Closed Functionality. 14:26:54 And in SC problematic for closed: 14:27:19 3.1.5 Reading Level - This may be problematic to apply for ICT with closed functionality, as there may be no method of providing supplemental content or alternative versions. Ensuring that the text provided by the ICT with closed functionality is no more advanced than the lower secondary education level would still address the user needs identified 14:27:19 in Intent from Understanding Success Criterion 3.1.5. 14:27:24 https://github.com/w3c/wcag2ict/issues/560 14:29:12 q+ 14:29:28 GreggVan: Change sentence to remove redundancy: Where the platform does provide a suitable mechanism, the non-web software should work with these features. 14:29:54 bbailey: Suggest we take a similar approach to 3.1.4 - applies as written for software, add a note 14:30:20 q+ 14:30:33 ack bbailey 14:30:38 ack GreggVan 14:31:16 Proposal to address bbailey's suggestion (by moving note to software, rather than just for closed). But still saying it is problematic. 14:31:16 Applying SC 3.1.5 Reading Level to non-web documents 14:31:16 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5. 14:31:16 Applying SC 3.1.5 Reading Level to non-web software 14:31:18 This success criterion may be problematic to apply directly to non-web software because not all platforms provide support for providing supplemental content, or alternative versions of content (such as a version that does not require reading ability more advanced than the lower secondary education level). Non-web software needs to work with 14:31:18 platform capabilities where they exist, but when the platform does not provide capabilities, it is unreasonable for all apps on a particular platform to build in their own mechanism to provide supplemental content or alternative versions. Where the platform does provide a suitable mechanism, the non-web software should work with these features. 14:31:18 NOTE 14:31:19 Ensuring that the text provided by the ICT with closed functionality is no more advanced than the lower secondary education level would still address the user needs identified in Intent from Understanding Success Criterion 3.1.5. 14:31:35 q? 14:31:52 GreggVan: Not sure it can apply as written for software in all cases 14:32:28 bbailey: Think it is the same problem for web software - not sure why we should add a caveat for non-web software 14:33:06 ... OK if a Physics application uses advanced terminology. 14:33:28 q+ to suggest applies as written with single note 14:33:47 NOTE 14:33:47 Ensuring that the text provided by the ICT with closed functionality is no more advanced than the lower secondary education level would still address the user needs identified in Intent from Understanding Success Criterion 3.1.5. 14:33:48 ack PhilDay 14:33:48 PhilDay, you wanted to suggest applies as written with single note 14:34:00 i am all for keeping a note 14:34:22 NOTE 14:34:22 Ensuring that the text provided by the non-web software is no more advanced than the lower secondary education level would still address the user needs identified in Intent from Understanding Success Criterion 3.1.5. 14:34:22 NOTE 14:34:22 Help can be a mechanism for explaining 14:34:56 PhilDay: Second note needs padding out 14:35:56 GreggVan: Why don't we state it as an exception - and reference trigonometry as an example of a concept that is above the reading level 14:37:14 q+ 14:37:25 GreggVan: NOTE 1 should be phrased as an exception 14:37:28 NOTE 2 is OK. 14:37:45 ack Daniel 14:37:52 q+ to say that NOTE 1 is already in the SC and NOTE 2 can be rephrased to refer to supplemental content 14:38:02 ack me 14:38:03 ack loicmn 14:38:03 loicmn, you wanted to say that NOTE 1 is already in the SC and NOTE 2 can be rephrased to refer to supplemental content 14:38:17 ack loicmn 14:38:30 q+ 14:38:56 loicmn: NOTE 1 is already implied in the SC, so can be removed. 14:38:56 The other note could be modified to explicitly refer to supplemental content 14:39:12 NOTE 14:39:12 Help can be a mechanism for providing supplemental content. 14:40:09 ack GreggVan 14:40:28 SC says: When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. 14:41:10 loicmn: This is a problem in WCAG - and that is why it is AAA 14:41:12 q+ to agree with not fixing WCAG 2.2 14:41:40 NOTE Help can be a mechanism for providing supplemental content 14:41:57 q+ to clarify what we now have 14:42:00 ack bbailey 14:42:00 bbailey, you wanted to agree with not fixing WCAG 2.2 14:42:02 q+ 14:42:03 ack bbailey 14:42:35 bbailey: Agree that we are not fixing WCAG 2.2, but we should capture and pass back to WCAG 2.2. 14:42:42 ack PhilDay 14:42:42 PhilDay, you wanted to clarify what we now have 14:42:45 GreggVan: But it's AAA so we don't need to apply 14:43:15 q+ 14:43:30 q+ 14:43:35 q? 14:43:39 ack loicmn 14:43:45 PhilDay: Clarification - We are saying that the software applies directly as written and not sure about the rest 14:43:54 loicmn: Remove exception, keep note about help 14:43:57 q? 14:44:10 ack Daniel 14:44:11 q? 14:44:30 Daniel: The SC doesn't contain any exception. 14:44:40 q? 14:44:56 ack GreggVan 14:45:07 GreggVan: When it applies - is a form of exception 14:45:21 q+ 14:45:26 q? 14:45:32 ack GreggVan 14:45:48 +1 to loicmn: delete exception, add a note 14:45:59 Latest proposed content for software: 14:45:59 Applying SC 3.1.5 Reading Level to non-web software 14:45:59 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5, 14:45:59 NOTE 14:46:00 Help can be a mechanism for providing supplemental content. 14:46:35 +1 to remove exception, just add 1 note 14:47:09 LauraM: +1 if you agree with this approach 14:47:14 +1 14:47:22 Proposed content 14:47:23 Applying SC 3.1.5 Reading Level to non-web documents 14:47:23 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5. 14:47:23 Applying SC 3.1.5 Reading Level to non-web software 14:47:23 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5, 14:47:25 NOTE 14:47:25 Help can be a mechanism for providing supplemental content. 14:47:48 q+ 14:47:50 ack bbailey 14:48:19 Applying SC 3.1.5 Reading Level to non-web documents and non-web software 14:48:19 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5. 14:48:19 NOTE 14:48:19 Help can be a mechanism for providing supplemental content. 14:48:35 +1 14:48:35 Applying SC 3.1.5 Reading Level to non-web documents and non-web software 14:48:35 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5. 14:48:35 NOTE (SOFTWARE) 14:48:35 Help can be a mechanism for providing supplemental content. 14:48:46 DRAFT RESOLUTION: Appliesa as written to NWS and NWD along with a note on software that reads " Help can be a mechanism for providing supplemental content." 14:48:50 DRAFT RESOLUTION: Proposed content Applying SC 3.1.5 Reading Level to non-web documents and non-web software This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5. 14:48:50 10:48 NOTE 14:48:50 10:48 Help can be a mechanism for providing supplemental content. 14:49:01 rrsagent, draft minutes 14:49:02 I have made the request to generate https://www.w3.org/2026/05/28-WCAG2ICT-minutes.html bbailey 14:49:12 DRAFT RESOLUTION: Proposed content Applying SC 3.1.5 Reading Level to non-web documents and non-web software This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5. NOTE Help can be a mechanism for providing supplemental content. 14:49:16 +1 14:49:17 +1 14:49:18 +1 14:49:18 +1 14:49:23 +1 14:49:47 s/non-web documents and// 14:49:56 DRAFT RESOLUTION: Proposed content Applying SC 3.1.5 Reading Level to non-web documents and non-web software This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5. with a not on software NOTE Help can be a mechanism for providing supplemental content. 14:49:59 rrsagent, draft minutes 14:50:01 I have made the request to generate https://www.w3.org/2026/05/28-WCAG2ICT-minutes.html Daniel 14:50:19 s/not on/note on 14:50:27 s/10:48 // 14:50:29 s/10:48 // 14:50:29 +1 14:50:31 s /not on/ note on/ 14:50:32 +1 14:50:37 +1 14:50:38 +1 14:50:38 +1 14:50:38 +1 14:50:54 RESOLUTION: Proposed content Applying SC 3.1.5 Reading Level to non-web documents and non-web software This applies directly as written, and as described in Intent from Understanding Success Criterion 3.1.5. with a note on software NOTE Help can be a mechanism for providing supplemental content. 14:50:59 rrsagent, draft minutes 14:51:01 I have made the request to generate https://www.w3.org/2026/05/28-WCAG2ICT-minutes.html bbailey 14:51:07 zakim, next item 14:51:07 agendum 4 -- 3.1.6 Pronunciation - Discussion, Laura -- taken up [from LauraM] 14:51:26 q+ 14:51:52 zakim, next item 14:51:52 I see a speaker queue remaining and respectfully decline to close this agendum, PhilDay 14:51:56 ack Bbailey 14:52:00 q- bbailey 14:52:03 zakim, next item 14:52:03 agendum 4 was just opened, PhilDay 14:52:03 https://github.com/w3c/wcag2ict/pull/937 14:52:14 zakim, next item 14:52:14 agendum 5 -- 3.3.5 Help - Discussion, Bruce -- taken up [from LauraM] 14:52:22 https://github.com/w3c/wcag2ict/issues/563 14:52:44 See: https://deploy-preview-937--wcag2ict.netlify.app/#help 14:54:01 Proposal: 14:54:01 Applying SC 3.3.5 Help to non-web documents and non-web software 14:54:01 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.5. 14:54:01 NOTE 1 (ADDED) 14:54:02 As noted in [glossary item context-sensitive help], clear labels or other information provided by the system can act as context-sensitive help. 14:54:02 NOTE 2 (ADDED) (FOR NON-WEB SOFTWARE) 14:54:02 See also the Comments on Closed Functionality. 14:55:21 bbailey: Applies directly as written, 2 notes added 14:55:36 LauraM: Any disagreement with this approach? 14:55:38 q? 14:56:33 bbailey: Did have 1 question 14:57:12 ... Do we want to say something about non-web documents - to differentiate between media players and static docs 14:57:30 Proposed NOTE (FOR NON-WEB DOCUMENTS) 14:57:31 This success criterion readily applies to player/viewer software application. This success criterion is generally not applicable to static non-web documents. It is possible for some non-web file formats to include interactive elements that are specific to the document and independent of the software used. Examples of non-web documents that can 14:57:31 directly support context-sensitive include, but are not limited to, PDF forms, complex spreadsheets, and database source files. 14:58:19 Latest update from Bruce: Applying SC 3.3.5 Help to non-web documents and non-web software 14:58:20 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.5. 14:58:20 NOTE 1 (ADDED) 14:58:20 As noted in [glossary item context-sensitive help], clear labels or other information provided by the system can act as context-sensitive help. 14:58:21 NOTE 2 (ADDED) (FOR NON-WEB SOFTWARE) 14:58:21 See also the Comments on Closed Functionality. 14:58:21 NOTE (NON-WEB DOCUMENTS) 14:58:22 This success criterion readily applies to player/viewer software application. This success criterion is generally not applicable to static non-web documents. It is possible for some non-web file formats to include interactive elements that are specific to the document and independent of the software used. Examples of non-web documents that can 14:58:22 directly support context-sensitive include, but are not limited to, PDF forms, complex spreadsheets, and database source files. 14:59:05 NOTE (NON-WEB DOCUMENTS) 14:59:05 This success criterion readily applies to player/viewer software application. This success criterion is problematic to apply to static non-web documents. It is possible for some non-web file formats to include interactive elements that are specific to the document and independent of the software used. Examples of non-web documents that can directly 14:59:05 support context-sensitive include, but are not limited to, PDF forms, complex spreadsheets, and database source files. 15:00:26 DRAFT RESOLUTION: Proposal: 15:00:27 Applying SC 3.3.5 Help to non-web documents and non-web software 15:00:27 This applies directly as written, and as described in Intent from Understanding Success Criterion 3.3.5. 15:00:27 NOTE 1 (ADDED) 15:00:28 As noted in [glossary item context-sensitive help], clear labels or other information provided by the system can act as context-sensitive help. 15:00:28 NOTE 2 (ADDED) (FOR NON-WEB SOFTWARE) 15:00:28 See also the Comments on Closed Functionality NOTE 3 (FOR NON-WEB DOCUMENTS) 15:00:29 This success criterion readily applies to player/viewer software application. This success criterion is problematic to apply to static non-web documents. It is possible for some non-web file formats to include interactive elements that are specific to the document and independent of the software used. Examples of non-web documents that can directly 15:00:29 support context-sensitive include, but are not limited to, PDF forms, complex spreadsheets, and database source files 15:00:48 +1 15:01:32 DRAFT RESOLUTION 3.3.5 Help add three notes as written above 15:01:38 +1 15:01:40 +1 15:01:47 +1 15:01:47 +1 15:01:47 +1 15:01:48 +1 15:01:50 +1 15:01:54 RESOLUTION 3.3.5 Help add three notes as written above 15:02:19 ACTION: bbailey to fix PR 15:02:29 rrsagent, draft minutes 15:02:31 I have made the request to generate https://www.w3.org/2026/05/28-WCAG2ICT-minutes.html bbailey 15:02:37 bbailey will fix PR which was in draft, and then make final 15:02:52 loicmn has left #wcag2ict 15:03:19 zakim, end meeting 15:03:19 As of this point the attendees have been PhilDay, LauraM, Jim, loicmn, bbailey, Daniel, GreggVan 15:03:21 RRSAgent, please draft minutes v2 15:03:23 I have made the request to generate https://www.w3.org/2026/05/28-WCAG2ICT-minutes.html Zakim 15:03:29 I am happy to have been of service, LauraM; please remember to excuse RRSAgent. Goodbye 15:03:29 rrsagent, bye 15:03:29 I see 2 open action items saved in https://www.w3.org/2026/05/28-WCAG2ICT-actions.rdf : 15:03:29 ACTION: Editors to rework both 3.1.4 and 3.1.3 to maintain consistency [1] 15:03:29 recorded in https://www.w3.org/2026/05/28-WCAG2ICT-irc#T14-14-25 15:03:29 ACTION: bbailey to fix PR [2] 15:03:29 recorded in https://www.w3.org/2026/05/28-WCAG2ICT-irc#T15-02-19 15:03:29 Zakim has left #wcag2ict