- From: Noah Blon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2016 02:14:36 +0000
- To: public-css-archive@w3.org
I agree @AmeliaBR. We do have the wonderful clip technique. However, we are currently in limbo with clip, considering that [it has been deprecated](https://developer.mozilla.org/en-US/docs/Web/CSS/clip) and Edge hasn't yet [picked up support for clip-path](https://developer.microsoft.com/en-us/microsoft-edge/platform/status/masks/). In my opinion this is reason alone to move away from "hacks" towards a standard method of dealing with a very common need. In regards to focusable elements within visually hidden elements, my understanding of the [Focus Visible Success Criterion of WCAG 2.0](https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-focus-visible.html) says that an element must be visible when focused. When focused, and in this particular use case, such as for skip links, I would expect the browser to give the element a display, such as block or flex. If the developer needs to disable keyboards from focusing the elements, they should disable tabbing to the focusable elements. -- GitHub Notification of comment by noahblon Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/560#issuecomment-252793482 using your GitHub account
Received on Tuesday, 11 October 2016 02:14:50 UTC