oh yeah and need header when no id="conformance"

graphics-aria/index.html

@@ -265,6 +265,7 @@ <h2>Assistive Technologies</h2>
 	</section>
 </section>
 <section class="normative">
+	<h2>Conformance</h2>
 	<p>This specification indicates whether a section is <a class="termref">normative</a> or non-normative (<a class="termref">informative</a>) and the classification applies to the entire section. A statement "This section is normative" or "This section is non-normative" applies to all sub-sections of that section.</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 <strong class="rfc2119">MUST</strong>, <strong class="rfc2119">MUST NOT</strong>, <strong class="rfc2119">REQUIRED</strong>, <strong class="rfc2119">SHALL</strong>, <strong class="rfc2119">SHALL NOT</strong>, <strong class="rfc2119">SHOULD</strong>, <strong class="rfc2119">RECOMMENDED</strong>, <strong class="rfc2119">MAY</strong>, and <strong class="rfc2119">OPTIONAL</strong> 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 a <code>strong</code> 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>