Re: Updated draft WCAG 2.0 documents for review

Under "Who WCAG is for" perhaps include User Agent Developers along with
Authoring Tool Developers?

Under "what is in" consider bolding "testable" since it's central to the new
image of WCAG in version 2?

Also might de-emphasize HTML by saying "technical" or "markup"? One reason
for 2.0 is that 1.0 was so HTML-centric.

"The best place to start working with WCAG 2.0 How to Meet WCAG 2.0 (Quick
Reference). For more details on how these document related" doesn't "scan" -
[perhaps this is an editorial comment?] A colon after the first "2.0"?

"how these documents are related"? Under "WCAG Versions: 1.0 and 2.0"
there's a superfluous "is" in the second sentence


On Mon, Nov 17, 2008 at 3:13 PM, Shawn Henry <shawn@w3.org> wrote:

>
> EOWG,
>
> Two draft documents are updated based on input from last week's
> teleconference:
> * Web Content Accessibility Guidelines (WCAG) Overview <
> http://www.w3.org/WAI/intro/wcag-new.html>
> * How WCAG 2.0 Differs from WCAG 1.0 <
> http://www.w3.org/WAI/EO/Drafts/transition1to2/20differs10>
>
> More pages will be available later this week, and I will indicate when they
> are ready for review in:
> * WCAG Pages New and Updated for December 2008 <
> http://www.w3.org/WAI/EO/Drafts/transition1to2/newdocs>.
>
> Please review the updated drafts and be prepared to discuss them in this
> week's teleconference. Feel free to send comments to the list before the
> meeting. Note that we probably will not discuss them again before they are
> published.
>
> Regards,
> ~Shawn
>
>
> -----
> Shawn Lawton Henry
> W3C Web Accessibility Initiative (WAI)
> e-mail: shawn@w3.org
> phone: +1.617.395.7664
> about: http://www.w3.org/People/Shawn/
>
>
>