Call for Review: Core Accessibility API Mappings 1.1 (Core-AAM) and WAI-ARIA 1.1

Dear WAI Interest Group Participants,

W3C WAI invites you to comment on a new draft of Core Accessibility API Mappings 1.1 and an updated draft of WAI-ARIA 1.1 at:

*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 <>.

*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.

WAI-ARIA 1.0 is currently a W3C Recommendation. It remains the recommended version for production user agent implementations and authors at this time. WAI-ARIA 1.1 and Core-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: <>.

In-progress updates to WAI-ARIA 1.1 are available in an Editors' Draft at <>.
In-progress updates to Core Accessibility API Mappings 1.1 are available in an Editors' Draft at < >.

The status of WAI-ARIA versions is updated in the WAI-ARIA FAQ: <>

*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 *11 July 2014*

About the URIs:
The first URIs above go to the latest versions of the documents. The "dated" versions of these drafts are: <> and <>. The difference between these URIs are explained in Referencing and Linking to WAI Guidelines and Technical Documents at: <>

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, W3C Staff Contact

Shawn Lawton Henry
W3C Web Accessibility Initiative (WAI)
Massachusetts Institute of Technology (MIT)
phone: +1.617.395.7664

Received on Thursday, 12 June 2014 16:11:04 UTC