WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Fwd: Call for Review: UAAG 2.0 and Implementing UAAG 2.0 Working Drafts

for

From: terry kebbel
Date: Jul 20, 2011 5:00PM

Ok
TerryS

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ] On Behalf Of Jennifer Sutton
Sent: Wednesday, July 20, 2011 4:36 PM
To: <EMAIL REMOVED> >
Subject: [WebAIM] Fwd: Call for Review: UAAG 2.0 and Implementing UAAG 2.0
Working Drafts


>Date: Wed, 20 Jul 2011 15:26:41 -0500
>To: WAI Interest Group < <EMAIL REMOVED> >
>Subject: Call for Review: UAAG 2.0 and Implementing UAAG 2.0 Working
>Drafts
>
>Dear WAI Interest Group Participants,
>
>The W3C WAI User Agent Accessibility Guidelines (UAAG) Working Group
>invites you to comment on updated UAAG documents published 19 July 2011:
>* User Agent Accessibility Guidelines (UAAG) 2.0 Working Draft
> http://www.w3.org/TR/UAAG20/
>* Implementing UAAG 2.0 Working Draft
> http://www.w3.org/TR/Implementing-UAAG20/
>
>Changes in the updated UAAG 2.0 Working Draft include:
>* New organization - the order of the Principles has been changed to
>more closely reflect WCAG.
>* Focus - the success criteria related to focus have been separated
>into more discrete, testable success criteria.
>* Media - success criteria that were not required for accessibility
>were removed.
>
>The Working Group is looking for feedback on these changes along with
>the specific questions listed in the Status section at:
> http://www.w3.org/TR/UAAG20/#status
>
>Implementing UAAG 2.0 Working Draft provides additional information
>about the guidelines and success criteria, including intent, examples,
>and resources. This draft is mostly complete, although guidance for
>some success criteria is still to be written. Comments are welcome on
>the existing information as well as suggestions for the information yet
>to be written.
>
>WAI encourages people with disabilities and developers of browsers,
>assistive technologies, plug-ins, extensions, and accessibility APIs
>(application programming interfaces) to provide feedback on these
>drafts. Please send comments to the publicly-archived list:
> <EMAIL REMOVED>
> *by 19 August 2011*
>
>We also welcome additional help developing UAAG. If you might be
>interested in actively participating in the UAAG Working Group, please
read:
> Participating in WAI at http://www.w3.org/WAI/participation
>and contact Jeanne Spellman, see http://www.w3.org/People/jeanne/
>
>Background:
>UAAG defines how browsers, media players, and other "user agents"
>should support accessibility for people with disabilities and work with
>assistive technologies. UAAG is part of a series of accessibility
>standards developed by WAI, including Web Content Accessibility
>Guidelines (WCAG) and Authoring Tool Accessibility Guidelines (ATAG).
>UAAG 2.0 is currently informative only. For more information on UAAG
>and WAI standards, see:
>* UAAG Overview http://www.w3.org/WAI/intro/uaag.php
>* WAI Guidelines and Techniques http://www.w3.org/WAI/guid-tech.html
>* User Agent Accessibility Guidelines Working Group (UAWG)
>http://www.w3.org/WAI/UA/
>
>Please let us know if you have any questions. Thank you in advance for
>your comments.
>
>Feel free to circulate this message to other lists; please avoid
>cross-postings where possible.
>
>Regards,
>~Shawn Henry
>Jim Allan and Kelly Ford, UAAG Co-Chairs Jeanne Spellman, W3C Staff
>Contact for UAAG
>