W3C

– DRAFT –
WCAG2ICT Task Force Extra Friday Teleconference

03 May 2024

Attendees

Present
Laura_Miller, PhilDay
Regrets
-
Chair
Mary Jo Mueller
Scribe
PhilDay

Meeting minutes

Survey on answers to public comments

<maryjom> https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results

<maryjom> Start with Question 4: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq4

<maryjom> Google doc: https://docs.google.com/document/d/1TbtNcNjrpog8-6OYloMcPILh2UsqUOXBjPwVwv7dPsw/edit#heading=h.rdnzztss5c30

present

<Chuck> +1 to include Mitch's response

<maryjom> Question 5: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq5

Google doc on issue 257: https://docs.google.com/document/d/1TbtNcNjrpog8-6OYloMcPILh2UsqUOXBjPwVwv7dPsw/edit#heading=h.rdnzztss5c30

<maryjom> Mitch's additional text was added to the Google doc with a comment to highlight it.

<maryjom> Question 6: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq6

<maryjom> Proposed answer to Issue 221...

<Chuck> +1 to plopping!

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

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.

<maryjom> Question 7: SC Problematic for Closed FUnctinoality - SC 1.4.10 Reflow

<maryjom> https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq7

<maryjom> Google doc link: https://docs.google.com/document/d/1TbtNcNjrpog8-6OYloMcPILh2UsqUOXBjPwVwv7dPsw/edit#heading=h.ynsr98668tn5

Go with options 0 & 2 and resurvey TF

<maryjom> Question 8: Review: Proposed updates to Status of this Document

<maryjom> https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-miscellaneous2/results#xq8

<Laura_Miller> +1 to phil's solution

Second survey on Issue 4

<maryjom> Question (1 of 4) Point 3: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-issue-4-resize-text/results#xq2

<maryjom> https://docs.google.com/document/d/1p5EX9d5Q9L1CghcECjPMVqIBxg4UJUZ5U3A3EZhNxUQ/edit#heading=h.tqu8jju9a2a9

Response to w3c/wcag2ict#4

Remove option 2, just survey options 1 and 3 with the wider TF to get input on point 3

<maryjom> Question (2 of 4) Points 4 & 5: https://www.w3.org/2002/09/wbs/55145/WCAG2ICT-issue-4-resize-text/results#xq3

<maryjom> Google doc link: https://docs.google.com/document/d/1p5EX9d5Q9L1CghcECjPMVqIBxg4UJUZ5U3A3EZhNxUQ/edit#heading=h.djvhdqrcm8la

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

NOTE 1

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

Android, and effective pixels (epx) for Windows.

NOTE 2

Examples where a density-independent pixel may not be defined in the platform:

Software designed for specific hardware, such as kiosks or office equipment, where the author knows the physical screen size and, potentially, the pixel density.

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.

When there is no platform-defined density-independent pixel measurement, the reference pixel size can be approximated in the following manner:

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).

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).

NOTE 3

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,

because this would signify a viewing distance of more than arm’s length.

NOTE 4

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

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.

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

No scribenick or scribe found. Guessed: PhilDay

Active on IRC: Chuck, Laura_Miller, maryjom, PhilDay