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

RE: implementation report for guideline 1:

From: Jim Allan <allanj@tsbvi.edu>
Date: Thu, 02 Nov 2000 10:53:37 -0600
To: David Poehlman <david.h.poehlman@verizon.net>, User Agent Working group list <w3c-wai-ua@w3.org>
Message-id: <NBBBIBAJLBJPFGFFMBMEEEAFEHAA.allanj@tsbvi.edu>
hi David,
I have some concerns about 1.1. there are several things that one can do
with a mouse that are not possible from the keyboard in IE.
for example: saving a picture on a web page - with a mouse you click on the
picture then bring up the context menu and a host of commands are
available--these are not available to a keyboard interface without much
work. (yes, you can get the url from the source, then go to the specific
image and save it--tedious at best), another example is controlling an svg
image--I have played with the adobe svg plug in, many features are available
with the mouse (resizing, searching for text, etc.). these functions are not
available via the keyboard because you cannot get to the object on the web
page (the svg is not an active element.)

I think I have the intent of 1.1 correct.

Jim Allan, Statewide Technical Support Specialist
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9453  http://www.tsbvi.edu/
"Be BOLD and mighty forces will come to your aid." Basil King

-----Original Message-----
From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org]On
Behalf Of David Poehlman
Sent: Thursday, November 02, 2000 9:18 AM
To: User Agent Working group list
Subject: implementation report for guideline 1:

Here is my best shot at taking on guideline 1.

   1.1 Ensure that every functionality available through the user
          interface is also available through every input API that is
          implemented by the user agent. This checkpoint does not
          developers to reimplement the input methods associated with
          keyboard, pointing device, voice, and other input APIs.
          [Priority 1]
MicroSoft Internet Explorer5.5 and MicroSoft Office2,000 provide this
   1.2 Use the standard input and output APIs of the operating system.
          not bypass the standard output APIs when rendering
          [Priority 1]
   1.3 Implement the operating system's standard API for the keyboard
          ensure that every functionality available through the user
          interface is available through this API. [Priority 1]
   1.4 Ensure that the user can interact with all active elements in a
          device-independent manner. [Priority 1]
   1.5 Ensure that every message (e.g., prompt, alert, notification,
          etc.) that is a non-text element and is part of the user
          user interface has a text equivalent. [Priority 1]
Hands-On Technolog(eye)s
touching the internet
voice: 301.949.7599
---end sig---
Received on Thursday, 2 November 2000 11:52:57 UTC

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