[w3ctag/design-reviews] [wg/browser-tools-testing] Browser Testing and Tools Working Group Charter (Issue #1230)

w3cbot created an issue (w3ctag/design-reviews#1230)

This issue was created because the 'horizontal review requested' label was added to
§ https://github.com/w3c/strategy/issues/558

This review is requested prior to the [Advisory Committee Review](https://www.w3.org/guide/process/charter.html#ac-review).

New charter proposal, reviewers please take note.

# Charter Review

[Charter](https://w3c.github.io/charter-drafts/2026/charter-wg-btt.html)

[diff from charter template](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fw3c.github.io%2Fcharter-drafts%2Fcharter-template.html&doc2=https%3A%2F%2Fw3c.github.io%2Fcharter-drafts%2F2026%2Fcharter-wg-btt.html)

Expected end of charter refinement phase: mid-June 2026

If applicable:

[diff from previous charter](https://services.w3.org/htmldiff?doc1=https%3A%2F%2Fwww.w3.org%2F2024%2Fbtt-wg-charter.html&doc2=https%3A%2F%2Fw3c.github.io%2Fcharter-drafts%2F2026%2Fcharter-wg-btt.html)

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

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

* Existing 
 - [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

No substantive change. Same scope and list of deliverables.

## Communities suggested for outreach

## Known or potential areas of concern

Where would charter proponents like to see issues raised? (this strategy funnel issue, a different github repo, email, ...)

The [charter-drafts repository](https://github.com/w3c/charter-drafts/)

The Working Group is not considering substantive changes to its scope, but is currently assessing support for the [AT Driver](https://w3c.github.io/at-driver/) deliverable, which has not been published on the Recommendation track during this chartering period. The deliverable may be dropped from the draft charter as a result.

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

Cc @AutomatedTester

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.


## Charter facilitator(s)

cc @tidoust

<!-- Content below this is maintained by @w3c-tag-bot -->
---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1230


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1230
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1230@github.com>