RE: EOWG work this week on WCAG 2.0

Hi All,

Some initial thoughts

2. Understanding WCAG 2.0
* http://www.w3.org/TR/UNDERSTANDING-WCAG20/
* Title of document: 
 - Clarifying potential concerns with title, and ways to mitigate them

I agree that the title is a bit misleading or rather doesn't quite
clearly state what the document is in relation to the others. The
document is more of a guide/manual on how to apply WCAG2, essential
supporting information for applying the guidelines. As I think Wayne put
it giving it a title along the lines of "A guide to WCAG 2" (possibly
too easy to confuse with "guidelines") or "How to apply WCAG2",
"Applying WCAG2", "How to use WCAG2", "Using WCAG2" may be more useful.

3. Checklist for WCAG 2.0 / Appendix B: Checklist (Non-Normative)
* http://www.w3.org/TR/2006/WD-WCAG20-20060427/appendixB.html
Focusing on:
- Presentation, including grouping and color
- Introduction: Does it place the document well within the context of
the other documents?

With regard to the colour scheme I found it a useful additional way of
indicating Levels. What wasn't quite clear was why the colours changed
when I moused over them (perhaps I'm missing something here). I'm also
wondering if there needs to be a legend or explanation of the colours at
the top or whether that would be overkill. 

The checkboxes are useful for indicating if you have met a success
criterion but for some reason I kept on wanting to find a submit button
and have the page return results of how far I had met various levels! It
seems odd to have form elements that are not part of an interactive
form. Perhaps expanding on the explanation of the purpose of the
checkboxes in the introduction ("It lists all of the success criteria
from WCAG 2.0 in a checkable list") would be useful.

Finally I think the overall principle titles should be added in-between
the 4 guideline sections i.e.

   1. Content must be perceivable
   2. Interface elements in the content must be operable
   3. Content and controls must be understandable
   4. Content should be robust enough to work with current and future
Web technologies

Without them is seems strange to go from 1.4 to 2.1 (for
example)...you're left wondering "Where's 2?"

Thanks, Henny

Received on Thursday, 11 May 2006 09:44:20 UTC