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:36:45 -0700
Message-ID: <824e742c0705171636j6e5e5252wa2adbd6950f3e8a3@mail.gmail.com>
To: "Jim Allan" <jimallan@tsbvi.edu>
Cc: public-comments-WCAG20@w3.org

Dear Jim Allan ,

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/HDEAKIPKOHBCMDILOOPNMEKDGBAB.allanj@tsbvi.edu
(Issue ID: LC-755)

Comment (including rationale for any proposed change):

SC 3.2.2 Changing the setting of any form control or field does not
automatically cause a change of context (beyond moving to the next
field in tab order) unless the authored unit contains instructions
before the control that describe the behavior.

This is the only SC with a parenthetical clause (beyond moving to the
next field in tab order). UAWG believes the clause violates user
expectations of form control behavior.

Further, the clause violates UAAG Checkpoint 9.3 Move content focus
(P1) http://www.w3.org/TR/2002/REC-UAAG10-20021217/guidelines.html#tech-nav-active

Techniques for checkpoint 9.3

1. Allow the user to move the content focus to any enabled element in
the viewport.
2. Allow configuration so that the content focus of a viewport only
changes on explicit user request.
3. If the author has not specified a navigation order, allow at least
forward sequential navigation, in document order, to each element in
the set established by provision one of this checkpoint.

Sufficient techniques

1. To satisfy provision two of this checkpoint, configuration is
preferred, but is not required if the content focus only ever changes
on explicit user request.

Default behavior is for content focus only ever changes on explicit
user request.

Proposed Change:

remove the clause (beyond moving to the next field in tab order)

Response from Working Group:

We have accepted your recommendation and removed the parenthetical
clause. Note that auto-advance-focus can be an important accessibility
aid for the mobility impaired, so it is still permitted, but only if
the user has been warned about it as they would be if configured their
user agent for this behavior.

Comment 2:

Source: http://www.w3.org/mid/HDEAKIPKOHBCMDILOOPNCENDGBAB.allanj@tsbvi.edu
(Issue ID: LC-756)

Comment (including rationale for any proposed change):

there is a need for more descriptive adjectives and phrases that put
the  responsibility of conformance with WCAG on the Web author (and
not the user agent) by using valid accessibility features from their
chosen baseline

Proposed Change:

new definition: determined from Web author-supplied data provided in a
user-agent-supported manner, such as valid element tags and
attributes, such that the user agents can extract and present this
information to users in different modalities.

Response from Working Group:

We have reworded the definition of programmatically determined to
clarify that the data is provided by the author.
Received on Thursday, 17 May 2007 23:36:52 UTC

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