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

Call for Review: WAI-ARIA 1.1 and Accessibility API Mappings Working Drafts

From: Shawn Henry <shawn@w3.org>
Date: Thu, 11 Dec 2014 10:19:58 -0600
Message-ID: <5489C42E.9030609@w3.org>
To: WAI Interest Group <w3c-wai-ig@w3.org>
Dear WAI Interest Group Participants,

The W3C WAI Protocols and Formats Working Group (PFWG) invites you to comment on new and updated Working Drafts of:
* Accessible Rich Internet Applications (WAI-ARIA) 1.1 (updated)
* Core Accessibility API Mappings 1.1 (Core-AAM) (updated)
* Accessible Name and Description: Computation and API Mappings 1.1 (AccName-AAM) (new)

*About WAI-ARIA*:
WAI-ARIA defines a way to make web content, particularly web applications, more accessible to people with disabilities. It especially helps with dynamic content and advanced user interface controls developed with Ajax, HTML, JavaScript, and related technologies. WAI-ARIA works with existing web content technologies, such as HTML and SVG, and provides a way to apply the requirements of Web Content Accessibility Guidelines (WCAG) 2.0 for rich web applications. It is introduced in the WAI-ARIA Overview at <http://www.w3.org/WAI/intro/aria>.

*About Core-AAM*:
Core Accessibility API Mappings (Core-AAM) describes how user agents should expose content semantics (including WAI-ARIA semantics) to accessibility APIs. Core-AAM defines support that applies across multiple content technologies, including general keyboard navigation support and mapping of general-purpose WAI-ARIA features. Other Accessibility API Mappings specifications will depend on and extend this Core specification for specific technologies, including native technology features and WAI-ARIA extensions. Core-AAM will eventually supersede the guidance in the WAI-ARIA 1.0 User Agent Implementation Guide that is a W3C Recommendation.

*About AccName-AAM*:
Accessible Name and Description: Computation and API Mappings 1.1 (AccName-AAM) describes how user agents determine names and descriptions of accessible objects from web content languages and expose them in accessibility APIs. This allows assistive technologies to associate and relay the name or description of objects to users. It contains content previously published in WAI-ARIA 1.1 and Core Accessibility API Mappings 1.1. Moving that content to this specification eliminates duplication between Core AAM and WAI-ARIA, and facilitates future host language-specific accessible name guidance. The AccName-AAM defines support for general-purpose WAI-ARIA roles, states, and properties as well as features specific to individual content languages.

WAI-ARIA 1.0 is currently a W3C Recommendation. It remains the recommended version for production user agent implementations and authors at this time. The status of WAI-ARIA versions is updated in the WAI-ARIA FAQ: http://www.w3.org/WAI/aria/faq#status
WAI-ARIA 1.1, Core-AAM 1.1, and AccName-AAM 1.1 are Working Drafts and subject to change. Eventually they are expected to advance to Recommendation, at which point they would subsume WAI-ARIA 1.0. The stages of specification development are explained in How WAI Develops Accessibility Guidelines through the W3C Process at: <http://www.w3.org/WAI/intro/w3c-process>.
The in-progress updates to WAI-ARIA 1.1 are available in an Editors' Draft at <http://w3c.github.io/aria/aria/aria.html>.
The in-progress updates to Core Accessibility API Mappings 1.1 are available in an Editors' Draft at <http://w3c.github.io/aria/core-aam/core-aam.html>.
The in-progress updates to AccName-AAM 1.1 are available in an Editors' Draft at <http://w3c.github.io/aria/accname-aam/accname-aam.html>.

*For review*:

The First Public Working Draft of Core Accessibility API Mappings (Core-AAM) sets up the modularization model envisioned for WAI-ARIA 1.1 and provides accessibility API mapping support for new features in that specification. It also re-adds mappings for User Interface Automation that were removed during the Candidate Recommendation of WAI-ARIA 1.0 User Agent Implementation Guide. The updated Working Draft of WAI-ARIA 1.1 adds the "none" role and adjusts the scope and values of some states and properties.

Please submit comments the the publicly-archived e-mail:
or file an issue in W3C Bugzilla:
by *30 January 2015*

The first URIs above go to the latest versions of the documents. The "dated" versions of these drafts are: <http://www.w3.org/TR/2014/WD-wai-aria-1.1-20141211/>, <http://www.w3.org/TR/2014/WD-core-aam-1.1-20141211/>, <http://www.w3.org/TR/2014/WD-accname-aam-1.1-20141211/>. 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.

Shawn Henry, WAI Outreach
Janina Sajka, PFWG Chair
Michael Cooper, PFWG W3C Staff Contact
Judy Brewer, WAI Director

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 Thursday, 11 December 2014 16:20:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:50 UTC