New SC for #71

drafts/guidelines.json

@@ -2322,6 +2322,10 @@
 						{
 							"title": "Avoiding Dependency",
 							"description": "Create your own clickable icons and widgets, rather than relying on third-party services to host or allow embedding within your product or service."
+						},
+						{
+							"title": "Third-party Preferences",
+							"description": "Third-party products, services, libraries, and frameworks are often a source of sustainability issues that cannot be controlled or managed by the first-party provider of a service. While many do provide benefits to a website, the need to justify their inclusion should be made not only by those creating the product or service but also be able to be controlled by the consumer. As showcased with cookies, websites or applications should provide a similar mechanism of disabling or refusing non-first-party features (with explanations of their purpose) - unless such features can be proven as critical for functionality."
 						}
 					],
 					"impact": "High",

drafts/index.html

@@ -3966,6 +3966,10 @@ <h4>Success Criterion - Self-Hosting</h4>
 					<h4>Success Criterion - Avoiding Dependency</h4>
 					<p>Create your own clickable icons and widgets, rather than relying on third-party services to host or allow embedding within your product or service.</p>
 				</section>
+				<section class="notoc">
+					<h4>Success Criterion - Third-party Preferences</h4>
+					<p>Third-party products, services, libraries, and frameworks are often a source of sustainability issues that cannot be controlled or managed by the first-party provider of a service. While many do provide benefits to a website, the need to justify their inclusion should be made not only by those creating the product or service but also be able to be controlled by the consumer. As showcased with cookies, websites or applications should provide a similar mechanism of disabling or refusing non-first-party features (with explanations of their purpose) - unless such features can be proven as critical for functionality.</p>
+				</section>
 				<section class="notoc">
 					<h4>Impact &amp; Effort</h4>
 					<dl class="rating">

drafts/quickref.html

@@ -873,6 +873,9 @@ <h2>Web Development</h2>
 					<tr>
 						<td><input type="checkbox" id="3.7e"></td><td colspan="5"><label for="3.7e">Create your own clickable icons and widgets, rather than relying on third-party services to host or allow embedding within your product or service.</label></td>
 					</tr>
+					<tr>
+						<td><input type="checkbox" id="3.7f"></td><td colspan="5"><label for="3.7f">Third-party products, services, libraries, and frameworks are often a source of sustainability issues that cannot be controlled or managed by the first-party provider of a service. While many do provide benefits to a website, the need to justify their inclusion should be made not only by those creating the product or service but also be able to be controlled by the consumer. As showcased with cookies, websites or applications should provide a similar mechanism of disabling or refusing non-first-party features (with explanations of their purpose) - unless such features can be proven as critical for functionality.</label></td>
+					</tr>
 					<tr>
 						<td></td><td><strong>Impact & Effort</strong></td>
 						<td>High</td><td>Medium</td><td></td><td></td>