W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2002

Re: Comment: Checkpoint 1.1

From: David Poehlman <poehlman1@comcast.net>
Date: Wed, 10 Jul 2002 13:59:11 -0400
To: David Poehlman <poehlman1@comcast.net>, Jon Gunderson <jongund@uiuc.edu>, "Ian B. Jacobs" <ij@w3.org>
Cc: w3c-wai-ua@w3.org
Message-id: <01a101c2283b$7f21ac90$19e03244@DAVIDPOEHLMAN>

sorry, rong message.

----- Original Message -----
From: "David Poehlman" <poehlman1@comcast.net>
To: "Jon Gunderson" <jongund@uiuc.edu>; "Ian B. Jacobs" <ij@w3.org>
Cc: <w3c-wai-ua@w3.org>
Sent: Wednesday, July 10, 2002 1:42 PM
Subject: Re: Comment: Checkpoint 1.1



trouble with any embedded sound is it is inaccessible to a large
population without sound cards or the appropriate platform no matter
what audio format you use.  Trouble with real audio is that it is not
available to all platforms and even on those that it is available for,
requires additional software/plug in.  best audio is .wav or other
native formats since they require only the existing built in processors.

----- Original Message -----
From: "Jon Gunderson" <jongund@uiuc.edu>
To: "Ian B. Jacobs" <ij@w3.org>
Cc: <w3c-wai-ua@w3.org>
Sent: Wednesday, July 10, 2002 1:39 PM
Subject: Re: Comment: Checkpoint 1.1



Ian,
Suggested change:

Note: User agents should support at least two types of keyboard access
to
functionalities: direct and sequential access (where user awareness of a
location "in space" is not required, as is the case with keyboard
shortcuts
and navigation of user agent menus).  Spatial keyboard access (where the
user moves the pointing device "in space" via the keyboard) is required
for
functionalities that cannot be made available by direct or sequential
access.  For example, when the position "in space" is an important part
of
the functionality (i.e. a program to manipulate a bit-mapped image).  In
most cases the direct and sequential access techniques will be redundant
with spatial techniques associated with a pointing device.  Furthermore,
the user agent should satisfy this requirement by offering a combination
of
keyboard-operable user interface controls (e.g., keyboard operable print
menus and settings) and direct keyboard operation of user agent
functionalities (e.g., a short cut to print the current page). As
examples
of functionalities, ensure that the user can interact with enabled
elements, select content, navigate viewports, configure the user agent,
access documentation, install the user agent, operate controls of the
user
interface, etc., all entirely through keyboard input. It is also
possible
to claim conformance to this document for full support through pointing
device input and voice input. See the section on Input modality labels.

Jon


At 12:38 PM 7/10/2002 -0400, Ian B. Jacobs wrote:
>Jon Gunderson wrote:
>>Ian,
>>The note on checkpoint 1.1 makes it sound like mouse keys can be used
to
>>conform to the keyboard input requirement.  We don't want to imply
>>that.  I think it should be clearer that user agents need to be
>>compatible with mouse keys, but that supporting mousekeys does not
>>satisfy the conformance requirements for checkpoint 1.1 for keyboard
access.
>
>The UAWG resolved that it would not impose that all keyboard
>access be through direct access. Therefore, 1.1 allows a mix
>of:
>
>  1) Direct access (e.g., "F1" pulls up help)
>  2) Sequential access that is not through two-dimensional
>     space (e.g., navigation through cascading menus)
>  3) Spatial access (e.g., for drawing functionalities).
>
>Later in the document we have single-key requirements for
>some functionalities. But for the rest, we do not require
>that access be available through just one of the
>above three modes. Consequently, it is my understanding
>that we agreed that mouse keys was far from ideal for
>satisfying this checkpoint, but for some input (e.g.,
>drawing), it would be better than actually moving a mouse
>around a desktop).
>
>Are you suggesting that mouse keys would *never* be
>acceptable as part of satisfying 1.1? I think that's different
>from our resolution. The Note reads:
>
>"User agents should allow direct keyboard access where possible, and
this
>may be redundant with spatial input techniques. Furthermore, the user
>agent should satisfy this requirement by offering a combination of
>keyboard-operable user interface controls (e.g., keyboard operable
print
>menus and settings) and direct keyboard operation of user agent
>functionalities (e.g., a short cut to print the current page)."
>
>Do you have other text to propose?
>
>_ Ian
>
>
>[1] http://www.w3.org/WAI/UA/2001/08/issues-20010830#514
>
>--
>Ian Jacobs (ij@w3.org)   http://www.w3.org/People/Jacobs
>Tel:                     +1 718 260-9447

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 Wednesday, 10 July 2002 14:00:10 GMT

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