Re: CfC - Add Focus Visible (Enhanced) to WCAG 2.2 draft

Hi Jonathan,

I know that but it's a bit of another issue.

See the next two images:

[cid:d18b7c8c-5efb-4e53-abbd-e1b7c7655bc4]
AND...
[cid:b527cb35-9de5-48d1-9eaa-1135b84cd4d5]

For the first one, the indicator is a pass / OK
For the second one I made the buttons just a bit bigger (wider) for increased touch target, but now the indicator fails!

ALSO

When this indicator (the yellow square) is fine for indication, WHY would it not be for other UICs (if the size of the UIC is bigger than for the Example buttons in Alastair's example)

We want the focus indicator to be 'seen' and if the square is enough to be seen, the size of the UIC shouldn't matter anymore for this SC.
________________________________
From: Jonathan Avila <jon.avila@levelaccess.com>
Sent: Tuesday, December 10, 2019 1:25 PM
To: Abma, J.D. (Jake) <Jake.Abma@ing.com>
Cc: Alastair Campbell <acampbell@nomensa.com>; Patrick H. Lauke <redux@splintered.co.uk>; w3c-wai-gl@w3.org <w3c-wai-gl@w3.org>
Subject: Re: CfC - Add Focus Visible (Enhanced) to WCAG 2.2 draft

Jake, I think the minimum area here is not of the button or control but the focus indicator which may be smaller than the longest side.   So if you had a focus indicator on the shorter side that was just a vertical line it would have to be thicker.  That is my understanding.

Jonathan

Sent from my iPhone

On Dec 10, 2019, at 5:37 AM, Abma, J.D. (Jake) <Jake.Abma@ing.com> wrote:


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.


coming back on this CfC and my last comment: my biggest question would be WHY a focus indicator MUST be bigger than others (based on touch target)?

It just doesn't make sense if we compare them to other UICs and their indicator:

------------------------------

IF a focus indicator is enough, wouldn't this be enough in other cases too on the same page?

SO, shouldn't a clear focus indicator not be enough to be based on a specific size (as we have for AAA touch target)?

A clear focus indicator is a clear focus indicator, no matter how big the target area is.
________________________________
From: Alastair Campbell <acampbell@nomensa.com>
Sent: Tuesday, December 10, 2019 10:21 AM
To: Patrick H. Lauke <redux@splintered.co.uk>; w3c-wai-gl@w3.org <w3c-wai-gl@w3.org>
Subject: Re: CfC - Add Focus Visible (Enhanced) to WCAG 2.2 draft

>  doesn't the "or" clause then simply allow absolutely faint contrast
> ratio to be used, as long as the thickness is 2 CSS pixels?

All bullets have to be true, so this is in combination with the 2nd.
(https://raw.githack.com/w3c/wcag/wcag22-focus-visible-enhanced/understanding/22/focus-visible-enhanced.html )

I.e. the change of contrast has to be there (2nd bullet). *Then* it has to contrast with its adjacent colors *or* be thicker.

>    I'm assuming this is supposedly then covered by the following note

No, the note is for the 2nd bullet, although it hasn't changed since the third was added. Perhaps we need to make the note more specifically for the 2nd bullet then?

"E.g. Note: A focus indicator that is larger than the minimum area may have parts that do not meet the 3:1 focus contrast requirement, as long as an area equal to the minimum does meet the contrast ratio."

-Alastair


-----------------------------------------------------------------
ATTENTION:
The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.
-----------------------------------------------------------------

-----------------------------------------------------------------
ATTENTION:
The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.
-----------------------------------------------------------------

Received on Tuesday, 10 December 2019 12:34:16 UTC