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

Action Item Proposal: Rewording of Checkpoints 1.1 and 1.6

From: <schwer@us.ibm.com>
Date: Mon, 11 Oct 1999 13:16:43 -0500
To: ij@w3.org, w3c-wai-ua@w3.org
Message-ID: <85256807.006C9DB5.00@d54mta08.raleigh.ibm.com>



After reading checkpoints 1.1 and 1.6, the clarity problem is due to a lack
of definitions. Too much is left up to the assumption of the reader. So, my
suggestion is to make the following four changes:

1. Modify the glossary definition of device independence.

Device Independence The ability to make use of software via any input or
output device supported by the operating system. These supported devices
consist of standard input and output devices.

User agents should follow system conventions and use standard APIs for
device input and output.

2. Create and add the following glossary definition:

Standard Input and Output Devices: These devices are those which are
expected for normal use by the operating system and its standard user
interface. Operating systems provide standard API to these devices to be
used by applications for expected inter operability between the operating
system and the application environment.

For example, today's personal computer desktop operating systems expect to
use mouse and keyboard devices as the standard input mechanism. For a palm
computer the standard input may be the stylus and buttons. The expected,
standard output on these systems consists of the display and/or an audio
output device.

3. Modify Checkpoint 1.1

1.1     Ensure that all functionality offered through the user interface
may be operated through standard input device APIs supported by the
operating system. [Priority 1] Standard input device APIs are those used by
the operating system to support the use of expected, <A Link to Standard
Input and Output Devices Definition>standard input and output devices</a>.

4. Modify Checkpoint 1.6

1.6 Ensure that all messages to the user (e.g., warnings, errors, etc.) are
available through standard output device APIs supported by the operating
system. [Priority 1] Standard output device APIs are those used by the
operating system to support the use of expected, <A Link to Standard Input
and Output Devices Definition>standard input and output devices</a>.

For instance, ensure that information about how much of a page or video
clip has been viewed is available through output device APIs. Proportional
navigation bars may provide this information visually, but the information
must be available to users relying on synthesized speech or braille output.


Rich Schwerdtfeger
Lead Architect, IBM Special Needs Systems
EMail/web: schwer@us.ibm.com http://www.austin.ibm.com/sns/rich.htm

"Two roads diverged in a wood, and I -
I took the one less traveled by, and that has made all the difference.", Frost
Received on Monday, 11 October 1999 15:46:40 GMT

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