Re: Focus appearance updates

I think it is shorter without part 1, and we can demo a fully enclosed with a nice technique.

The lift to something as big as a 2px perimeter addresses some of the findings from Google, and as a AAA, I think it’s reasonable to seek that.

I do wonder if we can remove the “or is no thinner than 2 CSS pixels” from the final bullet?

Google’s research suggested that lacking the contrast made it more difficult to locate the indicator, especially when there was not neighbouring components to assess what can amount to just a smallish size difference. If we’re at AAA, I think we can make the bar a bit higher and insist on the contrast with adjacent non-focus indicator.

Those are shopping list items for me. I can abide your proposal, but I do think we can be a bit pickier.
Mike




From: Alastair Campbell <acampbell@nomensa.com>
Date: Tuesday, March 21, 2023 at 9:54 AM
To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: [EXTERNAL] Focus appearance updates
Hi everyone, Based on the survey and the call today, we agreed to move Focus Appearance to AAA. If we can make some further modifications, we should work out what those are. It isn’t clear what would count as ‘substantive’, as we are creating
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Hi everyone,

Based on the survey and the call today, we agreed to move Focus Appearance to AAA.

If we can make some further modifications, we should work out what those are.

It isn’t clear what would count as ‘substantive’, as we are creating requirements rather than features. Moved to AAA we have reduced the requirement in practice.

Another fairly straightforward change would be to remove the ‘part 1’ of the SC. That would at least make it smaller, if not simpler. It would not affect conformance, as anything that passes part 1 would pass part 2.

I can see two other changes that could be appropriate at AAA.

  1.  Simplify the ‘size’ bullet, e.g. remove the 4 times shortest side measure.
  2.  Increase the size requirement to 2 CSS pixel thick perimeter.

All of those together would leave us with:

When the keyboard focus indicator<https://www.w3.org/TR/WCAG22/#dfn-focus-indicator> is visible, an area of the focus indicator meets all the following:
·         is at least as large as the area of a 2 CSS pixel<https://www.w3.org/TR/WCAG22/#dfn-css-pixels> thick perimeter<https://www.w3.org/TR/WCAG22/#dfn-perimeter> of the unfocused component or sub-component, and
·         has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states, and
·         has a contrast ratio of at least 3:1 against adjacent non-focus-indicator colors, or is no thinner than 2 CSS pixels.
(Plus the exceptions.)

Does anyone have a different approach to this, or would like to make a case for retaining the 4 x shortest side metric?

I think the overall impact, for those aiming for AAA, would be a stronger push toward outlines, and thicker outlines as well.

Kind regards,

-Alastair

--

@alastc / www.nomensa.com<http://www.nomensa.com>