- From: Michael Cooper <cooper@w3.org>
- Date: Wed, 3 Oct 2018 10:22:08 -0400
- To: WAI IG <w3c-wai-ig@w3.org>
- Message-ID: <e4207657-b814-87fc-e251-f501ee3a18ce@w3.org>
WAI-ARIA Graphics Module (Graphics-ARIA) and Graphics Accessibility API Mappings (Graphics-AAM) are W3C Recommendations: https://www.w3.org/TR/graphics-aria-1.0/ https://www.w3.org/TR/graphics-aam-1.0/ Graphics-ARIA provides three roles to allow an author to express the logical structure of graphics to assistive technologies. These three roles identify a class of structured graphics documents such as charts, maps, diagrams, technical drawing, blue prints and instructional graphics. Within graphics documents, roles allow identification of distinct objects or sub-component with semantic meaning, and symbols where the meaning is more important than the particular visual appearance. These roles work with structured graphics languages like SVG. Graphics Accessibility API Mappings defines how these roles should be exposed to accessibility APIs, and serves as a basis for SVG-specific work in SVG Accessibility API Mappings being developed separately. Future work on graphics accessibility is expected to build on the basic roles defined in this 1.0 version. At this time, the ARIA Working Group does not plan future versions of Graphics-ARIA, but may do so if additional requirements, and knowledgeable people able to help define features, test cases, and implementations, are presented to the Working Group. Please provide feedback by filing an issue in the W3C graphics-aria GitHub repository (https://github.com/w3c/graphics-aria/) for Graphics ARIA, or the W3C graphics-aam GitHub repository (https://github.com/w3c/graphics-aam/) for Graphics AAM. If this is not feasible, send email to public-aria@w3.org.
Received on Wednesday, 3 October 2018 14:22:12 UTC