Aligning with earlier updates.

requirements/index.html

@@ -176,15 +176,16 @@ <h5>Proposed updates</h5>
 		  <h2 id="design_principles">Design Principles</h2>
           <p>The WCAG 3.0 Design Principles are based on the requirements of WCAG 2.0 and build on those requirements to meet needs identified in the WCAG 3.0 research. </p>
           <p>Accessibility guidelines should:</p>
-          <ol>
+		  <ol>
             <li>Support the needs of a wide range of people with disabilities and recognize that people have individual and multiple needs.</li>
             <li>Support a measurement and conformance structure that includes guidance for a broad range of disabilities. This includes particular attention to the needs of low vision and cognitive accessibility, whose needs don't tend to fit the true/false statement success criteria of WCAG 2.x.</li>
             <li>Be flexible enough to support the needs of people with disabilities and keep up with emerging technologies. The information structure allows guidance to be added or removed.</li>
             <li>Be accessible and conform to the Guidelines. <span class="ednote">Note: This design principle will move to the Requirements section once the Conformance section is completed and we determine a specific measurement of compliance. </span></li>
             <li>Be written in plain language, as easy as possible to understand. <span class="ednote"> We need a definition of plain language that includes the ease of translation. Ideally, it will be a broadly accepted definition internationally. </span></li>
+			<li>Include accompanying documents that are clear and concise. Technical information  (such as methods and how-tos) can be located quickly from  a central place. </li>
+			<li>Define normative requirements unambiguously, so that there is only one possible meaning for each requirement. </li>
 			<li>Improve the ability to support automated testing where appropriate and provide a procedure for repeatable tests when manual testing is appropriate.</li>
 			<li>Provide requirements to address functional needs, while avoiding or minimizing negative impacts on other functional needs. </li>
-			<li>Include instructional videos, illustrations, and how-to content where appropriate. Although the creation of new videos and illustrations are outside the scope of this project at this time, linking to suitable resources can be done.</li>
           </ol>
           <p>The creation process for the guidelines should:</p>
           <ol start="7">