Update from Issue 44 (#739)

* Update from Issue 44

Closes #44

* Covering #727 as well

* Gregg's suggestions from thread in #739

* Caveating the general requirement for self-meeting

requirements/index.html

@@ -113,7 +113,7 @@ <h4>Usability</h4>
 					<h4>Conformance Model</h4>
 					<p>There are several areas for exploration in how conformance can work. These opportunities may or may not be incorporated. They need to work together, and that interplay will be governed by the design principles</p>
 					<ul>
-						<li><strong>Measurable Guidance</strong>: Certain accessibility guidance is best expressed as a true/false statement. Others far less so. There are needs of people with disabilities, especially cognitive and low vision disabilities, that are better captured by a different type of measurement. WCAG 3.0 can include multiple means of measurement, in addition to true/false statements, allowing inclusion of more accessibility guidance.</li>
+						<li><strong>Measurable Guidance</strong>: Certain accessibility guidance is best expressed as a true/false statement. Others far less so. There are needs of people with disabilities, especially cognitive and low vision disabilities, that are better captured by a different type of measurement. WCAG 3.0 can include guidance (provisions) that use different means of evaluation beyond just true/false performance or outcome statements, allowing for the inclusion of more accessibility guidance.</li>
 						<li><strong>Scope Options</strong>: WCAG 3.0 conformance could include web pages, web sites, page sections, individual components, and conformance based on a set of tasks as defined by the author of the site or application. A task-based assessment would allow flexibility for conformance of complex applications that go beyond component/tag assessment or full-page assessment.</li>
 						<li><strong>Accessibility Supported</strong>: As the technologies advance, the lines between content, user agents, and assistive technology will continue to shift and blur. Interoperability may be affected by any number of factors outside of the control of the author and publisher of digital content. WCAG 3.0 can include advice to user agents and assistive technology developers. WCAG 3 does not intend to make authors responsible for interoperability problems beyond a reasonable effort.</li>
 					</ul>
@@ -188,6 +188,7 @@ <h2 id="design_principles">Design Principles</h2>
 			<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 accompanying documents that provide clear, concise, and findable technical information quickly in one place.</li>
+			<li>Include, where possible and appropriate, links to instruction videos, illustrations, and how-to guides. Creation of new videos and illustrations are outside the scope of the working group at this time.</li>
 			<li>Normative requirements should be unambiguous so there is only one possible meaning for each requirement.</li>
           </ol>
           <p>The creation process for the guidelines should:</p>
@@ -204,42 +205,47 @@ <h2 id="requirements">Requirements</h2>
           <p>The WCAG 3.0 Requirements are high level and will be expanded and refined as Silver members move through the prototyping process.</p>
           <section>
           <h3>Broad disability support</h3>
-          <p>Silver guidance includes tests and other evaluation methods. Some guidance may use true/false verification but other guidance will use other ways of measuring and/or evaluating where appropriate so that more needs of people with disabilities may be included (for example: rubrics, sliding scale, task-completion, user research with people with disabilities, and more). This approach includes particular attention to people whose needs may better be met with a broad testing strategy, such as people with low vision, limited vision, or cognitive and learning disabilities. </p>
+          <p>The guidance includes requirements that are not available in WCAG 2.x. Some guidance may use true/false verification but other guidance will use other ways of measuring and/or evaluating where appropriate so that more needs of people with disabilities may be included (for example: rubrics, sliding scale, task-completion, user research with people with disabilities, and more). This approach includes particular attention to people whose needs may better be met with a broad testing strategy, such as people with low vision, limited vision, or cognitive and learning disabilities.</p>
           </section>
           <section>
           <h3>Flexible maintenance and extensibility</h3>
-            <p>Create a maintenance and extensibility model for guidelines that can better meet the needs of people with disabilities using emerging technologies and interactions. The process of developing the guidance includes experts in the technology.</p>
+            <p>The informative documentation uses a process that is easy to update and maintain.
+			The process of developing the guidance includes experts who review the guidelines to check they will work for emerging technologies and interactions.</p>
             </section>
           <section>
             <h3>Multiple ways to display</h3>
-            <p>Design the guidelines so that they can be presented in different accessible and usable ways or formats, to address the needs of different audiences.</p>
+            <p>The Guidelines can be presented in different accessible and usable ways or formats, to address the needs of different audiences.</p>
           </section>
           <section>
             <h3>Technology Neutral</h3>
-	    <p>Guidance should be expressed in generic terms so that they may apply to more than one platform or technology. The intent of technology-neutral wording is to provide the opportunity to apply the core guidelines to current and emerging technology, even if specific technical advice doesn't yet exist.</p>
+	    <p>Guidance is expressed in technology-neutral terms so that it can be met using different platforms or technologies. The intent of technology-neutral wording is to provide the opportunity to apply the core guidelines to current and emerging technology, even if specific technical advice doesn't yet exist.</p>
 	 </section>
           <section>
             <h3>Readability</h3>
-            <p>The core guidelines are understandable by a non-technical audience. Where technical guidance is necessary, a plain language alternative or summary will be provided. Text and presentation are usable and understandable through the use of plain language, structure, and design. They link to instruction videos, illustrations, and how-to where available.  Creation of new videos and illustrations are outside the scope of this project at this time.</p>
+            <p>Requirements in WCAG 3 for plain language shall be applied to WCAG 3. It is desirable for the guidelines to be understandable by the widest possible audience.</p>
           </section>
           <section>
             <h3>Regulatory Environment</h3>
-	    <p>The Guidelines provide broad support, including</p>
+	    <p>Requirements are written to facilitate adoption into law, regulation, or policy, since this has been shown to have major impact on practice. This includes:</p>
 	    <ul>
-	      <li>Structure, methodology, and content that facilitates adoption into law, regulation, or policy, and</li>
-	      <li>clear intent and transparency as to purpose and goals, to assist when there are questions or controversy.</li>
+	      <li>making the need and purpose for the requirement clear, and</li>
+	      <li>a clear definition of when requirements are met.</li>
 	    </ul>
 	  </section>
           <section>
             <h3>Motivation</h3>
-	    <p>The Guidelines motivate organizations to go beyond minimal accessibility requirements by structuring WCAG 3 to provide encouragement to organizations which demonstrate a greater effort to improve accessibility.</p>
+	    <p>The Guidelines motivate organizations to go beyond minimal accessibility requirements with a conformance model that shows which organizations demonstrate a greater effort to improve accessibility</p>
 	 </section>
-          <section>
+        <section>
             <h3>Scope</h3>
-	    <p>The guidelines provide guidance and a conformance model for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. The associated informative materials will include guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.</p>
+	    <p>WCAG 3 will provide guidance and a conformance model suitable for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. The scope of the associated informative materials will include guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.</p>
 
-	</section>
 		</section>
+		<section>
+			<h3>Self validation</h3>
+			<p>The WCAG 3 guidelines document shall meet its own requirements where relevant. (Some requirements may apply to organisations or scenarios not relevent to the development of a standard.)</p>
+		</section>
+	</section>
 		<section class="appendix" id="changelog">
 	    <h2>Change Log</h2>
           <section>