Final: Benefits of WCAG 2.0 presentation material

EOWG,

Based on feedback from today's call, I made a few minor changes to the presentation at:
   <http://www.w3.org/WAI/presentations/WCAG20_benefits/WCAG20_benefits-presentation-format.ppt> 

Changes:
* Added slide #2 "WCAG 2.0 is"
* Changed the format of slide #7 "Integrated Accessibility Guidelines"
* In slide #8 "Cooperatively developed International standard", the notes section, added the second part of: "This is especially important for non-English-speaking countries that want to adopt WCAG, rather than investing effort in developing a different set of guidelines."

In the notes for slide #7, we have "Another benefit of WCAG is that it is part of an integrated suite of accessibility guidelines and specifications from the W3C WAI". Jack suggested that we add why this is a benefit. Please (anyone) send suggestions to the list for wording on that.

Other than that, this is done. After Wayne & Sharron finish the HTML version and I create an intro page for it, it's ready to go out into the world.

Best,
~Shawn


Shawn Henry wrote:
> Original thread with links to other replies:
>   <http://lists.w3.org/Archives/Public/w3c-wai-eo/2008AprJun/0091.html>
> 
>> When I present about the *benefits* of WCAG 2.0, I usually mention 
>> that it is part of a suite with ATAG and UAAG. I think this is often a 
>> very important argument to make the case for adopting WCAG 2.0.
>>
>> Also, the opportunity for having authorized translations is one of the 
>> benefits for adopting WCAG 2.0 rather than investing that same amount 
>> of effort in developing a different set of guidelines.
> 
> For discussion, I've added to the presentation at:
> <http://www.w3.org/WAI/presentations/WCAG20_benefits/WCAG20_benefits-presentation-format.ppt> 
> 
> the two slides below.
> 
> Slide 6:
> * Web Content Accessibility Guidelines
> WCAG for Web sites and applications
> * Authoring Tool Accessibility Guidelines
> ATAG for HTML editors, content management systems, blogs, wikis, etc.
> * User Agent Accessibility Guidelines
> UAAG for browsers, media players, and other ‘user agents’
> * Accessible Rich Internet Applications Suite
> WAI-ARIA for advanced Web interfaces
> 
> Speakers NOTES: Another benefit of WCAG is that it is part of an 
> integrated suite of accessibility guidelines and specifications from the 
> W3C WAI. [text on slide]
> 
> Note to presenters: If you have time, this is a topic that you might 
> want to cover in more detail. For material, see:
> - The "About WCAG 2.0" Presentation 
> <www.w3.org/WAI/presentations/WCAG20_about/>
> - Essential Components of Web Accessibility 
> <www.w3.org/WAI/intro/components.php>
> - WAI Guidelines and Techniques <www.w3.org/WAI/guid-tech.html>
> 
> Slide 7:
> Cooperatively developed International standard
> [check] W3C Web Accessibility Initiative (WAI)
> [check] W3C process designed to:
>  -- ensure broad public input, and  -- encourage consensus development
> [check] Integrated Web accessibility standards suite
> [box] Policy for Authorized W3C Translations
> 
> Speakers NOTES:
> These points are all aspects of WCAG 2.0 being a cooperatively developed 
> International standard:
> - WCAG is developed by the W3C Web Accessibility Initiative (WAI)
> - WCAG is developed under the W3C process designed to:
>  -- ensure broad public input, and  -- encourage consensus development
> - WCAG is part of an integrated Web accessibility standards suite
> 
> Another benefit is that WCAG, and other W3C specifications, can be 
> translated and provided as an Authorized W3C Translation. This is 
> especially important for non-English-speaking countries that want to 
> adopt WCAG.
> 
> ---
> Note to presenters: If you are short on time, depending on your 
> audience, you may want to cut out this slide.
> 
> 
> 
> 
> 

-- 
Shawn Lawton Henry, W3C Web Accessibility Initiative (WAI)
about: http://www.w3.org/People/Shawn/
phone: +1-617-395-7664
e-mail: shawn@w3.org

Received on Friday, 13 June 2008 21:17:13 UTC