W3C home > Mailing lists > Public > public-wcag2ict-tf@w3.org > June 2012

Re: 2.1.1 Keyboard

From: Andi Snow-Weaver <andisnow@us.ibm.com>
Date: Thu, 14 Jun 2012 18:13:56 -0500
To: Peter Korn <peter.korn@oracle.com>
Cc: public-wcag2ict-tf@w3.org
Message-ID: <OF9232B778.C37F6DC3-ON86257A1D.007EC5ED-86257A1D.007F9E81@us.ibm.com>

Hi Peter,

I think we should refrain from mentioning specific products unless they are
our own.

It doesn't work today and so it wouldn't conform. And I don't think it
should conform because it supports only blind users, not all users with
disabilities. But if the platform implements a sufficient device
independent layer to enable keyboard operation of apps that support the
layer, then that should conform.

Andi



From:	Peter Korn <peter.korn@oracle.com>
To:	Andi Snow-Weaver/Austin/IBM@IBMUS
Cc:	public-wcag2ict-tf@w3.org
Date:	06/14/2012 05:39 PM
Subject:	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
Peter Korn | Accessibility Principal
Phone: +1 650 5069522
500 Oracle Parkway | Redwood City, CA 94065
Green
          OracleOracle is committed to developing practices and
products that help protect the environment



graycol.gif
(image/gif attachment: graycol.gif)

2B564039.gif
(image/gif attachment: 2B564039.gif)

2B262835.gif
(image/gif attachment: 2B262835.gif)

Received on Thursday, 14 June 2012 23:14:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 14 June 2012 23:14:45 GMT