13:01:26 RRSAgent has joined #wcag2ict 13:01:30 logging to https://www.w3.org/2024/05/03-wcag2ict-irc 13:01:30 RRSAgent, make logs Public 13:01:31 Meeting: WCAG2ICT Task Force Teleconference 13:01:34 chair: Mary Jo Mueller 13:02:11 meeting: WCAG2ICT Task Force Extra Friday Teleconference 13:05:33 Chuck has joined #wcag2ict 13:08:06 TOPIC: Survey on answers to public comments 13:08:07 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results 13:08:31 Start with Question 4: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq4 13:09:01 Google doc: https://docs.google.com/document/d/1TbtNcNjrpog8-6OYloMcPILh2UsqUOXBjPwVwv7dPsw/edit#heading=h.rdnzztss5c30 13:12:20 mitch11 has joined #wcag2ict 13:13:49 Laura_Miller has joined #WCAG2ICT 13:13:53 present+ 13:15:15 PhilDay has joined #wcag2ict 13:15:21 present 13:15:24 present+ 13:15:54 +1 to include Mitch's response 13:18:58 Question 5: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq5 13:21:09 Google doc on issue 257: https://docs.google.com/document/d/1TbtNcNjrpog8-6OYloMcPILh2UsqUOXBjPwVwv7dPsw/edit#heading=h.rdnzztss5c30 13:23:40 Mitch's additional text was added to the Google doc with a comment to highlight it. 13:24:08 Question 6: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq6 13:24:20 Proposed answer to Issue 221... 13:25:02 +1 to plopping! 13:26:17 Latest text from editor's draft in SC problematic for 1.4.10 reflow: 1.4.10 Reflow — Many closed functionality products do not allow users to modify the viewport or change font sizes, so there would be no need to impose a requirement on all closed functionality that content is able to reflow. Additionally, many closed functionality products do 13:26:17 not display large chunks of text and only have UI controls; in such cases, two-directional scrolling to access the text and UI controls may be considered essential. 13:26:59 Question 7: SC Problematic for Closed FUnctinoality - SC 1.4.10 Reflow 13:27:00 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq7 13:28:17 Google doc link: https://docs.google.com/document/d/1TbtNcNjrpog8-6OYloMcPILh2UsqUOXBjPwVwv7dPsw/edit#heading=h.ynsr98668tn5 13:30:14 Go with options 0 & 2 and resurvey TF 13:31:19 Question 8: Review: Proposed updates to Status of this Document 13:31:27 https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq8 13:31:39 +1 to phil's solution 13:32:48 TOPIC: Second survey on Issue 4 13:33:30 Question (1 of 4) Point 3: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-issue-4-resize-text/results#xq2 13:36:47 https://docs.google.com/document/d/1p5EX9d5Q9L1CghcECjPMVqIBxg4UJUZ5U3A3EZhNxUQ/edit#heading=h.tqu8jju9a2a9 13:39:08 Response to https://github.com/w3c/wcag2ict/issues/4 13:40:58 Remove option 2, just survey options 1 and 3 with the wider TF to get input on point 3 13:41:03 Question (2 of 4) Points 4 & 5: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-issue-4-resize-text/results#xq3 13:41:20 Google doc link: https://docs.google.com/document/d/1p5EX9d5Q9L1CghcECjPMVqIBxg4UJUZ5U3A3EZhNxUQ/edit#heading=h.djvhdqrcm8la 13:46:07 Current text in WCAG2ICT editor's draft on applying CSS pixels: https://w3c.github.io/wcag2ict/#applying-css-pixel-to-non-web-documents-and-software 13:46:48 NOTE 1 13:46:48 Non-web software and its accompanying platform software do not use CSS pixel measurements. Therefore, use platform-defined density-independent pixel measurements which approximate the CSS reference pixel. Examples of platform-defined density-independent pixel measurements include: points (pt) for iOS and macOS, density-independent pixels (dp) for 13:46:48 Android, and effective pixels (epx) for Windows. 13:46:48 NOTE 2 13:46:50 Examples where a density-independent pixel may not be defined in the platform: 13:46:50 Software designed for specific hardware, such as kiosks or office equipment, where the author knows the physical screen size and, potentially, the pixel density. 13:46:50 Software, such as streaming apps on smart TV platforms or similar software, where the author may lack information about the physical screen size but may know an appropriate viewing distance or viewing angle. 13:46:51 When there is no platform-defined density-independent pixel measurement, the reference pixel size can be approximated in the following manner: 13:46:51 Determine a viewing distance that matches the use case and display type. For instance, in the case of a touchscreen, the viewing distance is normally less than the length of an arm, typically around 28 inches (71 cm). 13:46:51 Calculate the size of the reference pixel: Divide the viewing distance by 2688. The number 2688 is obtained by dividing 28 inches (arm's length) by the derived reference pixel size (1/96 inch). 13:46:52 NOTE 3 13:46:52 Most software and devices are usable at more than one viewing distance. However, only viewing distances that are plausible for the product can be considered an appropriate approximation for the reference pixel. For example, in software designed for use with a touchscreen, a visual-angle pixel longer than 0.11 inch (0.28 mm) would not be plausible, 13:47:14 because this would signify a viewing distance of more than arm’s length. 13:47:14 NOTE 4 13:47:14 People with low vision often use devices at less than the standard viewing distance. However, basing the density-independent pixel on a typical viewing distance provides a balance of benefits for users with disabilities. If a longer viewing distance were chosen as the basis for the density-independent pixel, the viewport would be measured with a 13:47:15 smaller number of larger pixels, causing Success Criterion 1.4.10 Reflow to be less stringent. If a shorter viewing distance were chosen, user interface components would be measured with a larger number of smaller pixels, causing some success criteria, such as 2.5.8 Target Size, to be less stringent. 14:02:59 rrsagent, draft minutes 14:03:00 I have made the request to generate https://www.w3.org/2024/05/03-wcag2ict-minutes.html PhilDay 14:10:53 zakim, end meeting 14:10:53 As of this point the attendees have been Laura_Miller, PhilDay 14:10:54 RRSAgent, please draft minutes v2 14:10:56 I have made the request to generate https://www.w3.org/2024/05/03-wcag2ict-minutes.html Zakim 14:11:01 I am happy to have been of service, maryjom; please remember to excuse RRSAgent. Goodbye 14:11:03 Zakim has left #wcag2ict 14:11:07 rrsagent, bye 14:11:07 I see no action items