W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2003

Re: WCAG1.0 Checkpoint 10.5 - still valid?

From: Dave Shea <dave@mezzoblue.com>
Date: Tue, 09 Dec 2003 13:12:15 -0600
To: w3c-wai-gl@w3.org
Message-Id: <E1ATnHL-0006rn-8f@socrates.scdns.net>

> Currently, you "fail" triple-A, but this is a bug in the whole
> WCAG 1.0 process to begin with.  There is method by which any
> particular person or group was authorized to say that the "Until
> user agents..." clauses have been met.  The page author is not
> allowed to claim these clauses are fulfilled, and the working
> group has not claimed that function either.

Where is it stated that a page author isn't allowed to make the claim?
I'd be interested in reading up on that. Or is that the bug in this
case, that the door is open for page authors to make that determination?

> It is for this reason that the "Until user agents..." clauses are
> so disliked and opposed by many, including myself.  The plans for
> WCAG 2.0 have long been to totally eliminate any such requirements
> that are tied to a specific date in time with no way of certifying
> that the conditions have been universally met.

Completely unrelated to the issue at hand, but since you've got me
curious - will there be checks in place to make sure obsolete guidelines
don't live past their expiry date?

> This is just one of many reasons to consider WCAG 1.0 triple-A to
> be effectively unreachable; there's little reason to pursue that as
> a goal, and instead the goal should be to pursue increased
> accessibility and usability for people with disabilities.

But isn't that the entire point of WCAG 1.0 in the first place? I can
understand deviation between what was, 5 years ago, and what is, in late
2003. But until WCAG2.0 is released, what else can the average developer
be expected to use as a framework for accessibility?

d.
Received on Tuesday, 9 December 2003 14:13:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:26 GMT