W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > April to June 2013

EOWG: UAAG Call for Review

From: Shawn Henry <shawn@w3.org>
Date: Mon, 03 Jun 2013 14:09:14 -0500
Message-ID: <51ACE9DA.4010001@w3.org>
To: "EOWG (E-mail)" <w3c-wai-eo@w3.org>
Hey EOWG folks,

We need to review UAAG & Implementing UAAG (links below) for understandability, readability, usability, approachability, etc.

Who will volunteer?

You can put your comments in the wiki page at: <http://www.w3.org/WAI/EO/wiki/UAAG_review>


-------- Original Message --------
Subject: Call for Review: User Agent Accessibility Guidelines (UAAG) 2.0 Working Drafts
Date: Thu, 23 May 2013 11:52:21 -0500
From: Shawn Henry <shawn@w3.org>
To: WAI Interest Group <w3c-wai-ig@w3.org>

Dear WAI Interest Group Participants,

WAI invites you to comment on updated Working Drafts of:
* User Agent Accessibility Guidelines (UAAG) 2.0
* Implementing UAAG 2.0 Working Draft

Changes in the updated UAAG 2.0 Working Draft include:
* Edited the conformance section to encourage browser extensions that provide accessibility features to claim limited conformance
* Added a provision to Conformance to allow mobile browsers to claim conformance if the underlying platform does not support a success criterion of UAAG 2.0
* Updated the introduction section with more details on:
** The relationship between WCAG and UAAG
** Definitions of levels A, AA, AAA
** Definition of a User Agent

Changes in the updated Implementing UAAG 2.0 Working Draft include:
* Added mobile accessibility examples throughout

The UAAG Working Group is looking for feedback on these changes along with the specific questions listed in the Status section at:

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:
      *by 21 June 2013*

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 <http://www.w3.org/People/jeanne/>

UAAG defines how browsers, media players, and other "user agents" should support accessibility for people with disabilities and work with assistive technologies. Implementing UAAG 2.0 provides additional information about the guidelines and success criteria, including intent, examples, and resources.
UAAG is part of a series of accessibility standards developed by WAI, including Web Content Accessibility Guidelines (WCAG) and Authoring Tool Accessibility Guidelines (ATAG).
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.

Shawn Lawton 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)
Massachusetts Institute of Technology (MIT)
e-mail: shawn@w3.org
phone: +1.617.395.7664
about: http://www.w3.org/People/Shawn/
Received on Monday, 3 June 2013 19:09:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:29:47 UTC