Gm intro

graphics-aam/graphics-aam.html

@@ -176,7 +176,7 @@
     It provides Accessibility API Mapping guidance for the roles defined in the WAI-ARIA Graphics Module [[!GRAPHICS-ARIA]].
   </p>
   <p>
-      The Graphics Accessibility API Mappings [[!GRAPHICS-AAM]] is part of the
+      The Graphics Accessibility API Mappings is part of the
     <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> suite
     described in the <a href="http://www.w3.org/WAI/intro/aria.php"><abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> Overview</a>.
   </p>
@@ -185,6 +185,82 @@
 		<section id="sotd"> </section>
 		<section id="intro" class="informative">
 			<h2>Introduction</h2>
+			<p>The Graphics Accessibility API Mappings specification provides role mappings 
+    for the roles in the WAI-ARIA Graphics Module  [[!GRAPHICS-ARIA]].
+   			</p>
+  <p>
+    For web documents and applications, 
+    the essential semantic information is encapsulated 
+    within the Document Object Model (<abbr title="Document Object Model">DOM</abbr>).  
+    Assistive technologies obtain this information from the user agent, 
+    which maps elements and attributes 
+    to the platform Accessibility <abbr title="Application Programming Interface">API</abbr>.
+  </p>
+  <p>
+    The original suite of element semantics defined by
+    <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> 1.0
+    only considered graphics as individual embedded images,
+    with no interactivity or meaningful semantic structure.
+    It was therefore not sufficient for communicating complex graphics,
+    such as labelled diagrams or data charts, 
+    or for interactive graphics.
+    The WAI-ARIA Graphics Module defines a core set of three roles 
+    that can convey the structure of a graphic.
+    This specification defines how <a>user agents</a> should expose those roles
+    to the <a>accessibility APIs</a> currently in use,
+    so that the semantic information is available to <a>assitive technologies</a> that use those APIs.
+  </p>
+
+  <p>
+    For an introduction to <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>, 
+    see the <a href="http://www.w3.org/WAI/intro/aria.php"><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Overview</a>.  
+    It is part of a set of resources that define and support 
+    the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> specification, 
+    including the following documents: 
+  </p>
+  <ul>
+    <li>
+      <cite><a href="http://www.w3.org/TR/wai-aria-1.1/">Accessible Rich Internet Applications (WAI-ARIA) 1.1</a></cite> [[WAI-ARIA]], 
+      a planned <abbr title="World Wide Web Consortium">W3C</abbr> recommendation 
+      that extends the exising ARIA standard [[WAI-ARIA-10]].
+      It defines the core roles, states, and properties.
+    </li>
+    <li>
+      <cite><a href="http://www.w3.org/TR/graphics-aria-1.0/">WAI-ARIA Graphics Module</a></cite> [[GRAPHICS-ARIA]],
+      a planned <abbr title="World Wide Web Consortium">W3C</abbr> recommendation that defines graphics roles, states, and properties not included in <cite><a href="http://www.w3.org/TR/wai-aria-1.1/">Accessible Rich Internet Applications (WAI-ARIA) 1.1</a></cite> [[WAI-ARIA]].
+    </li>
+    <li>
+      <cite><a href="http://www.w3.org/TR/core-aam-1.1/">Core Accessibility API Mappings</a></cite> specification [[CORE-AAM]], 
+      which expresses how <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> 
+      <a href="#dfn-role" class="termref">roles</a>, <a href="#dfn-state" class="termref">states</a>, and <a href="#dfn-property" class="termref">properties</a> 
+      should be supported in user agents 
+      using platform accessibility <abbr title="Application Programming Interfaces">APIs</abbr>.
+    </li>
+    <li>
+      <cite><a href="http://www.w3.org/TR/svg-aam-1.0">SVG Accessibility API Mappings</a></cite>[[SVG-AAM]], a planned <abbr title="World Wide Web Consortium">W3C</abbr> recommendation,
+      which expresses how <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>
+      <a href="#dfn-role" class="termref">roles</a>, <a href="#dfn-state" class="termref">states</a>, and <a href="#dfn-property" class="termref">properties</a>
+      should be supported in user agents
+      using platform accessibility <abbr title="Application Programming Interfaces">APIs</abbr>.
+    </li>
+
+    <li>
+      <cite><a href="http://www.w3.org/TR/accname-aam-1.1/">Accessible Name and Description: Computation and API Mappings 1.1</a></cite> [[ACCNAME-AAM]], 
+      which outlines the specific steps user agents should follow 
+      in order to identify accessible names (labels) and descriptions (alternative text) 
+      for elements that are exposed to assistive technologies.
+    </li>
+    <li>
+      <cite><a href="http://www.w3.org/TR/wai-aria-practices/"><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Authoring Practices Guide</a></cite> [[ARIA-PRACTICES]], 
+      a planned W3C Working Group Note, 
+      which describes how web content developers can develop 
+      accessible rich internet applications using <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. 
+      It provides detailed advice and examples 
+      directed primarily to web application developers, 
+      yet also useful to developers of user agents and assistive technologies.
+    </li>
+  </ul>
+
 		</section>
 		<section id="conformance" class="normative">
 			<p>This specification indicates whether a section is <a class="termref">normative</a> or <a class="termref">informative</a> and the classification applies to the entire section. A statement "This section is normative" or "This section is informative" applies to all sub-sections of that section.</p>