14:33:50 RRSAgent has joined #wcag2ict 14:33:54 logging to https://www.w3.org/2025/02/27-wcag2ict-irc 14:33:54 RRSAgent, make logs Public 14:33:55 Meeting: WCAG2ICT Task Force Teleconference 14:34:04 zakim, clear agenda 14:34:04 agenda cleared 14:34:09 chair: Mary Jo Mueller 14:34:16 rrsagent, make minutes 14:34:18 I have made the request to generate https://www.w3.org/2025/02/27-wcag2ict-minutes.html maryjom 14:34:25 agenda+ Announcements 14:35:18 agenda+ Develop WCAG2ICT "Explainer" Content 14:35:35 agenda+ Analysis spreadsheet - SC that could use more extensive language changes 14:47:46 bruce_bailey has joined #wcag2ict 14:56:31 PhilDay has joined #wcag2ict 14:57:12 present+ 14:57:41 present+ 14:59:44 agenda? 15:00:30 scribe+ PhilDay 15:00:55 loicmn has joined #wcag2ict 15:01:25 bruce_bailey has joined #wcag2ict 15:01:31 present+ 15:01:34 Present+ 15:02:19 zakim, take up item 1 15:02:19 agendum 1 -- Announcements -- taken up [from maryjom] 15:02:32 regrets: Daniel, Mitchell 15:04:01 This week - a big request. The mobile accessibility task force is hoping to publish 1st public working draft of their guidance for mobile. 15:04:37 It would be helpful if members of the WCAG2ICT can review - to check consistency with WCAG2ICT - as there may be modifications. 15:05:02 https://w3c.github.io/matf/ 15:05:39 This is “pre-CFC”, i.e. a good (but last) chance to comment before we go into a CFC. 15:05:39 This publication will mark the first step towards the process of publishing a Group Note. 15:05:39 This is your last chance to comment for changes, either at: 15:05:39 https://github.com/w3c/matf/issues 15:05:40 Or to public-mobile-a11y-tf@w3.org 15:05:56 Email sent out on Tuesday 25 Feb from Alastair Campbell 15:07:04 1 week to review the mobile task force working draft 15:07:46 present+ 15:07:57 Does anyone have any time to review this doc in the next week? 15:08:26 I have no bandwidth :( I suggest comment would be to hold off and put under WCAG2ICT 15:08:36 q+ 15:09:15 i agree it is missed opportunity not too coordinate more closely 15:09:20 We may need to provide comment during the 30-day public comment period. 15:10:34 q+ to ask if we could ask MATF to identify any areas of friction between their work and ours? 15:11:06 Chris: Think there is still some discussion to have about how it relates to other W3C - where it is published and how it is organised is an open question. e.g. Is it a subset of WCAG2ICT? 15:11:24 s/Chris/ChrisLoiselle 15:11:31 ack ChrisLoiselle 15:11:34 +1 to Bruce. I had that same idea 15:11:35 ack bruce_bailey 15:11:35 bruce_bailey, you wanted to ask if we could ask MATF to identify any areas of friction between their work and ours? 15:12:01 bruce_bailey: Shame we don't have more time to coordinate. But suggest we ask them for input on where they think there might be areas of friction or challenges, so we can focus on those specific areas. 15:12:26 loicmn has left #wcag2ict 15:12:27 maryjom: To meet up with JJ after CSUN - will discuss matters then 15:12:56 loicmn6 has joined #wcag2ict 15:13:01 present+ 15:13:07 shadi has joined #wcag2ict 15:13:17 present+ 15:13:32 rrsagent, pointer? 15:13:32 See https://www.w3.org/2025/02/27-wcag2ict-irc#T15-13-32 15:13:45 Recap for shadi: This week - a big request. The mobile accessibility task force is hoping to publish 1st public working draft of their guidance for mobile. 15:13:45 It would be helpful if members of the WCAG2ICT can review - to check consistency with WCAG2ICT - as there may be modifications. 15:13:45 https://w3c.github.io/matf/ 15:14:16 q+ to mention that MATF might be of more utility to recent DOJ ADA web rule than WCAG2ICT 15:14:41 ack bruce_bailey 15:14:41 bruce_bailey, you wanted to mention that MATF might be of more utility to recent DOJ ADA web rule than WCAG2ICT 15:14:43 ack bruce_bailey 15:15:19 bruce_bailey: MATF might be of more utility to recent DOJ ADA web rule than WCAG2ICT - as this references primarily mobile, but points to WCAG2ICT at the moment 15:16:20 maryjom: Need to consider inconsistencies with WCAG2ICT and also new EN 301 549 draft. 15:16:49 ... And some ideas might only apply to mobile, not to all software. 15:17:10 zakim, next item 15:17:10 agendum 2 -- Develop WCAG2ICT "Explainer" Content -- taken up [from maryjom] 15:17:30 Google doc: https://docs.google.com/document/d/1hyei09Viby1bCoZnDLYwY9VWpzRvteK9pqt4v9sWCJE/edit?tab=t.0#heading=h.9xfsb5gpu681 15:17:41 +1 to reviewing draft comment 15:17:41 +1 15:17:46 +1 15:17:52 +1 that guidance to U.S. states needs to be harmonized with guidance to Europe. 15:18:02 maryjom: to work on drafting an initial comment on mobile TF. 15:18:11 +1 to reviewing draft maryjom draft comment 15:18:33 maryjom: Cleaned up comments, accepted suggested changes etc to make it easier to review. 15:18:43 [maryjom sharing screen˙ 15:18:51 s/'/] 15:20:21 q+ 15:20:43 ack bruce_bailey 15:20:51 Proposed edit: WCAG2ICT is the acronym used for the W3C Guidance on Applying WCAG 2 to Non-web Information and Communication Technology Group Note. 15:20:56 sometimes WCAG2ICT is the doc sometimes its the TF 15:21:52 maryjom: Add TF when we refer to the task force later to differentiate between document and task force 15:22:02 And refer to group note when we refer to the doc 15:23:21 Latest version "who develops" 15:23:23 Who develops WCAG2ICT 15:23:23 The WCAG2ICT Group Note is developed by a Task Force (TF) of the Accessibility Guidelines Working Group (AG WG). The work statement defines the objectives, scope, approach, and so on for the WCAG2ICT Group Note. The participants of the WCAG2ICT TF are volunteers drawn from W3C member organizations and invited experts and are supported by WAI staff. 15:23:35 q+ 15:23:47 Version being reviewed: Background and Development History for WCAG2ICT 15:23:47 This document is intended to help clarify how to use WCAG 2 to make non-web documents and non-web software more accessible to people with disabilities. Addressing accessibility involves addressing the needs of people with auditory, cognitive, neurological, physical, speech, and visual disabilities, and the needs of people with accessibility 15:23:47 requirements due to the effects of aging. Although this document covers a wide range of issues, it is not able to address all the needs of all people with disabilities. Because WCAG 2 was developed for the Web, addressing accessibility for non-web documents and non-web software may involve requirements beyond those included in this document. 15:23:47 Authors and developers are encouraged to seek relevant advice about current best practices to ensure that non-web documents and non-web software are accessible, as far as possible, to people with disabilities. 15:23:54 ack bruce_bailey 15:24:48 q+ 15:25:30 q+ to say Web or web 15:25:43 ack shadi 15:25:43 ack shadi 15:26:05 I had originally intended to reference the Access Board second ANPRM and suggesting WCAG incorporation by reference for software, and industry had concerns. 15:26:16 +1 to shadi 15:27:06 shadi: Good summary of what the document is -maybe the title should be changed. Sentences 2 & 3 removed or moved to end. (Addressing accessibility... and Although this document...) 15:27:13 +1 to shadi proposal to delete sentences 2 & 3. 15:27:39 q+ to say Replace this document by WCAG2ICT group note 15:28:17 ... Another minor comment. "relevant advice" - is this document irrelevant? Maybe change to "additional advice" 15:29:21 maryjom: Maybe worth talking about previous attempts to use WCAG outside of the web, so this document was created to provide that guidance. 15:29:24 q+ 15:29:34 ack PhilDay 15:29:34 PhilDay, you wanted to say Web or web 15:29:58 Phil, I think we could move to intent and usage 15:30:39 PhilDay: suggest sentences 2-3 move to intent & usage. 15:30:52 maryjom: Other sentences to go into introduction 15:31:02 ack loicmn6 15:31:07 loicmn 15:31:36 loicmn6: "This document" - should "The WCAG2ICT group note is intended to" 15:31:37 Again, I started from 2013 https://www.w3.org/TR/2013/NOTE-wcag2ict-20130905/#intro 15:31:38 +1 good point! 15:31:50 q? 15:31:52 ack shadi 15:31:53 ack loicmn6 15:32:34 shadi: Could be a section called "Why this was created" 15:32:35 explain intent to apply WCAG to non-web software - mention US Access Board etc. 15:33:21 q? 15:33:32 q- 15:33:50 [Now looking at Goals] 15:33:57 Goals 15:33:58 Brief description of the main goal for WCAG2ICT - in a sentence or two. 15:33:58 This document is a companion “explainer” for the WCAG2ICT W3C Group Note. It is meant to be….. 15:35:55 Addition for Background & dev history: This section should cover need for WCAG2ICT Group Note and how it was developed to provide the interpretation for use with regulatory standards (508, EN 301549). 15:36:40 There was a version from 2013 which covered WCAG 2.0 and the latest version of WCAG2ICT covers all WCAG 2 versions. 15:37:17 q+ 15:37:41 ack shadi 15:37:42 ack shadi 15:38:14 shadi: This document doesn't provide "the interpretation". 15:38:52 Sam has joined #wcag2ict 15:38:56 present+ 15:38:57 ... provides guidance or clarification from a W3C perspective to help those who wish to apply WCAG to non-web... 15:39:58 Latest rough draft: This section should cover need for WCAG2ICT Group Note and how it was developed to provide guidance and considerations for applying WCAG in non-web contexts. This helped regulatory standards (508, EN 301549) adopt WCAG criteria for non-web documents and software. There was a version from 2013 which covered WCAG 2.0 and the 15:39:58 latest version of WCAG2ICT covers all WCAG 2 versions. 15:40:54 We may not need a Goal section 15:41:13 If it ends up being too repetitive... 15:41:46 Still more work to do later in the doc 15:42:48 References have been cleaned up 15:44:16 Feel free to add to the document during the week, ready for next week 15:44:20 zakim, next item 15:44:20 agendum 3 -- Analysis spreadsheet - SC that could use more extensive language changes -- taken up [from maryjom] 15:44:41 Google sheet for analysis: https://docs.google.com/spreadsheets/d/1cRGxHxV0mBEI_rvcc2EXS9xcBanQjG6k/edit?gid=1726579776#gid=1726579776 15:45:00 Friday meeting has not worked - nobody has been able to attend. 15:45:10 So we will try and do some of the work in this Thursday session 15:45:35 Assign yourself to a few SCs, then go away and suggest if we need any changes 15:45:42 (e.g. CSS pixels) 15:50:53 Latest editor's draft for ref: https://w3c.github.io/wcag2ict/ 15:58:06 rrsagent, draft minutes 15:58:07 I have made the request to generate https://www.w3.org/2025/02/27-wcag2ict-minutes.html PhilDay 15:59:20 Group worked the remainder of the meeting on filling in the spreadsheet and discussing comments entered into the spreadsheet. 15:59:31 rrsagent, make minutes 15:59:32 I have made the request to generate https://www.w3.org/2025/02/27-wcag2ict-minutes.html maryjom 15:59:41 scribe+ 15:59:55 scribe+ maryjom 16:01:22 shadi: Why would consistent navigation be applied to elements with the same functionality repeated **on the same page**? 16:02:09 loic: This can happen where at the top of the page you have "Previous" and "Next" and may be the opposite order at the bottom of the page. 16:02:25 ...will provide additional examples for us to discuss next time. 16:02:36 rrsagent, make minutes 16:02:37 I have made the request to generate https://www.w3.org/2025/02/27-wcag2ict-minutes.html maryjom 16:03:28 zakim, end meeting 16:03:28 As of this point the attendees have been bruce_bailey, PhilDay, maryjom, GreggVan, loicmn, ChrisLoiselle, shadi, Sam 16:03:30 RRSAgent, please draft minutes v2 16:03:32 I have made the request to generate https://www.w3.org/2025/02/27-wcag2ict-minutes.html Zakim 16:03:38 I am happy to have been of service, maryjom; please remember to excuse RRSAgent. Goodbye 16:03:38 Zakim has left #wcag2ict 16:04:23 loicmn6 has left #wcag2ict 17:25:02 Sam has joined #wcag2ict