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

Re: Techniques for 3.3.6 Orientation to Frames

From: mark novak <menovak@facstaff.wisc.edu>
Date: Fri, 8 Oct 1999 09:58:40 -0500
Message-Id: <v01540b06b423ae78e2a8@[]>
To: schwer@us.ibm.com
Cc: w3c-wai-ua@w3.org
>After reading checkpoints 1.1 and 1.6, I feel the clarity problem is due to a
>of definitions. Too much is left up to the assumption of the reader. So, my
>proposal 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.

MN:  Perhaps maybe more of a cautionary note on how we word this....I had
to read this a couple of times before I realized we had shifted from graphical
desktop user agents to palm and voice based browsing.  I agree with pushing
the guidelines in that direction, but perhaps some rephrasing?

<this isn't the best wording, but I hope I'm getting the idea across, if
we want to as a group, cross into this territory ?>

For example, today's graphical desktop user agents running on personal computer
operating systems expect to use the keyboard and mouse as the standard
input mechanism, and a video display as the standard output mechanism.  However,
small hand-held palm computers may replace the keyboard and mouse with
their standard input devices being a stylus and perhaps some dedicated
buttons, and their
standard output device being a significantly more limited video display.

The expectations for future phone and mobile-based user agents, suggest that
the standard input device would be voice, while the standard output device
will be
limited video and or video/audio combination or only audio.

>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
Received on Friday, 8 October 1999 11:03:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:38:23 UTC