- From: Joe Watkins via GitHub <sysbot+gh@w3.org>
- Date: Fri, 07 Feb 2020 15:51:00 +0000
- To: public-css-archive@w3.org
joe-watkins has just created a new issue for https://github.com/w3c/csswg-drafts: == Consideration of keyup event for Polyfill instead of keydown == > In the polyfill, keydown event and mouseup event are used for the spatial navigation. I'm curious to see if there is a great case for leveraging a `keydown` event as apposed to a `keyup` event. Keyboard users who may have mobility/dexterity type disabilities that could benefit from an event that they have more control over the timing of it being fired. e.g. someone with tremors using a keyboard. WCAG 2.1 A 2.5.2 Pointer Cancellation currently speaks to this concept for touch/mouse. (should clearly extend to keyboard events IMO) https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/#252-pointer-cancellation-a Browser manufacturers may be looking to the polyfill for guidance and I was interested in seeing if maybe a `keyup` event could be the default vs requiring an override. https://wicg.github.io/spatial-navigation/#handling-browser-events Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4758 using your GitHub account
Received on Friday, 7 February 2020 15:51:02 UTC