Re: Pre-CFC - Focus Appearance and Target Size

Also, if I can be so bold to add some context: if the target size SC 
gets changed to the circle approach, I've been working on an 
understanding update to then go with this - 
https://github.com/w3c/wcag/pull/3103 (see the rendered preview at 
https://raw.githack.com/w3c/wcag/patrickhlauke-target-size-minimum-issue3089-companion/understanding/22/target-size-minimum.html) 
... this may help in grokking the nuances/changes that come with this 
new spacing approach.

--
Patrick H. Lauke

https://www.splintered.co.uk/ / https://github.com/patrickhlauke / 
https://codepen.io/patrickhlauke
https://flickr.com/photos/redux/ / https://www.deviantart.com/redux
https://mastodon.social/@patrick_h_lauke


------ Original Message ------
From "Alastair Campbell" <acampbell@nomensa.com>
To "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
Date 20/04/2023 14:51:24
Subject Pre-CFC - Focus Appearance and Target Size

>Hi everyone,
>
>
>
>This is a pre-CFC for the changes to Focus Appearance and Target Size.
>
>
>
>We reviewed these in the last meeting, the PR is:
>
>https://github.com/w3c/wcag/pull/3123/files
>
>
>
>Since the meeting, changes include:
>
>Adjusting the example in the definition of perimeter to 2 CSS pixels. 
>(It doesn’t affect the core meaning; it is helpful for people doing 
>calculations for focus-appearance). Linking the target-size SC to 
>minimum bounding box.
>
>
>Reviewing it further, the definition for min-bounding box appears (to 
>me) to work for both target-size and focus-appearance.
>
>
>
>The second sentence about wrapping targets should not apply to target 
>size because, by the definition of target, it is “a region” rather than 
>multiple regions.
>
>It should also not come up due to the inline exception.
>
>
>
>Any concerns?
>
>
>
>Kind regards,
>
>
>
>-Alastair
>

Received on Thursday, 20 April 2023 14:54:07 UTC