- From: Kun Zhang <kunzhang@w3.org>
- Date: Mon, 13 Apr 2015 22:25:13 +0800
- To: Andrew Kirkpatrick <akirkpat@adobe.com>, "WCAG (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
- Message-ID: <552BD1C9.5060503@w3.org>
If "Keyboard" control is very important for Touchscreen Devices, it should have a clear definition, imagine touchscreen device is ATM, watch, GPS, this is not always make sense in general keyboard definition. - Kenny Zhang 在 2015/4/10 0:51, Andrew Kirkpatrick 写道: > > *3.1 Keyboard Control for Touchscreen Devices* > > * Ensuring keyboard control for all functionality > * Ensuring touch access control for all functionality > * Ensuring that users are not trapped in content (using touch and > keyboard) > * Defining the hover, focus, selected and touch (regular, long) states > o Use focus, hover and select states consistently and in a way > that follows the respective platform conventions > > Questions: > > 1)Does each technique make sense to you? (for now these are just > titles, so it can be a challenge to be certain) > > 2)Do you agree that the referenced success criteria is applicable to > each suggested technique, or that the technique is applicable to the SC)? > > 3)Do you think that there is another technique that this might better > be an example for instead of a technique on its own? > > 4)Do you think that each is likely to be sufficient or advisory? > > 5)Are there other techniques that you can think of that address the SC > in the mobile space? > > Thanks, > > AWK > > Andrew Kirkpatrick > > Group Product Manager, Accessibility > > Adobe Systems > > akirkpat@adobe.com <mailto:akirkpatrick@adobe.com> > > http://twitter.com/awkawk > > http://blogs.adobe.com/accessibility >
Received on Monday, 13 April 2015 14:25:23 UTC