Skip to content
This repository has been archived by the owner on Mar 13, 2018. It is now read-only.

Enable tap from some keyboard buttons #44

Open
dfreedm opened this issue Aug 12, 2014 · 6 comments
Open

Enable tap from some keyboard buttons #44

dfreedm opened this issue Aug 12, 2014 · 6 comments
Assignees

Comments

@dfreedm
Copy link
Contributor

dfreedm commented Aug 12, 2014

Need to support a few keyboard buttons on a few elements to allow tap to be a full fidelity click replacement:

spacebar (on non input elements)
enter (on non input elements)
up/down (radio buttons)
?
Related to Polymer/polymer#255

@dfreedm dfreedm self-assigned this Aug 12, 2014
@dfreedm
Copy link
Contributor Author

dfreedm commented Aug 12, 2014

Ported from googlearchive/PointerGestures#12

@dfreedm dfreedm closed this as completed Aug 12, 2014
@dfreedm dfreedm reopened this Aug 12, 2014
@plato-cambrian
Copy link

+1

@kbwatts
Copy link

kbwatts commented Feb 17, 2015

+1

@kbwatts
Copy link

kbwatts commented Feb 17, 2015

The fact that on-tap ruins accessibility for keyboard users is actually a pretty serious issue. Built-in accessibility is one of the huge selling points for using the Polymer framework (among many other inspiring selling points). Correct me if I'm wrong, but as I understand it, on-tap is meant to be the "Finally, one-solution-to-rule-them-all" bridge between on-click and touch events, agnostic to whatever device or platform it happens to find itself on. If it breaks accessibility, then it renders the whole point of itself useless and as a result we're now going back to on-click events, which sucks when you know a far better solution is sitting right there, just beyond reach.

Please, don't let on-tap's lack of keyboard accessibility be a barrier to what helps Polymer become The Next Big Thing.

@dfreedm
Copy link
Contributor Author

dfreedm commented Feb 17, 2015

The next version (0.8+) of polymer-gestures will use click to fire tap instead of mousedown/mouseup pairs, which I believe will achieve what you're looking for.

In the meantime, the core-a11y-keys element provides keyboard driven callbacks for this use case, as well as more advanced use cases such as radio buttons, sliders, etc.

@kbwatts
Copy link

kbwatts commented Feb 17, 2015

That's exactly what I was hoping for - thanks for your quick reply. We'll do our best for now until 0.8 :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants