W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2000

Re: Conformance Claim and keyboard API support

From: Jon Gunderson <jongund@ux1.cso.uiuc.edu>
Date: Mon, 09 Oct 2000 08:03:20 -0500
Message-Id: <4.3.1.2.20001009075924.02cf77f8@staff.uiuc.edu>
To: Ian Jacobs <ij@w3.org>
Cc: w3c-wai-ua@w3.org
Ian,
I think my new wording states your conditions better than the previous 
statement. I think the previous statement is ambiguous on what happens if 
"unless the operating system does not offer one" clause.  My new statement 
says "If an operating system or user agent does not offer or support a 
keyboard API, then the user agent cannot conform to these guidelines."  It 
could be their own keyboard API through an infrared link to a Kiosk, but 
they still must offer the keyboard API.

Jon


At 06:32 AM 10/7/2000 -0400, Ian Jacobs wrote:
>Jon Gunderson wrote:
> >
> > Since the group has required support for a keyboard API, I don't think the
> > we should allow any type of conformance if a user agent cannot support a
> > keyboard API.  The group could address this issue in a future version of
> > the document.
> >
> > Currently the conformance section makes the following statement:
> > "Checkpoints that refer to the keyboard always apply. The subject must
> > implement the standard API for the keyboard unless the operating system
> > does not offer one."
> >
> > I think we should state:
> > "Checkpoints that refer to the keyboard always apply. The subject must
> > implement the standard keyboard API.  If an operating system or user agent
> > does not offer or support a keyboard API, then the user agent cannot
> > conform to these guidelines."
>
>1) The UA is required (in all cases) to implement a keyboard API (no
>conformance
>possible without this).
>
>2) The UA is required to implement the standard system API for the
>keyboard if
>one exists.
>
>I think we shouldn't say "On that particular operating system, you can't
>have any user agents at all that conform to UAAG 1.0 since there is no
>standard API
>for the keyboard." It does make it harder on AT developers to
>communicate since
>they don't have a standard to follow, but it is possible to have
>combinations of software
>that work together. For that reason -- it's not absolutely impossible --
>I think that
>conformance should be possible in case 2.
>
>  - Ian
>
>
>--
>Ian Jacobs (jacobs@w3.org)   http://www.w3.org/People/Jacobs
>Tel:                         +1 831 457-2842
>Cell:                        +1 917 450-8783

Jon Gunderson, Ph.D., ATP
Coordinator of Assistive Communication and Information Technology
Division of Rehabilitation - Education Services
MC-574
College of Applied Life Studies
University of Illinois at Urbana/Champaign
1207 S. Oak Street, Champaign, IL  61820

Voice: (217) 244-5870
Fax: (217) 333-0248

E-mail: jongund@uiuc.edu

WWW: http://www.staff.uiuc.edu/~jongund
WWW: http://www.w3.org/wai/ua
Received on Monday, 9 October 2000 09:03:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:50:22 GMT