Re: 2.1.1 Keyboard

Andi, gang,

I'm curious about how these concepts & language would apply to iOS.  It 
is possible to attach an external, wireless keyboard to iOS devices.  
But the resulting "keyboard interface" used doesn't provide for certain 
types of navigation (e.g. TAB for moving focus).  The built in VoiceOver 
screen reader does provide for such navigation, but not when done from a 
standard keyboard (though I believe object navigation is supported from 
a connected Braille display using the keys on that display).

Regards,

Peter

On 6/14/2012 3:21 PM, Andi Snow-Weaver wrote:
>
> Please see Proposal #3 for 2.1.1 Keyboard [1].
>
> I'm hoping this gets us past our logjam on "keyboard interface". The 
> SC doesn't actually say the keyboard interface has to be supported 
> directly by the software. It just says the functionality has to be 
> operable via the keyboard interface.
>
> As long as platform software device independent services layer has 
> sufficient support such that when a keyboard is attached, AT software 
> can utilize the services to operate an application via the keyboard, 
> then applications that support operation via the device independent 
> services can in fact be operated via a "keyboard interface". The note 
> is intended to clarify this scenario.
>
> [1] 
> https://sites.google.com/site/wcag2ict/home/2-operable/21-make-all-functionality-available-from-a-keyboard/211-keyboard
>
> Andi
>

-- 
Oracle <http://www.oracle.com>
Peter Korn | Accessibility Principal
Phone: +1 650 5069522 <tel:+1%20650%205069522>
500 Oracle Parkway | Redwood City, CA 94065
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to 
developing practices and products that help protect the environment