fix references

Author: jnurthen

graphics-aam/index.html

@@ -184,7 +184,7 @@
     preProcess:[linkCrossReferences],
 		postProcess:[],
 		definitionMap:[],
-		xref: ["core-aam", "accname", "wai-aria"]
+		xref: ["core-aam", "accname", "wai-aria", "dom", "infra"]
   }
 </script>
 		<script type="text/javascript">
@@ -283,14 +283,14 @@ <h2>Introduction</h2>
     <li>
       <cite><a href="https://www.w3.org/TR/core-aam-1.1/">Core Accessibility API Mappings</a></cite> specification [[CORE-AAM-1.1]], 
       which expresses how <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> 
-      <a class="termref">roles</a>, <a class="termref">states</a>, and <a class="termref">properties</a> 
+      <a class="termref">roles</a>, <a class="termref">states</a>, and [=ARIA/properties=] 
       should be supported in user agents 
       using platform accessibility <abbr title="Application Programming Interfaces">APIs</abbr>.
     </li>
     <li>
       <cite><a href="https://www.w3.org/TR/svg-aam-1.0/">SVG Accessibility API Mappings</a></cite> [[SVG-AAM-1.0]], a planned <abbr title="World Wide Web Consortium">W3C</abbr> recommendation,
       which expresses how <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>
-      <a class="termref">roles</a>, <a class="termref">states</a>, and <a class="termref">properties</a>
+      <a class="termref">roles</a>, <a class="termref">states</a>, and [=ARIA/properties=] 
       should be supported in user agents
       using platform accessibility <abbr title="Application Programming Interfaces">APIs</abbr>.
     </li>
@@ -315,7 +315,7 @@ <h2>Introduction</h2>
 		</section>
 		<section class="normative" id="conformance">
 			<h2>Conformance</h2>
-			<p>The main content of this specification is <a class="termref">normative</a> and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative" and their subsections, diagrams, examples, and notes are <a class="termref">informative</a> (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.</p>
+			<p>The main content of this specification is normative and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative" and their subsections, diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create requirements that impact a conformance claim.</p>
 			<p>Normative sections provide requirements that <a class="termref">user agents</a> must follow for an implementation to conform to this specification. The keywords <em class="rfc2119">MUST</em>, <em class="rfc2119">MUST NOT</em>, <em class="rfc2119">REQUIRED</em>, <em class="rfc2119">SHALL</em>, <em class="rfc2119">SHALL NOT</em>, <em class="rfc2119">SHOULD</em>, <em class="rfc2119">RECOMMENDED</em>, <em class="rfc2119">MAY</em>, and <em class="rfc2119">OPTIONAL</em> in this document are to be interpreted as described in <cite><a href="http://www.rfc-editor.org/rfc/rfc2119.txt">Keywords for use in RFCs to indicate requirement levels</a></cite> [[!RFC2119]]. RFC-2119 keywords are formatted in uppercase and contained in an element with <code>class="rfc2119"</code>. When the keywords shown above are used, but do not share this format, they do not convey formal information in the RFC 2119 sense, and are merely explanatory, i.e., informative. As much as possible, such usages are avoided in this specification.</p>
 			<p>Normative sections provide requirements that authors, user agents and assistive technologies MUST follow for an implementation to conform to this specification.</p>
 			<p>Non-normative (informative) sections provide information useful to understanding the specification. Such sections may contain examples of recommended practice, but it is not required to follow such recommendations in order to conform to this specification.</p>