W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > July 2010

Re: G192: Example

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Thu, 29 Jul 2010 18:01:32 -0700
Message-ID: <AANLkTi=3QdVg9tzV+5uzFPE89FKFH=8MG4M56TWar-YO@mail.gmail.com>
To: makoto.ueki@gmail.com
Cc: public-comments-wcag20@w3.org
On Thu, Jul 22, 2010 at 7:18 PM,  <makoto.ueki@gmail.com> wrote:
> Name: Makoto Ueki
> Email: makoto.ueki@gmail.com
> Affiliation: Infoaxia, Inc.
> Document: TD
> Item Number: G192
> Part of Item: Examples
> Comment Type: general comment
> Summary of Issue: G192: Example
> Comment (Including rationale for any proposed change):
> It reads "Specification requirements that can not be identified by validation are also checked and any failures are corrected."
> Need more concrete description and examples for "Specification requirements that can not be identified by validation". We couldn't understand what this means.
> Proposed Change:
> Add reason and/or description and examples why only validating web pages would not be sufficient for fully conforming to specifications.
Response from the Working Group
Specifications include requirements that cannot be machine checked.
For instance, in the HTML 4.0 specification, the description of the
alt attribute at
includes not specifying meaningless alternate text. However, there is
no way for a validator to determine whether the description is

Similarly, the specification for the title attribute at
http://www.w3.org/TR/html401/struct/global.html#title says that the
attribute offers advisory information about the element for which it
is set. There is no way to validate whether the title information is

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 Friday, 30 July 2010 01:02:01 UTC

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