[webauthn] [L3 REC] Transition Request Draft (#2399)

simoneonofri has just created a new issue for https://github.com/w3c/webauthn:

== [L3 REC] Transition Request Draft ==
# Document title, URLs, estimated publication date

Web Authentication: An API for accessing Public Key Credentials Level 3

https://www.w3.org/TR/webauthn-3

@@

# Abstract

https://www.w3.org/TR/webauthn-3/#abstract

# Status

@@

https://www.w3.org/TR/webauthn-3/#sotd

# Will new features be allowed to be incorporated in the Recommendation?

# Link to group's decision to request transition

[Minutes of 2026-03-18](https://www.w3.org/2026/03/18-webauthn-irc)

# Changes

@@

https://www.w3.org/TR/2025/CR-webauthn-3-20251121/#revision-history

# Requirements satisfied

N/A

# Dependencies met (or not)

Considering the groups present in the [charter](https://www.w3.org/2024/04/wg-webauthn-charter.html#coordination):
 - **W3C groups:** There is significant cross-participation across the various groups, both by the editors and by the groups, thanks also to cross-meetings during the various TPACs, particularly for the payments section.
 - **External groups**: there has been formal communication with 
    - [IETF SecDir](https://mailarchive.ietf.org/arch/msg/saag/iMVJFpEjf0Rj4G2hK0jMcLJhGqU/)
    - [FIDO (Team only)](https://lists.w3.org/Archives/Team/w3t-archive/2025Apr/0097.html)

# Wide Review

**Design**: 
- [Request](https://github.com/w3ctag/design-reviews/issues/1085)
- [No Issues](https://github.com/w3c/webauthn/issues?q=state%3Aopen%20label%3Atag-needs-resolution)

**Accessibility**: 
- [Request](https://github.com/w3c/a11y-request/issues/101)
- [No issues]( https://github.com/w3c/webauthn/issues?q=state%3Aopen%20label%3Aa11y-needs-resolution)

**Internationalization**:
- [Request](https://github.com/w3c/i18n-request/issues/257)
- [only old issues open](https://github.com/w3c/webauthn/issues?q=state%3Aopen%20label%3Ai18n-needs-resolution)

**Security**: 
 - [Request](https://github.com/w3c/security-request/issues/90#issuecomment-3357708982)
 - [No issues]( https://github.com/w3c/webauthn/issues?q=is%3Aissue%20state%3Aopen%20label%3Asecurity-needs-resolution)

**Privacy**: 
- [Request](https://github.com/w3cping/privacy-request/issues/162)
- [Issues](https://github.com/w3c/webauthn/issues?q=is%3Aissue%20state%3Aopen%20label%3Aprivacy-needs-resolution)
- [Mail discussion](https://lists.w3.org/Archives/Team/w3t-archive/2025Nov/0057.html)

**Transition Team**
During the [Transition to CR](https://github.com/w3c/transitions/issues/753#issuecomment-3730582563), the Team asked:

> While no formal objection was raised this document, we note that the resolution of some issues related to privacy considerations remain ongoing, in particular:
> 
> [w3c/webauthn#2319](https://github.com/w3c/webauthn/issues/2319) [w3c/webauthn#2321](https://github.com/w3c/webauthn/issues/2321)
> 
> The Team believes that those issues should be resolved within the current Recommendation cycle rather than pushed to the future. While past efforts faced hurdles, the W3C Team is committed to working alongside the Working Group throughout the Candidate Recommendation phase to improve the specification with respect to these two issues.
> 

Both issues are addressed, in the [PR 2391](https://github.com/w3c/webauthn/pull/2391), and received a comment by the [Privacy Reviewer](https://github.com/w3c/webauthn/pull/2391#issuecomment-4084811549).

# Issues addressed

https://github.com/w3c/webauthn/milestone/32?closed=1

# Formal Objections

No Formal Objections

# Implementation

@@

[WPT Results](https://www.w3.org/2021/04/wpt-fyi-snapshot.html?path=webauthn&products=chrome%2Cfirefox%2Csafari%2Cedge)

Please note that part of the implementation in Chrome is different from that in Edge.

# Patent disclosures

https://www.w3.org/groups/wg/webauthn/ipr/

NOTE: For more information, see [Organize a Technical Report Transition](https://www.w3.org/Guide/transitions?profile=newREC).


Please view or discuss this issue at https://github.com/w3c/webauthn/issues/2399 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 25 March 2026 17:50:39 UTC