Fwd: [Transition Request] Request to transition Accessible Name and Description: Computation and API Mappings 1.1 to First Public Working Draft

All, this may be of interest.

Kind regards

Nigel


Begin forwarded message:

Resent-From: <chairs@w3.org<mailto:chairs@w3.org>>
From: Michael Cooper <cooper@w3.org<mailto:cooper@w3.org>>
Date: 5 December 2014 22:05:40 GMT
To: Judy Brewer <jbrewer@w3.org<mailto:jbrewer@w3.org>>
Cc: Comm <w3t-comm@w3.org<mailto:w3t-comm@w3.org>>, Chairs <chairs@w3.org<mailto:chairs@w3.org>>
Subject: [Transition Request] Request to transition Accessible Name and Description:  Computation and API Mappings 1.1 to First Public Working Draft


The Protocols and Formats Working Group requests approval to transition Accessible Name and Description: Computation and API Mappings 1.1 to First Public Working Draft.

Title: Accessible Name and Description: Computation and API Mappings 1.1
Short Name: accname-aam-1.1
Description:  Describes how user agents determine names and descriptions of accessible objects from web content languages and expose them in accessibility APIs.
TR Categories: "Accessibility (All)", "Accessible Rich Internet Applications (WAI-ARIA)"
Publication URI: http://www.w3.org/TR/2014/WD-accname-aam-1.1-20141211/
Latest version URI: http://www.w3.org/TR/accname-aam-1.1/
Editors' Draft URI: http://w3c.github.io/aria/accname-aam/accname-aam.html

We hope to publish this document on 11 December 2014. The editors' draft of this document that we plan to publish at the above URIs is located at http://w3c.github.io/aria/accname-aam/accname-aam.html.

== Document Abstract ==

This document 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. Documenting the algorithm and mappings promotes interoperable exposure of these properties and events as implemented by different accessibility APIs, and helps to ensure that this information appears in a manner consistent with author intent.

The accessible name and description computation and mappings specification defines support that applies across multiple content technologies. This includes accessible name and description provided by general-purpose WAI-ARIA roles, states, and properties as well as features specific to individual content languages. The accessible name and description computation extends the mapping guidance provided by CORE-AAM and technology-specific accessibility API mappings.

This document updates and will eventually supersede the accessible name and description guidance in the WAI-ARIA 1.0 User Agent Implementation Guide W3C Recommendation. It is part of the WAI-ARIA suite described in the WAI-ARIA Overview.

== Document Status section ==

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.

This is a First Public Working Draft of Accessible Name and Description: Computation and API Mappings 1.1 by the Protocols & Formats Working Group of the Web Accessibility Initiative. 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. It is anticipated that this specification will progress on the same timeline as those two specifications, though it may also be updated as needed to describe accessible name and description computation for additional host languages.

Feedback on any aspect of the specification is accepted. For this publication, the Protocols and Formats Working Group particularly seeks feedback on the following questions:

  *   Is the accessible name and description computation clear?
  *   Are ambiguities between the role of WAI-ARIA and host language features resolved?
  *   Is the relationship of this specification to WAI-ARIA 1.1 and Core Accessibility API Mappings 1.1 clear?

To comment, send email to public-pfwg-comments@w3.org<mailto:public-pfwg-comments@w3.org> (comment archive) or file an issue in W3C Bugzilla. Comments are requested by 30 January 2015. In-progress updates to the document may be viewed in the publicly visible editors' draft.

Publication as a First Public Working Draft does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.

This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.

This document is governed by the 1 August 2014 W3C Process Document.

== Delta specification ==

This is not a delta specification.

== Record of the decision to request the transition ==

The Protocols and Formats Working Group agreed to request this transition in an email call for consensus, the results of which are reported at http://lists.w3.org/Archives/Public/public-pfwg/2014Dec/0068.html.

--

Michael Cooper
Web Accessibility Specialist
World Wide Web Consortium, Web Accessibility Initiative
E-mail cooper@w3.org<mailto:cooper@w3.org>
Information Page<http://www.w3.org/People/cooper/>