WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: WCAG 2.0 Last Call

for

From: Gez Lemon
Date: May 2, 2006 5:00AM

On 02/05/06, Patrick H. Lauke < <EMAIL REMOVED> > wrote:
> Now, if I
> went over to a complete accessibility noob with a complete printout of
> WCAG 2.0 and its supporting documents, they'd be very unlikely to work
> their way through those 600 odd pages. Just look at the length of
> "Understanding WCAG 2.0".

WCAG 2 itself is about 76 printed pages. Some of the supporting
documents, such as Understanding WCAG, are informative to provide
guidance. I don't think that causes an implementation issue - if
anything, I think it makes it easier as guidance for implementing WCAG
2 can be found in one place.

> I suspect that one of the first things to do once WCAG 2.0 is finalised
> will be the creation of technology (and baseline) specific
> implementation guides (at least that's what I plan to do at work for our
> developers...something like "How can my HTML/CSS site meet WCAG 2.0", as
> our baseline will probably just feature those two technologies).

Yeah, I agree. I also think the checklist in Appendix B [1] will be
useful for people to get a quick overview of the guidelines and
success criteria. Regarding the baseline - this is more of a device
independence issue than an accessibility issue, but I would encourage
early adopters not to include CSS in the baseline. Meeting WCAG 2
without depending on CSS would be more beneficial for universality,
but relying on CSS for conformance will obviously be acceptable under
WCAG 2.

[1] http://www.w3.org/TR/2006/WD-WCAG20-20060427/appendixB.html

Best regards,

Gez

--
_____________________________
Supplement your vitamins
http://juicystudio.com