Re: Should we require all functionality to be operable with pointer?

> On Jul 4, 2016, at 3:12 PM, Patrick H. Lauke <redux@splintered.co.uk> wrote: 
> Can this be handled through "a mechanism is available" language? 

That sounds promising.  
hmmm

remember the keyboards  on many mobile are partial keyboards— (except for connected keyboards)  

What exactly is being required of the AUTHOR? 


gregg

> On Jul 4, 2016, at 3:12 PM, Patrick H. Lauke <redux@splintered.co.uk> wrote:
> 
> On 04/07/2016 18:27, Gregg Vanderheiden wrote:
>> Grin
>> 
>> that would require that all content have an on-screen keyboard.
>> 
>> the only way for an author to ensure that everything I operable with
>> only a pointer — would be for them to include and on-screen keyboard on
>> every page that has text input — unless we are going to declare that
>> there is no platform anywhere that does not include an on-screen
>> keyboard.      Might be true - don’t know.
> 
> Can this be handled through "a mechanism is available" language? On Mac, Windows, Linux, Android, iOS, Windows Phone/10 Mobile, etc there are standard on-screen keyboards, meaning an author would not need to take care of this themselves. In closed/specific environments like point-of-sale/ATM scenarios, the authors would need to provide an on-screen keyboard (or ensure that middleware that does handle this is present/installed).
> 
>> But remember what you are asking of an AUTHOR   when you require
>> something be there that not all platforms may have.
>> 
>> Maybe a page that runs on a browser with voice for input?   and no on
>> screen keyboard?      If there is one — then an AUTHOR needs to detect
>> it and make all pages have an on screen keyboard as part of the page.
>> 
>> that kind of thing.
>> 
>> tricky bit
>> 
>> /gregg/
> 
> 
> -- 
> 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