WebAIM - Web Accessibility In Mind

E-mail List Archives

Implementing WCAG 2.0 (was: Scaleable fonts for Priority 2 WAI guidelines)

for

From: Christophe Strobbe
Date: May 15, 2008 2:50AM

Hi Steve,


At 16:39 14/05/2008, you wrote:
>WCAG 2.0 has not been officially released. It is merely a Candidate
>Recommendation, and won't become a Proposed Recommendation till 31 August
>2008. There will be a further delay before it reaches the final stage and
>becaomes a W3C Recommendation.
>
>In all probability it won't change much between now and then but it reached
>Candidate Recommendation status before about two years ago, after which it
>was substantially rewritten.

WCAG 2.0 has never been a Candidate Recommendation before April 2008.
What you are referring to is the last call working draft of April 2006:
<http://www.w3.org/TR/2006/WD-WCAG20-20060427/complete.html>;.
(There was another last call working draft in December 2007:
<http://www.w3.org/TR/2007/WD-WCAG20-20071211/>;. It is not unusual to
go through two last calls; the process has become much heavier since
WCAG 1.0 was released in 1999.)


>By all means learn about WCAG 2.0 but it's premature to be talking about
>implementing it.

On the contrary. Candidate Recommendation is a call for implementations.
See <http://www.w3.org/WAI/WCAG20/CR/>;.
Implementations are needed WCAG 2.0 to move to Proposed Recommendation;
it needs to be shown that WCAG 2.0 can be implemented.
Stating that it is premature to implement WCAG 2.0 is a self-fulfilling
prophecy that hinders the progress of WCAG 2.0 to W3C Recommendation.

Best regards,

Christophe Strobbe


>Steve
>
>
>
>