Skip to content

Commit bbecab0

Browse files
authored
Webauthn 2024: Tweaks from WG (w3c#483)
* Initial * Remove testing policy * Keep a11y paragraph * Keep APA WG. Drop DiD * Updated changes section
1 parent 3dff49b commit bbecab0

File tree

1 file changed

+5
-11
lines changed

1 file changed

+5
-11
lines changed

2024/wg-webauthn.html

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -304,19 +304,13 @@ <h2>Success Criteria</h2>
304304
Proposed Recommendation, each normative specification must have an open
305305
test suite of every feature defined in the specification.</p>
306306
<p>There should be testing plans for each specification, starting from the earliest drafts.</p>
307-
<p>
308-
<i class="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 <a href='https://www.w3.org/2019/02/testing-policy.html'>tests</a>.
312-
Testing efforts should be conducted via the <a href="https://github.com/web-platform-tests/wpt">Web Platform Tests</a> project.</p>
313307

314308
<!-- Horizontal review -->
315309

316310
<p>Each specification should contain sections detailing all known security and
317311
privacy implications for implementers, Web authors, and end users.</p>
318312

319-
<p><i class="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>
320314
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
321315
recommendations for maximising accessibility in implementations.</p>
322316

@@ -358,10 +352,8 @@ <h3 id="w3c-coordination">W3C Groups</h3>
358352
<dt><a href="https://www.w3.org/groups/ig/privacy/">Privacy Interest Group</a></dt>
359353
<dd>Coordination on privacy implications.
360354

361-
<dt class="todo"><a href="https://www.w3.org/groups/wg/apa/">Accessible Platform Architectures (APA) Working Group</a></dt>
355+
<dt><a href="https://www.w3.org/groups/wg/apa/">Accessible Platform Architectures (APA) Working Group</a></dt>
362356
<dd>Coordination to review accessibility requirements for APIs and for any direct user interfaces that may be specified.
363-
<dt class="todo"><a href='https://www.w3.org/groups/wg/did/'>Decentralized Identifier Working Group</a></dt>
364-
<dd>To liaison over issues related to strong authentication and proof of ownership of decentralized identifiers.</dd>
365357
<dt><a href="https://www.w3.org/community/webauthn-adoption/">WebAuthn Adoption Community Group</a></dt>
366358
<dd>This group helps coordinate research and actions to help with broader adoption of the Web Authentication ecosystem.</dd>
367359
</dl>
@@ -624,7 +616,9 @@ <h3>
624616
<i class="todo">TBD+2</i>
625617
</td>
626618
<td>
627-
No substantive change.
619+
Minor tweaks to scope to sync with coordination section.<br>
620+
Switching to Software license for specifications.<br>
621+
Drop DiD WG coordination.
628622
</td>
629623
</tr>
630624

0 commit comments

Comments
 (0)