W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2019

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

From: Abma, J.D. (Jake) <Jake.Abma@ing.com>
Date: Tue, 17 Dec 2019 15:51:53 +0000
To: Alastair Campbell <acampbell@nomensa.com>, WCAG list <w3c-wai-gl@w3.org>
Message-ID: <AM6PR03MB4454BAAFF4555D6C6640F5FEF1500@AM6PR03MB4454.eurprd03.prod.outlook.com>
Hi Alastair,

It all depends... 🙂

The SC works fine UNLESS in certain examples, like the ones you provide with border left and square (and some more) AND with bigger area's where the logic is just not there.

Of course I understand your comments that you CAN do it differently but this is not how the world always designs / works / wants.

So, IF the SC is to make focus clearly visible (and I'm all in for that one) than the way it's demanding the visual space right now doesn't take into account other scenario's than the perfect ones provided. Clearly visible is clearly visible, failing because you make the touch target bigger while the focus is already clearly visible is not thought through all the way.

I can do a plea for the reason why, even provide examples, but I think more people need to see what I mean and not just say +1 to fast without realizing what the consequences are.

But I will not want to stop a nice proceeding of a good new SC.

Cheers,
Jake

________________________________
From: Alastair Campbell <acampbell@nomensa.com>
Sent: Tuesday, December 17, 2019 3:21 PM
To: Abma, J.D. (Jake) <Jake.Abma@ing.com>
Subject: Re: CfC - Add Focus Visible (Enhanced) to WCAG 2.2 draft


Hi Jake,



Is this a -1 to publishing the SC as part of the FPWD?



Not sure we got to the bottom of your issue, but is it a blocker?



-Alastair





From: "Abma, J.D. (Jake)" <Jake.Abma@ing.com>
Date: Tuesday, 10 December 2019 at 10:36
To: Alastair Campbell <acampbell@nomensa.com>, Patrick Lauke <redux@splintered.co.uk>, WCAG list <w3c-wai-gl@w3.org>
Subject: Re: CfC - Add Focus Visible (Enhanced) to WCAG 2.2 draft





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, 17 December 2019 15:52:06 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:32 UTC