W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2012

Reminder: Call for Review: UAAG 2.0 Working Drafts

From: Shawn Henry <shawn@w3.org>
Date: Wed, 07 Nov 2012 19:21:33 -0600
Message-ID: <509B091D.3070707@w3.org>
To: WAI Interest Group <w3c-wai-ig@w3.org>
CC: Jeanne Spellman <jeanne@w3.org>, Jim Allan <jimallan@tsbvi.edu>, Kelly Ford <Kelly.Ford@microsoft.com>
Reminder: Comments due Friday 9 November 2012.

-------- Original Message --------
Subject: 	Call for Review: UAAG 2.0 Working Drafts
Date: 	Thu, 04 Oct 2012 10:52:18 -0500
From: 	Shawn Henry <shawn@w3.org>
To: 	WAI Interest Group <w3c-wai-ig@w3.org>
CC: 	Jim Allan <jimallan@tsbvi.edu>, Kelly Ford <Kelly.Ford@microsoft.com>, Jeanne Spellman <jeanne@w3.org>



Dear WAI Interest Group Participants,

W3C WAI invites you to comment on updated Working Drafts of:
  *   User Agent Accessibility Guidelines (UAAG) 2.0
       http://www.w3.org/TR/UAAG20/
  *   Implementing UAAG 2.0 Working Draft
       http://www.w3.org/TR/Implementing-UAAG20/

Changes in this updated UAAG 2.0 Working Draft include:
  * Customize text-display and focus-highlight - added and refined success criteria so users can customize the display of text and the highlight of focus location, which is especially important to meet the needs of people with low vision, dyslexia, and other conditions that impact reading.
  * Input methods: speech, touch&  gesture - added and refined success criteria to support broad methods of input including speech, touch and gesture.
  * Mobile accessibility - refined success criteria for applicability to mobile and added examples to Implementing UAAG 2.0.

We are particularly looking for feedback on these changes and 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.

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:
      public-uaag2-comments@w3.org
      *by 9 November 2012*

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/>

URI:
The first URI above goes to the latest version of the document. The "dated" version of this draft is:<http://www.w3.org/TR/2012/WD-UAAG20-20121004/>
The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at:<http://www.w3.org/WAI/intro/linking.html>

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, WAI Education and Outreach
Jim Allan, UAWG Co-Chair
Kelly Ford, UAWG Co-Chair
Jeanne Spellman, UAWG W3C Staff Contact




-----
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/
Received on Thursday, 8 November 2012 01:21:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 8 November 2012 01:21:44 GMT