RE: CFC - Add "Pointer target spacing" to WCAG 2.2 draft

+1 to David’s recommendation.

Jonathan

From: David MacDonald <david100@sympatico.ca>
Sent: Wednesday, July 22, 2020 4:25 PM
To: Chuck Adams <charles.adams@oracle.com>
Cc: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: Re: CFC - Add "Pointer target spacing" to WCAG 2.2 draft

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi All
I think it's fine for public review... but there is something that seems inconsistent... The basic requirement is for a 44px square area which includes the target.  But the first bullet exception says that there is a mechanism to set the target to 44 px not the aria that includes the target

CURRENT TEXT OF THE BULLET
Enlarge: A mechanism is available to change the CSS pixel size of all targets so that the width and height are each at least 44 CSS pixels;

I think that first bullet should instead say that the mechanism can produce the basic requirement which is a 44px area that CONTAINS the content rather than the target is IS 44px

SUGGESTED TEXT
Enlarge: A mechanism is available to provide, for each target, an area with a width and height of at least 44 CSS pixels that includes it, and no other active targets;


Cheers,
David MacDonald



CanAdapt Solutions Inc.

Tel:  613-806-9005

LinkedIn
<http://www.linkedin.com/in/davidmacdonald100>

twitter.com/davidmacd<http://twitter.com/davidmacd>

GitHub<https://github.com/DavidMacDonald>

www.Can-Adapt.com<http://www.can-adapt.com/>



  Adapting the web to all users
            Including those with disabilities

If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html>


On Mon, Jul 20, 2020 at 12:33 PM Chuck Adams <charles.adams@oracle.com<mailto:charles.adams@oracle.com>> wrote:
Hi everyone,



As we have received only positive feedback leading up to this CfC and no responses indicating that group members could not live with this decision, this CfC is agreed on as a consensus opinion of the working group.



This decision will be recorded at https://www.w3.org/WAI/GL/wiki/Decisions<https://urldefense.com/v3/__https:/www.w3.org/WAI/GL/wiki/Decisions__;!!GqivPVa7Brio!PAfe-XrsFxUH4dZL_FX19s4zZzyQOuZYCKyCtr86gjdjeTZC-aJbQHTdG80jEJPvhw$>

Kind regards,
Charles Adams

From: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Sent: Wednesday, July 15, 2020 5:29 PM
To: WCAG list (w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>) <w3c-wai-gl@w3.org<mailto:w3c-wai-gl@w3.org>>
Subject: CFC - Add "Pointer target spacing" to WCAG 2.2 draft
Importance: High


Call For Consensus — ends Monday 20th  July at midday Boston time.



The Working Group has discussed adding “Pointer Target Spacing” to the WCAG 2.2 draft:

https://www.w3.org/2020/04/14-ag-minutes.html#item05<https://urldefense.com/v3/__https:/www.w3.org/2020/04/14-ag-minutes.html*item05__;Iw!!GqivPVa7Brio!Kj4CYuv10KtafXYD_wSpfWoMgLWdI4M1az8uypM8Gn-N0TN9dssLp3H_T--aTWSN_w$>

And some more recent updates:

https://www.w3.org/2020/07/14-ag-minutes.html#item02<https://urldefense.com/v3/__https:/www.w3.org/2020/07/14-ag-minutes.html*item02__;Iw!!GqivPVa7Brio!Kj4CYuv10KtafXYD_wSpfWoMgLWdI4M1az8uypM8Gn-N0TN9dssLp3H_T-_NLIRm3w$>



The specific changes (including rendered SC and understanding doc) are detailed in this pull request:

https://github.com/w3c/wcag/pull/1179<https://urldefense.com/v3/__https:/github.com/w3c/wcag/pull/1179__;!!GqivPVa7Brio!Kj4CYuv10KtafXYD_wSpfWoMgLWdI4M1az8uypM8Gn-N0TN9dssLp3H_T-9BCuPxlA$>



If you have concerns about this proposed consensus position that have not been discussed already and feel that those concerns result in you “not being able to live with” this decision, please let the group know before the CfC deadline.

Kind regards,

-Alastair

--

www.nomensa.com<https://urldefense.com/v3/__http:/www.nomensa.com/__;!!GqivPVa7Brio!Kj4CYuv10KtafXYD_wSpfWoMgLWdI4M1az8uypM8Gn-N0TN9dssLp3H_T-8M2WnqdA$> / @alastc