WebAIM - Web Accessibility In Mind

E-mail List Archives

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

for

From: Christophe Strobbe
Date: May 15, 2008 10:20AM

Hi Steve,

At 17:38 15/05/2008, you wrote:
>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.

Thank you for that clarification.
However, Mike Cherim has already implemented WCAG 2.0 on a website for
an external client: see <http://green-beast.com/blog/?p=221>;.


>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.

Indeed, implememtation evidence is not optional but *required* in order
to exit the CR stage:
the exit criteria require at least 10 conforming websites
(more details at <http://www.w3.org/TR/2008/CR-WCAG20-20080430/#status_exit>;).

>If there is no possibility of change,
>what would be the purpose of those extra stages?

Some success criteria have been defined as being "at risk"; see
<http://www.w3.org/TR/2008/CR-WCAG20-20080430/#status_risk>;.
Depending on implementation feedback, some success criteria may
become less restrictive, revert to an earlier version, or
become advisory (i.e. they would become advisory techniques
instead of success critera).

In the past, some candicate recommendations have been pushed back
to the working draft stage. For example, CSS 2.1 was a candidate
recommendation in February 2004
<http://www.w3.org/TR/2004/CR-CSS21-20040225/>;,
went back to working draft in 2005
<http://www.w3.org/TR/2005/WD-CSS21-20050613/>;,
and is now again a candidate recommendation:
<http://www.w3.org/TR/2007/CR-CSS21-20070719/>;.

Best regards,

Christophe


>Steve
>
>
>
>