- From: Notifier <notifier@aries.w3.org>
- Date: Thu, 08 Sep 2016 14:07:32 +0000
- To: public-review-announce@w3.org
- Message-Id: <E1bhzzI-0006qG-11@aries.w3.org>
Graphics Accessibility API Mappings https://www.w3.org/TR/2016/WD-graphics-aam-1.0-20160908/ Abstract The Graphics Accessibility API Mappings [GRAPHICS-AAM] defines how user agents map the WAI-ARIA Graphics Module [GRAPHICS-ARIA] markup to platform accessibility APIs. It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility of graphics such as that created for [SVG] or [HTML5]. The implementation of this specification in user agents enables authors to produce more accessible graphics by conveying common graphics semantics to assistive technologies. It provides Accessibility API Mapping guidance for the roles defined in the WAI-ARIA Graphics Module [GRAPHICS-ARIA]. The Graphics Accessibility API Mappings is part of the WAI-ARIA suite described in the WAI-ARIA Overview. Status of the Document 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 https://www.w3.org/TR/. This is a First Public Working Draft of Graphics Accessibility API Mappings 1.0 by the SVG Accessibility Task Force, a joint task force of the Accessible Rich Internet Applications Working Group and the SVG Working Group. It provides guidance for mapping roles in WAI-ARIA Graphics Module [GRAPHICS-ARIA] to accessibility APIs, and complements SVG-specific mappings in the SVG Accessibility API Mappings [SVG-AAM]. It extends Core Accessibility Mappings 1.1 [CORE-AAM], and is part of a suite of similar technology-specific Accessibility API Mappings specifications. Feedback on any aspect of the specification is accepted. For this publication, the SVG Accessibility Task Force particularly seeks feedback on the following questions: Are mappings of graphics features clear and appropriate? Do the platform API mappings appropriately reflect the semantics defined for these roles in the WAI-ARIA Graphics Module? Is the relationship of this specification to Core Accessibility API Mappings 1.1 clear? Is the relationship of this specification to WAI-ARIA Graphics Module and WAI-ARIA 1.1 clear? To comment, file an issue in the W3C ARIA GitHub repository, using the "graphics" label in the issue. If this is not feasible, send email to public-svg-a11y@w3.org (comment archive). Comments are requested by 30 September 2016. In-progress updates to the document may be viewed in the publicly visible editors' draft. This document was published by the Accessible Rich Internet Applications Working Group and the SVG Working Group as a Working 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 groups operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures (Accessible Rich Internet Applications Working Group) and a public list of any patent disclosures (SVG Working Group) made in connection with the deliverables of each group; these pages also include 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 September 2015 W3C Process Document.
Received on Thursday, 8 September 2016 14:08:04 UTC