scanning, sip and puff, voice input don't act like actual keyboards...they do not send keystrokes. they can be used in concert with an on-screen keyboard, but on ios and android it is not generally possible to bring up the on-screen keyboard arbitrarily - it only appears when the user is on an element that allows key entry... (not to reiterate the lenghty thread from the mobile TF list) -- Patrick H. Lauke > On 20 Jul 2016, at 16:58, Gregg Vanderheiden <gregg@raisingthefloor.org> wrote: > > Please — the requirement is NOT that things work with a physical keyboard. Only the keyboard interface. This can be any keyboard installed on the phone itself — including scanning or sip and puff or voice input or…. (it CAN also be external— but only if that is what a person wants to use) > > gregg > >> On Jul 18, 2016, at 10:44 AM, Jonathan Avila <jon.avila@ssbbartgroup.com> wrote: >> >> Ø I don't see how I can ever fail someone on 1.4.2 anymore, thanks to James pointing this out. If we are looking to not cause SC bloat with the new SCs, perhaps we can make a new category for SCs which have been largely overcome by advances in User Agents etc... which still apply to 2.1 but are folded away somewhere so 2.1 is not bloated with SCs that developers don't need to worry about. >> >> I respectfully disagree with you David. Carrying around a physical keyboard with my iPhone so I can press control+M to mute audio is not acceptable. >> >> Jonathan >>
Received on Wednesday, 20 July 2016 17:57:12 UTC