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

Your comments on WCAG 2.0 Public Working Draft of May, 2007

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Sat, 3 Nov 2007 21:59:01 -0700
Message-ID: <824e742c0711032159j3ea0856bo7350bd8e41ac333c@mail.gmail.com>
To: "Maciej Jaros" <egil@wp.pl>
Cc: public-comments-WCAG20@w3.org

Dear Maciej Jaros,

Thank you for your comments on the 17 May 2007 Public Working Draft of
the Web Content Accessibility Guidelines 2.0 (WCAG 2.0
http://www.w3.org/TR/2007/WD-WCAG20-20070517/). The WCAG Working Group
has reviewed all comments received on the May draft, and will be
publishing an updated Public Working Draft shortly. Before we do that,
we would like to know whether we have understood your comments
correctly, and also whether you are satisfied with our resolutions.

Please review our resolutions for the following comments, and reply to
us by 19 November 2007 at public-comments-wcag20@w3.org to say whether
you are satisfied. Note that this list is publicly archived. Note also
that we are not asking for new issues, nor for an updated review of
the entire document at this time.

Please see below for the text of comments that you submitted and our
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 WCAG 2.0 Editor's
Draft of May-October 2007 at
http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20071102/

Thank you for your time reviewing and sending comments. Though we
cannot always do exactly what each commenter requests, all of the
comments are valuable to the development of WCAG 2.0.

Regards,

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: Issues with example 1
Source: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0061.html
(Issue ID: 1979)
----------------------------
Original Comment:
----------------------------

This is about:
http://www.w3.org/TR/2007/WD-WCAG20-TECHS-20070517/#SCR21

In Example 1 the paragraph:
> Here is the script that adds the event handlers to the form. If
> scripting is enabled, the validateNumbers() function will be called to
> perform client-side validation before the form is submitted to the
> server. If scripting is not enabled, the form will be immediately
> submitted to the server and validation will occur on the server.
Should be:
> ...If scripting is not enabled, the form will be immediately submitted
> to the server and so the validation should also occur on the server.

This could be important as some beginners might thought that the code
given in the example would also validate the form on server side.


There are also some minor bugs in the code.

I've made the corrected version available here:
http://free.of.pl/n/nux/smp/WCGA_SCR21_ex1.html
The copy&paste version is here:
http://free.of.pl/n/nux/smp/WCGA_SCR21_ex1_pre.html

Summary of changes:
*1. At the end of validateNumbers add:*
   return true;
/[function should always return a value]/

*2. addError is:*
 function addError(strError, strFragment, objForm, strID)
 {
   var objAnchor = document.createElement('a');
   var objListItem = document.createElement('li');
   objAnchor.appendChild(document.createTextNode(strError));
   objAnchor.setAttribute('href', strFragment);
   objAnchor.onclick = function(event){return focusFormField(this,
event, objForm);};
   objAnchor.onkeypress = function(event){return focusFormField(this,
event, objForm);};
   // If strID has a value, this is the first error in the list
   if (strID.length > 0)
      objAnchor.setAttribute('id', strID);
      objListItem.appendChild(objAnchor);
      return objListItem;
   }
 }

*addError should be:*
function addError(strError, strFragment, objForm, strID)
{
   var objAnchor = document.createElement('a');
   var objListItem = document.createElement('li');
   objAnchor.appendChild(document.createTextNode(strError));
   objAnchor.setAttribute('href', strFragment);
   objAnchor.onclick = function(event){return focusFormField(this,
event, objForm);};
   objAnchor.onkeypress = function(event){return focusFormField(this,
event, objForm);};
   // If strID has a value, this is the first error in the list
   if (strID.length > 0)
      objAnchor.setAttribute('id', strID);
   objListItem.appendChild(objAnchor);
   return objListItem;
}

/[There is a syntax error near the if (strID.length > 0) in the original
code. I think I've fixed this correctly, but have a look at it]/

I've also changed some indenting, removed action from the form, and
changed HTML to be XHTML ready ;).

BTW, you could make all examples available on-line as they are in SVG specs.

Oh and I'm not sure what do you mean by this:
> Note that the sample form will not submit. This example only
> demonstrates the creation of error messages when client side
> validation fails.
As I see it - the form does got submitted - the values are send to the
server. So you should either clarify this note or always return false in
onsubmit. Not to mention that even if the validation function would
always return false, then with JavaScript disabled the form would still
get submitted.

---------------------------------------------
Response from Working Group:
---------------------------------------------

Thank you for pointing out the errors with example 1 in SCR21. We have
fixed the errors in the script, and amended the description
accordingly.

The action attribute is a required attribute, and must contain a valid
URI so that it works when scripting is not available, so we have left
that attribute with its value in the markup. In order to avoid
namespace scripting, we have left the markup example as HTML.
Received on Sunday, 4 November 2007 04:59:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:09 UTC