RE: Responding to issue 4 for Resize Text

Thanks for adding the Friday comment<https://github.com/w3c/wcag2ict/issues/4#issuecomment-2183357940> and closing the issue. I want to make sure I understand this part of the comment (highlights mine):

> TF Answer to Point 3: For Non-Web Documents and Software, features including software provided by the platform <https://www.w3.org/TR/wcag2ict-22/#dfn-assistive-technology> that provide a means of enlarging the text 200% (zoom or otherwise) without the loss of content<https://w3c.github.io/wcag2ict/#content-on-and-off-the-web> or functionality, meet the intent of this success criteria.
> Platform accessibility features, including platform software that, when applied, causes loss of content, including a reduction in the ability to distinguish characters, would not meet this success criteria.
Does this mean the following? A screen magnifier built into the operating system meets the “without assistive technology” condition of SC 1.4.4. However, if a screen magnifier were the only resize mechanism for a software application, and it causes pixilation, then SC 1.4.4 could fail for “loss of content”.


Mitchell Evan (he/him)
Senior Accessibility Engineer

TPG Interactive
https://www.tpgi.com<https://www.tpgi.com/>

A Vispero Company
https://www.vispero.com<https://www.vispero.com/>

This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.

From: Mary Jo Mueller <maryjom@us.ibm.com>
Sent: Friday, June 21, 2024 11:29 PM
To: Mitchell Evan <mevan@tpgi.com>; public-wcag2ict-tf@w3.org
Subject: Re: Responding to issue 4 for Resize Text

CAUTION:EXTERNAL EMAIL SENDER!

Hi Mitch,

I noticed that Bruce also volunteered to post the response to Issue 4, so he and I got together today (21 June) and completed that task per the agreed text from the resolutions we had made on the responses. (Thanks Bruce!)

If there’s anything you’d like to add or edit, let me know and we can work on that.

Best regards,

Mary Jo Mueller
IBM Accessibility Standards Program Manager


From: Mitchell Evan <mevan@tpgi.com>
Date: Wednesday, June 19, 2024 at 10:19 AM
To: Mary Jo Mueller <maryjom@us.ibm.com>, public-wcag2ict-tf@w3.org <public-wcag2ict-tf@w3.org>
Subject: [EXTERNAL] Responding to issue 4 for Resize Text
Hi Mary Jo, On May 9 and May 16 we made some decisions about Resize Text, and I see them in our editor’s draft (looks good). Do we also need to turn these decisions into a response for issue 4? I might have time in the next few days to

Hi Mary Jo,

On May 9<https://www.w3.org/2024/05/09-wcag2ict-minutes> and May 16<https://www.w3.org/2024/05/16-wcag2ict-minutes> we made some decisions about Resize Text, and I see them in our editor’s draft<https://w3c.github.io/wcag2ict/#resize-text> (looks good). Do we also need to turn these decisions into a response for issue 4<https://github.com/w3c/wcag2ict/issues/4>? I might have time in the next few days to help with this, but let me know if a response is already in the works so I don’t duplicate the effort.

Thanks,
Mitchell

Mitchell Evan (he/him)
Senior Accessibility Engineer

TPG Interactive
https://www.tpgi.com<https://www.tpgi.com/>

A Vispero Company
https://www.vispero.com<https://www.vispero.com/>

This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful.