Merge pull request #17 from seanturner/success

Consistency on Success/Deliverables

charter.html

@@ -253,14 +253,24 @@ <h3>Timeline</h3>
 
 	<section id="success-criteria">
 	  <h2>Success Criteria</h2>
-	  <p>In order to advance to <a href="https://www.w3.org/Consortium/Process/#RecsPR" title="Proposed Recommendation">Proposed Recommendation</a>, each normative specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of every feature defined in the specification.</p>
-
-	  <p>
-          Each normative specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
+	  <p>The WG will progress its normative specifications through the following
+    standardization process: 
+    <a href="https://www.w3.org/2021/Process-20211102/#RecsWD">First Public
+      Working Draft</a>, 
+    <a href="https://www.w3.org/2021/Process-20211102/#RecsWD">Working
+      Draft</a>,
+    <a href="https://www.w3.org/2021/Process-20211102/#candidate-recommendation-draft">Candidate
+      Recommendation Draft</a>, and
+    <a href="https://www.w3.org/2021/Process-20211102/#candidate-recommendation-snapshot">Candidate
+      Recommendation Snapshot</a>.
+    It is expected that to reach the Candidate Recommendation Snapshot stage, each normative
+    specification is expected to have <a href="https://www.w3.org/Consortium/Process/#implementation-experience">at least two independent implementations</a> of every feature defined in the specification.</p>
+
+	  <p>Each normative specification should contain separate sections detailing all known security and privacy implications for implementers, Web authors, and end users.</p>
 
 	  <p>There should be testing plans for each specification, starting from the earliest drafts.</p>
 
-          <p>Normative specifications which have user-facing features should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximizing accessibility in implementations.</p>
+    <p>Normative specifications which have user-facing features should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximizing accessibility in implementations.</p>
 	</section>
 
       <section id="coordination">