WebAIM - Web Accessibility In Mind

E-mail List Archives

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


From: Steve Green
Date: May 15, 2008 9:50AM

Perhaps I should have caveated that comment. Yes, if you're designing
websites for your own use or for your employer, then by all means implement
WCAG 2.0 now on the understanding that you may need to do some rework later.

If you're designing for external clients I don't think it's appropriate to
be working to guidelines that have not yet reached W3C Recommendation
status. I assume that the process of attaining Proposed Recommendation and
W3C Recommendation is not just a rubber stamp job and that there is
therefore the possibility of change. If there is no possibility of change,
what would be the purpose of those extra stages?


-----Original Message-----
[mailto: <EMAIL REMOVED> ] On Behalf Of Christophe
Sent: 15 May 2008 09:47
To: WebAIM Discussion List
Subject: [WebAIM] Implementing WCAG 2.0 (was: Scaleable fonts for Priority 2
WAI guidelines)

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:
(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

>-----Original Message-----
>[mailto: <EMAIL REMOVED> ] On Behalf Of Paul Collins
>Sent: 14 May 2008 15:19
>To: WebAIM Discussion List
>Subject: Re: [WebAIM] Scaleable fonts for Priority 2 WAI guidelines
>Thanks Rahul, that is a big help. I was refering to WCAG 1.0, I just
>realised WCAG 2.0 has been officially released! You could still use
>sIFR for
>1.4.5 thought, right? Just that you have the option to use images as well.
>Better start learning the new rules then...
>Thanks again for your help.

Please don't invite me to LinkedIn, Facebook, Quechup or other "social
networks". You may have agreed to their "privacy policy", but I haven't.

Christophe Strobbe
K.U.Leuven - Dept. of Electrical Engineering - SCD Research Group on
Document Architectures Kasteelpark Arenberg 10 bus 2442
B-3001 Leuven-Heverlee
tel: +32 16 32 85 51

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm