W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2004

RE: The Problem with WCAG (was RE: CSS Techniques for WCAG 2.0)

From: Patrick Lauke <P.H.Lauke@salford.ac.uk>
Date: Thu, 19 Aug 2004 13:59:49 +0100
Message-ID: <3A1D23A330416E4FADC5B6C08CC252B90113BB7D@misnts16.mis.salford.ac.uk>
To: <w3c-wai-ig@w3.org>

> This is precisely the problem with WCAG, in any version. It is too
> ambiguous. If the guidelines were all clear, such as using ALT
> attributes, they would be more widely understood, accepted and
> practiced.

That can be done in the specific technique documents for HTML and CSS.
That level of detail should not creep into the main technology
agnostic WCAG document.

> It needs to get away from ludicrous requirements that require 
> content to
> be comprehensible -- because that's not a measurable guideline.
> Therefore it should simply be left up to the developer or 
> designer. Why
> does WCAG bother mentioning something like that at all? 

Because otherwise what you have is a document detailing purely
"technical accessibility", which can be quite far away from the
goal of real accessibility.

Patrick
________________________________
Patrick H. Lauke
Webmaster / University of Salford
http://www.salford.ac.uk
Received on Thursday, 19 August 2004 13:01:26 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 23:39:44 UTC