Re: Rough draft of some success criteria for a extension guideline "Touch accessible"

Patrick,
I like your insight. I personally have an hp Pavillion windows 10 inch
tablet that is a 2 in 1 and have added keyboard cases to my iPad mini and
Galaxy Note 4. Love them all. Keyboard interface is specifically required
for visually impaired users at all ranges of lose and important as many
other AT intersfaces emulate the keyboard signals. Touch is definately new
on the user interface scene and small touch sizes are everywhere. They need
a specific guideline. Try using touch on a 8 inch windows tablet along the
bottom Taskbar in desktop application. I can access them but not touch with
my finger. Even on my 10 inch windows tablet I've upped the text size to
150 percent and those are a little easier to touch but still I make
mistakes.  Mouse or cursor pad is needed. On my Galaxy Note 4 I use the
stylus all the time on Web browsers and native apps for check boxes and
radio buttons since their sizes are too tiny to get focus most of the time
with finger touch. Regards. Alan (losing sight, hearing and fine motor
control)
On Jul 27, 2015 3:50 PM, "Patrick H. Lauke" <redux@splintered.co.uk> wrote:

> Apologies for joining the party late and asking what is probably an
> obvious question, but just wanted to point out that "touch" is not strictly
> a "mobile" issue. There are already many devices (2-in-1 tablet/laptops,
> desktop machines with external touch-capable monitors, etc) beyond the
> mobile space which include touch interaction. So, a fundamental question
> for me would be: would these extensions be signposted/labelled as being
> "mobile-specific", or will they be added to WCAG 2 core in a more general,
> device-agnostic manner?
>
> Further, though I welcome the addition of SCs relating to touch target
> size and clearance, I'm wondering why we would not also have the equivalent
> for mouse or stylus interfaces...again, in short, why make it
> touch-specific, when in general the SCs should apply to all "pointers"
> ("mouse cursor, pen, touch (including multi-touch), or other pointing input
> device", to borrow some wording from the Pointer Events spec
> http://www.w3.org/TR/pointerevents/)?
>
> Perhaps more of an aside (apologies if this is the wrong forum to raise
> this): if I understand the idea of extensions correctly, the core WCAG 2
> SCs will remain unaffected. So does this mean that the keyboard-specific
> SCs will still be in effect, even though some devices may simply not have a
> keyboard? This feels like an imbalance...I'd rather see the core language
> made more input-agnostic in core WCAG 2 (e.g. replacing explicit mentions
> of "Keyboard" with something more open-ended, like "non-pointer interface"
> (see some of my musings from a while ago
> https://twitter.com/patrick_h_lauke/status/602414144583761920)
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>