13:08:28 RRSAgent has joined #wcag2ict 13:08:32 logging to https://www.w3.org/2024/08/23-wcag2ict-irc 13:08:32 RRSAgent, make logs Public 13:08:33 Meeting: WCAG2ICT Task Force Teleconference 13:08:38 chair: Mary Jo Mueller 13:08:54 meeting: WCAG2ICT Task Force Extra Friday Teleconference 13:09:21 scribe+ PhilDay 13:09:49 https://github.com/w3c/wcag2ict/issues?q=is%3Aissue+is%3Aopen+-assignee%3A%22daniel-montalvo%22+-label%3A%22Project+task%22 13:10:20 https://docs.google.com/document/d/1o6ruxbOKxAU6aWWz9Ac7P8DMi7lrIwXCy5DgvRzQZA4/edit 13:11:03 Issue 473: https://github.com/w3c/wcag2ict/issues/473#top 13:11:16 Issue: https://github.com/w3c/wcag2ict/issues/473 13:11:25 TOPIC: Issue 473 - Definitions and explanations for “Set of Documents” and “Set of Software Programs” produces strange corner cases that should be addressed or explained 13:11:58 Issue 473, working ideas in Google doc: https://github.com/w3c/wcag2ict/issues/473#top 13:11:58 Issue: https://github.com/w3c/wcag2ict/issues/473 13:12:45 Proposal 1: No change to the content, with the following proposed answer 13:12:45 Thank you for your question regarding WCAG2ICT. The Task Force considered making the advisory content regarding “sets of software” and “sets of documents” more formal, but decided against making any changes. While overlapping sets could occur, we do not foresee a problem in evaluating each overlapping set as a set. 13:12:56 Add proposal 1 to a survey for the coming week 13:12:59 +1 to proposal 1 13:14:06 TOPIC: Issue 466 - Closed functionality list - suggested additions 13:14:14 Issue: https://github.com/w3c/wcag2ict/issues/466 13:14:38 https://docs.google.com/document/d/1YfD_Rxeg72vLZXBuV05BDvlKFCjwy5KZEOeeJSTtfLY/edit#heading=h.vsbif8i8ovr7 13:16:48 Proposal 1: No change to examples of closed functionality 13:16:48 [Examples excerpt from the Key Terms section on “closed functionality (as used by WCAG2ICT)”] 13:16:48 Example: Examples of technology that may have closed functionality include: 13:16:48 self-service transaction machines or kiosks — examples include machines used for retail self-checkout, point of sales (POS) terminals, ticketing and self-check-in, and Automated Teller Machines (ATMs). 13:16:50 telephony devices such as internet phones, feature phones, smartphones, and phone-enabled tablets 13:16:50 entertainment technologies including smart TVs, set-top boxes, smart displays, smart speakers, smart watches, and tablets 13:16:50 an ebook reader or standalone ebook software that allows assistive technologies to access all of the user interface controls of the ebook program (open functionality) but does not allow the assistive technologies to access the actual content of book (closed functionality). 13:16:51 an operating system that makes the user provide login credentials before it allows any assistive technologies to be loaded. The login portion would be closed functionality. 13:16:51 other technology devices, such as printers, displays, and Internet of Things (IoT) devices. 13:16:51 [Examples excerpt from the Comments on Closed Functionality section] 13:16:52 Example: In developing guidance for closed functionality, the task force has considered examples of ICT that historically have been partially or fully closed to assistive technologies: 13:16:52 self-service transaction machines or kiosks (e.g. retail self-checkout, point of sales (POS) terminals, and Automated Teller Machines (ATMs)) 13:16:52 telephony devices (e.g. internet phones, feature phones, and smartphones) 13:16:53 entertainment technologies (e.g. smart TV, set-top box, smart watches) 13:16:53 ebook reader 13:16:54 computer that is locked down due to a policy so that users may not adjust settings or install software 13:16:54 other technology devices (e.g. printers, displays, and Internet of Things (IoT) devices). 13:17:28 Proposal 2: Incorporate suggested examples from Issue 466 13:17:28 [Examples excerpt from the Key Terms section on “closed functionality (as used by WCAG2ICT)”] 13:17:28 Example: Examples of technology that may have closed functionality include but are not limited to: 13:17:28 self-service transaction machines or kiosks — examples include machines used for retail self-checkout, point of sales (POS) terminals, ticketing and self-check-in, and Automated Teller Machines (ATMs). 13:17:30 telephony devices such as internet phones, feature phones, smartphones, and phone-enabled tablets 13:17:30 educational devices such as interactive whiteboards and smart boards 13:17:30 entertainment technologies including gaming platforms or consoles, smart TVs, set-top boxes, smart displays, smart speakers, smart watches, and tablets 13:17:31 an ebook reader or standalone ebook software that allows assistive technologies to access all of the user interface controls of the ebook program (open functionality) but does not allow the assistive technologies to access the actual content of the book (closed functionality). 13:17:31 medical devices such as digital blood pressure monitors, glucose meters, or other wearable devices 13:17:31 an operating system that makes the user provide login credentials before it allows any assistive technologies to be loaded. The login portion would be closed functionality. 13:17:32 other technology devices, such as printers, displays, and Internet of Things (IoT) devices. 13:17:59 [Examples excerpt from the Comments on Closed Functionality section] 13:17:59 Example: In developing guidance for closed functionality, the task force has considered examples of ICT that historically have been partially or fully closed to assistive technologies: 13:17:59 self-service transaction machines or kiosks (e.g. retail self-checkout, point of sales (POS) terminals, and Automated Teller Machines (ATMs)) 13:17:59 telephony devices (e.g. internet phones, feature phones, and smartphones) 13:18:01 educational devices such as interactive whiteboards and smart boards 13:18:01 entertainment technologies (e.g. gaming platforms or consoles, smart TV, set-top box, smart watches) 13:18:01 ebook reader 13:18:02 medical devices such as digital blood pressure monitors, glucose meters, or other wearable devices 13:18:02 computer that is locked down due to a policy so that users may not adjust settings or install software 13:18:02 other technology devices (e.g. printers, displays, and Internet of Things (IoT) devices). 13:20:57 2 lists of closed functionality examples. First is a full list of systems that may be closed. 13:21:13 Second list is specifically those technologies that the TF has considered 13:23:57 After discussion - add new examples only to the definitions section, not to the Comments on Closed Functionality list 13:24:36 Proposal 2 modified as follows: 13:25:00 Proposal 2: Incorporate suggested examples from Issue 466 13:25:00 [Examples excerpt from the Key Terms section on “closed functionality (as used by WCAG2ICT)”] 13:25:00 Example: Examples of technology that may have closed functionality include but are not limited to: 13:25:00 self-service transaction machines or kiosks — examples include machines used for retail self-checkout, point of sales (POS) terminals, ticketing and self-check-in, and Automated Teller Machines (ATMs). 13:25:02 telephony devices such as internet phones, feature phones, smartphones, and phone-enabled tablets 13:25:02 educational devices such as interactive whiteboards and smart boards 13:25:02 entertainment technologies including gaming platforms or consoles, smart TVs, set-top boxes, smart displays, smart speakers, smart watches, and tablets 13:25:03 an ebook reader or standalone ebook software that allows assistive technologies to access all of the user interface controls of the ebook program (open functionality) but does not allow the assistive technologies to access the actual content of the book (closed functionality). 13:25:03 medical devices such as digital blood pressure monitors, glucose meters, or other wearable devices 13:25:03 an operating system that makes the user provide login credentials before it allows any assistive technologies to be loaded. The login portion would be closed functionality. 13:25:04 other technology devices, such as printers, displays, and Internet of Things (IoT) devices. 13:25:04 [Examples excerpt from the Comments on Closed Functionality section] 13:25:04 Example: In developing guidance for closed functionality, the task force has considered specific examples of ICT that historically have been partially or fully closed to assistive technologies: 13:25:05 self-service transaction machines or kiosks (e.g. retail self-checkout, point of sales (POS) terminals, and Automated Teller Machines (ATMs)) 13:25:24 telephony devices (e.g. internet phones, feature phones, and smartphones) 13:25:24 entertainment technologies (e.g. smart TV, set-top box, smart watches) 13:25:24 ebook reader 13:25:25 computer that is locked down due to a policy so that users may not adjust settings or install software 13:25:25 other technology devices (e.g. printers, displays, and Internet of Things (IoT) devices). 13:26:32 TOPIC: Issue 465 - Seeking clarity for key term 'underlying platform software' 13:26:45 Issue: https://github.com/w3c/wcag2ict/issues/465 13:26:45 Issue 465: https://github.com/w3c/wcag2ict/issues/465 13:27:03 Google doc: https://docs.google.com/document/d/1YfD_Rxeg72vLZXBuV05BDvlKFCjwy5KZEOeeJSTtfLY/edit#heading=h.riup8xx2ph62 13:28:37 Decision yesterday was to not change SCs 13:28:44 Correct Google doc: https://docs.google.com/document/d/1o6ruxbOKxAU6aWWz9Ac7P8DMi7lrIwXCy5DgvRzQZA4/edit#heading=h.gaeapqyyickf 13:29:05 No change to SCs 2.5.1, 2.5.2 and 2.5.7 13:29:28 Accessible authentication also has "underlying" platform software 13:29:50 So SC 3.3.8 should leave as is, to keep consistent with SCs 2.5.1, 2.5.2, 2.5.7 13:31:12 Only things we will change are removing "Underlying" from Note 1 in the Glossary entry 'keyboard interface' and from SC 2.1.1 Keyboard 13:32:23 TOPIC: Issue 464 - Suggest slight clarification of audience and outcomes #464 13:32:47 Google doc: https://docs.google.com/document/d/1o6ruxbOKxAU6aWWz9Ac7P8DMi7lrIwXCy5DgvRzQZA4/edit#heading=h.jr7sf28haxhk 13:33:00 Issue: https://github.com/w3c/wcag2ict/issues/464 13:33:38 Decision made yesterday - just needs a PR to be created 13:34:34 TOPIC: Issue 463 - Programmatically determine the language of text #463 13:34:42 Issue: https://github.com/w3c/wcag2ict/issues/463 13:35:05 Google doc: https://docs.google.com/document/d/1o6ruxbOKxAU6aWWz9Ac7P8DMi7lrIwXCy5DgvRzQZA4/edit#heading=h.btjjjqb0z1lr 13:37:14 Question is regarding the quote from WCAG - not how we apply it. 13:39:04 https://w3c.github.io/wcag2ict/#language-of-parts 13:39:13 Our application: https://w3c.github.io/wcag2ict/#applying-sc-3-1-2-language-of-parts-to-non-web-documents-and-software 13:39:55 Only change from WCAG is word substitution - content replaced with non-web document and software 13:40:42 Definition of programmatically determined - https://w3c.github.io/wcag2ict/#applying-programmatically-determined-to-non-web-documents-and-software 13:42:09 Looks like this is just a question on the original WCAG language, not our word substitutions for ICT 13:46:00 Chris to draft reply 13:47:16 Stepping away for a few mins... 13:49:27 s/Stepping away for a few mins.../ 13:50:39 Draft reply to go in google doc for others to give input 13:51:10 https://docs.google.com/document/d/1YfD_Rxeg72vLZXBuV05BDvlKFCjwy5KZEOeeJSTtfLY/edit#heading=h.btjjjqb0z1lr 13:51:21 (Now moved to horizontal review google doc) 13:53:49 TOPIC: https://github.com/w3c/wcag2ict/issues/427 13:54:05 Needs 2 proposals to be added to survey - one version with, one version without 13:54:35 Mary Jo to work on this one, add options to google doc, then put in survey 13:55:10 TOPIC: Issue 421 - In definition of 'keyboard interface' and in 2.1.1, "would satisfy the success criterion" is incomplete #421 13:55:45 Mary Jo to propose 2 options and survey 13:57:31 TOPIC: Issue 383 - Adjust links in Guidance Section to link to all taskforce and AG publications #383 13:58:07 If we point to an evergreen link, then the Curren link points to lots of documents. Only a few are relevant to WCAG2ICT, and are difficult to identify! 13:58:51 s/Curren/curent 13:59:00 s/curent/current 13:59:21 Categories make it difficult to search 14:01:12 https://www.w3.org/WAI/about/groups/agwg/task-forces/ ? 14:02:15 We could point to the general TF page - and suggest people refer to specific guidance from these areas that may be helpful... 14:02:36 https://www.w3.org/WAI/about/groups/task-forces/ 14:02:48 Refer to the publications from these various groups 14:04:30 Mary Jo to draft PR on this and add to survey 14:06:33 Daniel has worked on a few PRs. Editor's to review and give input 14:06:48 s/Editor's/Editors 14:09:02 rrsagent, draft minutes 14:09:03 I have made the request to generate https://www.w3.org/2024/08/23-wcag2ict-minutes.html PhilDay 14:09:12 present+ maryjom, PhilDay, ChrisLoiselle 14:09:19 zakim, end meeting 14:09:19 As of this point the attendees have been maryjom, PhilDay, ChrisLoiselle 14:09:21 RRSAgent, please draft minutes v2 14:09:22 I have made the request to generate https://www.w3.org/2024/08/23-wcag2ict-minutes.html Zakim 14:09:28 I am happy to have been of service, maryjom; please remember to excuse RRSAgent. Goodbye 14:09:29 Zakim has left #wcag2ict 14:09:36 rrsagent, bye 14:09:36 I see no action items