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

Re: Action Item: Techniques for guideline 1.

From: Bryan Campbell <bryany@pathcom.com>
Date: Thu, 18 Nov 1999 09:22:55 -0500
Message-Id: <2.2.32.19991118142255.00683a18@mail.pathcom.com>
To: w3c-wai-ua@w3.org
11:28 AM 17-11-99 -0600, Rich Schwerdtfeger <schwer@us.ibm.com> wrote:
>Here they are:
>1.1 Ensure that every functionality offered through the user interface is
[snip]
>   Techniques:
[snip]
[Point 3]
>    If you implement an interface where the user selects text then issues
>a command related to it (e.g., select text then create a link using the
>selected text as content), all operations related to the selection and
>operation on the selected text must be done in a device independent way. In
>the case of a desktop user agent this means that the user must be able to
>perform these tasks using the keyboard and mouse independently.

Hi,
For clarity the last line of the above should read:
"perform these tasks using either keyboard or mouse."

Meaning either can do all functions

[snip]
>   1.3 Ensure that the user can interact with all active elements in a
>   device-independent manner. [Priority 1]

>   For example, users who are blind or have motor impairments must be able
>   to activate the links in a client-side image map without a pointing
>   device. One technique for doing so is to render client-side image maps
>   as text links. Note. This checkpoint is an important special case of
>   checkpoint 1.1.

"Motor impairments" aptly describes the results of many physical
disabilities. Yet the phrase is unlikely to mean much to most programmers.
Somewhere on the Guildlines page 2 or 3 lines should outline how "motor
impairments" or physical disability relates to computer usage: Lack of or
little manual dexterity; increased tendency to push unwanted 
button (say elevator) or key; muscular degeneration means decreased mobility
even in hand movements. Those factors came to mind just as examples to start
from. Similar tiny briefs should be given for other impairments as is
needed. Giving program designers some idea why things are required will
enable them to produce better & perhaps new solutions! Giving background
makes them more like partners in making the Web usable for everyone & the
Guildlines less of another task list to get done.

Regards,
Bryan

->"It has been said the pebbles can't stop the avalanche, guess the pebbles
didn't have access to the Web!"
Received on Thursday, 18 November 1999 09:24:32 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:25 UTC