W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > May 2007

Your comments on WCAG 2.0 Last Call Draft of April 2006

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Thu, 17 May 2007 16:29:36 -0700
Message-ID: <824e742c0705171629t4674c528x2c69851867c04386@mail.gmail.com>
To: "Csaba Gabor" <csaba@alum.mit.edu>
Cc: public-comments-WCAG20@w3.org

Dear Csaba Gabor ,

Thank you for your comments on the 2006 Last Call Working Draft of the
Web Content Accessibility Guidelines 2.0 (WCAG 2.0
http://www.w3.org/TR/2006/WD-WCAG20-20060427/). We appreciate the
interest that you have taken in these guidelines.

We apologize for the delay in getting back to you. We received many
constructive comments, and sometimes addressing one issue would cause
us to revise wording covered by an earlier issue. We therefore waited
until all comments had been addressed before responding to commenters.

This message contains the comments you submitted and the resolutions
to your comments. Each comment includes a link to the archived copy of
your original comment on
http://lists.w3.org/Archives/Public/public-comments-wcag20/, and may
also include links to the relevant changes in the updated WCAG 2.0
Public Working Draft at http://www.w3.org/TR/2007/WD-WCAG20-20070517/.

PLEASE REVIEW the decisions  for the following comments and reply to
us by 7 June at public-comments-WCAG20@w3.org to say whether you are
satisfied with the decision taken. Note that this list is publicly

We also welcome your comments on the rest of the updated WCAG 2.0
Public Working Draft by 29 June 2007. We have revised the guidelines
and the accompanying documents substantially. A detailed summary of
issues, revisions, and rationales for changes is at
http://www.w3.org/WAI/GL/2007/05/change-summary.html . Please see
http://www.w3.org/WAI/ for more information about the current review.

Thank you,

Loretta Guarino Reid, WCAG WG Co-Chair
Gregg Vanderheiden, WCAG WG Co-Chair
Michael Cooper, WCAG WG Staff Contact

On behalf of the WCAG Working Group

Comment 1:

Source: http://www.w3.org/mid/20060512200803.0E5BA47BA5@mojo.w3.org
(Issue ID: LC-467)

Item Number: Make all functionality operable via a keyboard interface
Part of Item:
Comment Type: GE
Comment (Including rationale for any proposed change):
A few years back I tried to pay my Sprint account online and found
that even though I could submit a payment form via an image, the
payment was not accepted because the x and y coordinates which are
automatically submitted with the image (and are 0 in the case of a
keyboard click) were both 0.  This was bad programming on their part,
but the point is:

If an element has focus where a mouse click would take an action that
takes the mouse location into account, then using the arrow keys at
that point (or some other keyboard means) should allow the user to set
the mouse position that will be used upon keyboard simulated clicking
(such as using the spacebar) of the element.

This example may be too specific for this document, but I thought I'd
mention it as a concrete case that really troubled me.

Csaba Gabor from Vienna

Proposed Change:

Response from Working Group:

Thank you for your note.  You will be happy to know that Guideline 2.1
and SC 2.1.1 of WCAG 2.0 require that all functionality of content be
operable from the keyboard interface (unless the underlying function
requires input that depends on the path of the user's movement and not
just the endpoints - which yours doesn't). So the Web page you
describe would not pass WCAG 2.0 even at the basic level of
Received on Thursday, 17 May 2007 23:29:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:43 UTC