- From: Andi Snow-Weaver <andisnow@us.ibm.com>
- Date: Fri, 15 Jun 2012 08:33:18 -0500
- To: Loïc Martínez Normand <loic@fi.upm.es>
- Cc: public-wcag2ict-tf@w3.org
- Message-ID: <OF5ED01BF1.208EEC75-ON86257A1E.004A6D0C-86257A1E.004A75BB@us.ibm.com>
Modified the note per Loïc's suggestion. Andi From: Loïc Martínez Normand <loic@fi.upm.es> To: Andi Snow-Weaver/Austin/IBM@IBMUS Cc: public-wcag2ict-tf@w3.org Date: 06/15/2012 03:07 AM Subject: Re: 2.1.1 Keyboard Hi everyone, I'm OK with Andi's proposal. Just a minor change in the words. Instead of "device independent services" I'd rather have "device independent input services" to clarify. Best regards, Loïc On Fri, Jun 15, 2012 at 12:21 AM, Andi Snow-Weaver <andisnow@us.ibm.com> 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 -- --------------------------------------------------------------- Loïc Martínez-Normand DLSIIS. Facultad de Informática Universidad Politécnica de Madrid Campus de Montegancedo 28660 Boadilla del Monte Madrid --------------------------------------------------------------- e-mail: loic@fi.upm.es tfno: +34 91 336 74 11 ---------------------------------------------------------------
Attachments
- image/gif attachment: graycol.gif
Received on Friday, 15 June 2012 13:33:59 UTC