[strategy] Issue: [wg/webauthn] Web Authentication Working Group Charter (#540) marked as Horizontal review requested

simoneonofri has just labeled an issue for https://github.com/w3c/strategy as "Horizontal review requested":

== [wg/webauthn] Web Authentication Working Group Charter ==
New charter proposal, reviewers please take note.

# Charter Review

[Web Authentication Working Group Charter](https://w3c.github.io/charter-drafts/2026/charter-wg-webauthn-2026.html)

[diff from charter template](https://services.w3.org/htmldiff?doc1=https://w3c.github.io/charter-drafts/charter-template.html&doc2=https://w3c.github.io/charter-drafts/2026/charter-wg-webauthn-2026.html)

Expected end of charter refinement phase: unknown

[diff from previous charter](https://www.w3.org/2024/04/wg-webauthn-charter.html&doc2=https://w3c.github.io/charter-drafts/2026/charter-wg-webauthn-2026.html)

[chair dashboard](https://www.w3.org/PM/Groups/chairboard.html?gid=wg/webauthn)

What kind of charter is this? Check the relevant box / remove irrelevant branches. 

 - [x] Existing WG recharter 
 
Horizontal Reviews: apply the Github label "Horizontal review requested" to request reviews for accessibility (a11y), internationalization (i18n), privacy, security, and TAG. **Also add a "card" for this issue to the [Strategy Funnel](https://github.com/orgs/w3c/projects/97/views/2).**

## Substantive changes

Short description (or link to it) of the substantive changes in this charter:
 - Deliverables update (L4)
 - Out-of-Scope
 - Groups

## Communities suggested for outreach

## Known or potential areas of concern

Where would charter proponents like to see issues raised? (this strategy funnel issue)

## Anything else we should think about as we review? 

@nadalin

Note: The Technical Strategy Team Lead or Project & Process Team Lead will assign the issue to a [Charter Facilitator](https://www.w3.org/guide/process/charter.html#cr-acceptance) for new charters. For rechartering, the team contact is the Charter Facilitator by default, please assign the issue to them directly.


See https://github.com/w3c/strategy/issues/540


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

Received on Wednesday, 25 March 2026 17:57:18 UTC