Sure some thoughts be sure that the final language does not provide alternatives to the keyboard interface requirement unless whatever else is allowed can be used by people who cannot do gestures including swipes. If it comes out “keyboard interface access AND something" — then it should be a separate SC. It would be two requirements. if it is “keyboard interface OR something — then something has to have all the characteristics of the keyboard interface (an actual single testable thing authors can do that will will still allow users to drive it with many different types of input including voice, keyboards, gestures, sip and puff, etc. I don’t see how the "sequential input” language will do that — but I will wait to see what comes out. best gregg > On Jul 1, 2016, at 10:54 AM, Patrick H. Lauke <redux@splintered.co.uk> wrote: > > On 01/07/2016 15:00, Gregg Vanderheiden RTF wrote: >> can you define what you mean by >> >> Sequential access mechanisms ? > > It's a mechanism that allows for the user to navigate sequentially https://www.w3.org/TR/WCAG20/#nav-seqdef (but that is currently defined by referencing "keyboard interface", which has the narrow definition using "keystroke" in it). > > And can I ask that I be given a bit of time to formulate what I have in mind, before the idea itself is critiqued without even seeing exactly what I'm proposing? > > 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
Received on Friday, 1 July 2016 15:56:47 UTC