-
Notifications
You must be signed in to change notification settings - Fork 257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Technique - ensuring single pointer usage #380
Conversation
Alastair, thanks for putting this together. The text seems to indicate that drag and drop must have an equivalent yet in other threads I thought we agreed that drag and drop did not need an alternative? What is our position? this technique should match. Single is misspelled as "signle" in the test section. |
"assistive technologies" is plural so changed an "is" to "are". Removed the first example, which simply re-stated the SC text.
Hi Jon, -Alastair |
Need to revisit with #403 resolution in mind |
I've removed the direct drag & drop references, and added the common example I come across (carousels), diff of updates. (And moved the AT paragraph into the description so it doesn't get removed by the build process.) However, from experience with other techniques this seems like a 'test the SC' sort of thing, rather than a specific technique. Should this be converted to something like: "Adding buttons so that path-based gestures are not relied on"? It is a little vague at the moment, that might help make it a specific techinque. |
Also removed ‘on touch devices’, not necessary.
Replaced single pointer with "simple click or tap"
I think this one got combined with #760 and was approved today, so closing this. (Unless @detlevhfischer thinks otherwise?) |
GitHub says there's another open PR that depends on the |
Initial creation of the technique, comment on this pull request, and preview on rawgit.com.