WCAG 2.2 Focus Not Obscured (Minimum + Enhanced)

  *   failing things that can be dismissed with a single action feels unreasonable to me

A cookie notice may be dismissible with a single action by a pointer user -  but a keyboard only user may need to navigate many items with the keyboard before locating the control to dismiss – this includes navigating to content hidden behind it where there is limited or no visibility to where the keyboard indicator is. So unfortunately, for keyboard-only folks it’s not a single action and it’s much more complex.

Jonathan

From: Wilco Fiers <wilco.fiers@deque.com>
Sent: Monday, July 18, 2022 6:11 AM
To: Michael Gower <michael.gower@ca.ibm.com>
Cc: Alastair Campbell <acampbell@nomensa.com>; WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: Re: CFC - WCAG 2.2 Focus Not Obscured (Minimum + Enhanced)

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.

Hey Mike,
While I'm all on board with doing something about sticky headers/footers, failing things that can be dismissed with a single action feels unreasonable to me. I realize I'm too late to adjust my vote here, so I'm going to raise an issue for this instead. I feel this should've been more explicitly mentioned in the understanding documents. If we're going to fail 95% of websites with cookie popups, we should be upfront about it.



On Sat, Jul 16, 2022 at 5:12 PM Michael Gower <michael.gower@ca.ibm.com<mailto:michael.gower@ca.ibm.com>> wrote:
BTW, I maybe should have stated clearly that in many of these implementations the keyboard user CANNOT get to the sticky footer to dismiss it until they have traversed the entire site, because it just continues to float elusively ahead of the currently obscured tab location. On even a medium sized page, it’s an exercise in frustration.

And of course there are some sites where the banner never IS in the tab order, just floating over all the content endlessly, simple to dismiss with a pointer, impossible with a keyboard. Those already fail 2.1.1, but the ones we’re discussing here, despite the enormous impact on sighted users who rely on the keyboard API, pass 2.1 (or rather, we couldn’t get agreement that they fail Focus Order). A prime motivator for this SC.

Thanks!
Mike

From: Michael Gower <michael.gower@ca.ibm.com<mailto:michael.gower@ca.ibm.com>>
Date: Saturday, July 16, 2022 at 7:51 AM
To: Wilco Fiers <wilco.fiers@deque.com<mailto:wilco.fiers@deque.com>>, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Cc: 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: [EXTERNAL] RE: CFC - WCAG 2.2 Focus Not Obscured (Minimum + Enhanced)
No, that’s the whole point of the requirement 😊 And those sticky footers that cropped up after Europe’s GDPR came into effect are some of the worst offenders. They are a nightmare to deal with as a keyboard user. ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
No, that’s the whole point of the requirement 😊 And those sticky footers that cropped up after Europe’s GDPR came into effect are some of the worst offenders. They are a nightmare to deal with as a keyboard user.

There are two easy ways those can be implemented that meet not obscured:

  *   Use scroll-padding to keep focus from being hidden behind it
  *   Make it a modal so it takes focus right away and folks have to dismiss it

There are other techniques, but those are two of the quickest ways of resolving so that keyboard users can use a site.

Mike
From: Wilco Fiers <wilco.fiers@deque.com<mailto:wilco.fiers@deque.com>>
Date: Saturday, July 16, 2022 at 4:23 AM
To: Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>>
Cc: 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: [EXTERNAL] Re: CFC - WCAG 2.2 Focus Not Obscured (Minimum + Enhanced)
Hey Alastair, I just spotted something that I dhttps://deque.com/on't<http://deque.com/on't> believe the group has discussed. Many websites these days have a cookie banner. These are pretty much always banners that are sticky at the bottom of the page, thus when
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Hey Alastair,
I just spotted something that I dhttps://deque.com/on't<http://deque.com/on't> believe the group has discussed. Many websites these days have a cookie banner. These are pretty much always banners that are sticky at the bottom of the page, thus when you tab through the page the focus indicator is almost inevitably obscured somewhere by that cookie banner until it is dismissed. Looking at a few random sites, it's almost hard to find sites that don't have this. Should the SC have an exception for when the obscuring content can be dismissed?


On Wed, Jul 13, 2022 at 4:18 PM Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
Call For Consensus — ends Monday July 18th at midday Boston time.

The Working Group has previously discussed the WCAG 2.2 SCs Focus Not Obscured (Minimum), Focus Not Obscured (Enhanced) and the Normative text needs to be approved by CFC.

It can be previewed in the editor’s draft:
https://w3c.github.io/wcag/guidelines/22/#focus-not-obscured-minimum

https://w3c.github.io/wcag/guidelines/22/#focus-not-obscured-enhanced


The SC has been discussed previously, Most recently:
https://www.w3.org/2022/05/24-ag-minutes#item07


The change history is here:
https://github.com/w3c/wcag/commits/main/guidelines/sc/22/focus-not-obscured.html

https://github.com/w3c/wcag/commits/main/guidelines/sc/22/focus-not-obscured-enhanced.html


The survey questions are available here:
https://www.w3.org/2002/09/wbs/35422/wcag22-focus-appearance-enhanced2/results


The github issues are listed here:
https://github.com/w3c/wcag/issues?q=is%3Aissue+is%3Aopen+focus+obscured

(There are several open related to an understanding content updates.)

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
--

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



--
Wilco Fiers
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator ACT Task Force



--
Wilco Fiers
Axe-core & Axe-linter product owner - WCAG 3 Project Manager - Facilitator ACT Task Force
[cid:BCBD7D4B-677E-4B95-AE3F-60005DBD9EE4]