W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2011

Re: WCAG 2 conformance claim: validating code

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Wed, 23 Mar 2011 09:25:00 -0700
Message-ID: <AANLkTinGr5gomg=8AjMwR1V9tvPLdehnvXEgBRoPmLsn@mail.gmail.com>
To: Sailesh Panchang <spanchang02@yahoo.com>
Cc: w3c-wai-gl@w3.org
On Fri, Sep 24, 2010 at 11:45 AM, Sailesh Panchang <spanchang02@yahoo.com>wrote:

> Hello WCAG-WG,
> SC 4.1.1 requires limited validity checks for markup: unique ID values,
> proper tag nesting and closing and a check for duplicate attributes.
> However, the WCAG 2 Understanding documentat suggests that conformance
>  claim could include something along the lines of:
> "The documented set of accessibility-supported content technologies relied
> upon for this claim includes XHTML 1.0 (Transitional), CSS 2  and
>  JavaScript 1.2. "
> Refer: example conformance claims on
> http://www.w3.org/TR/UNDERSTANDING-WCAG20/conformance.html#uc-conformance-requirements-head
> Does this imply that one can make such a statement only after ensuring that
> markup / CSS / JS code is valid?
> Please clarify whether validating the code for CSS / JS / XHTML beyond what
> is suggested in SC 4.1.1 is  required for a conformance claim if for
> instance, all three technologies are used.
> Thanks,
> Sailesh Panchang (MS, ASQ-CSQE)
> Web Accessibility Lead
> www.deque.com
> ================================
Response from the Working Group
No, this just says that you depend on those technologies in making your
claim.  That just tells the user that if they use a browser that doesn’t
support JS or CSS the page might not be accessible. In the spirit of success
criterion 4.1.1, any modifications made to the DOM should also preserve
these same properties, e.g., elements properly nested, no duplicate IDs,

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
Received on Wednesday, 23 March 2011 16:25:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 16 January 2018 15:34:07 UTC