You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 2024/wg-webauthn.html
+5-11Lines changed: 5 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -304,19 +304,13 @@ <h2>Success Criteria</h2>
304
304
Proposed Recommendation, each normative specification must have an open
305
305
test suite of every feature defined in the specification.</p>
306
306
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
307
-
<p>
308
-
<iclass="todo">Consider adopting a healthy testing policy, such as:</i> To promote interoperability, all changes made to specifications
309
-
in Candidate Recommendation
310
-
or to features that have deployed implementations
311
-
should have <ahref='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.
312
-
Testing efforts should be conducted via the <ahref="https://github.com/web-platform-tests/wpt">Web Platform Tests</a> project.</p>
313
307
314
308
<!-- Horizontal review -->
315
309
316
310
<p>Each specification should contain sections detailing all known security and
317
311
privacy implications for implementers, Web authors, and end users.</p>
318
312
319
-
<p><iclass="todo">For specifications of technologies that directly impact user experience, such as content technologies, as well as protocols and APIs which impact content: </i>
313
+
<p>
320
314
Each specification should contain a section on accessibility that describes the benefits and impacts, including ways specification features can be used to address them, and
321
315
recommendations for maximising accessibility in implementations.</p>
0 commit comments