– DRAFT –
(MEETING TITLE)

Agenda Review, Membership & Announcements

Administrivia

matatk: Proposing to make status changes to the docs, now we've got at least most of the way with the PRs. Changes per email: https://lists.w3.org/Archives/Public/public-pronunciation/2025Jul/0005.html

DRAFT RESOLUTION: Deprecate the Gap Analysis and Use Cases document at

<https: //www.w3.org/TR/pronunciation-gap-analysis-and-use-cases/>, and refer

instead to the separate Use Cases (at

<https: //www.w3.org/TR/pronunciation-use-cases/>), and Gap Analysis (at

<https: //www.w3.org/TR/pronunciation-gap-analysis/>), documents.

<matatk> +1

<PaulG> +1

<PaulG> +1

<IrfanA> +1

RESOLUTION: Deprecate the Gap Analysis and Use Cases document at <https://www.w3.org/TR/pronunciation-gap-analysis-and-use-cases/>, and refer instead to the separate Use Cases (at <https://www.w3.org/TR/pronunciation-use-cases/>), and Gap Analysis (at <https://www.w3.org/TR/pronunciation-gap-analysis/>), documents.

DRAFT RESOLUTION: Deprecate the User Scenarios document at <https://www.w3.org/TR/pronunciation-user-scenarios/>, and refer instead to the Use Cases document (at <https://www.w3.org/TR/pronunciation-use-cases/>).

<matatk> +1

<IrfanA> +1

<PaulG> +1

<IrfanA> +1

RESOLUTION: Deprecate the User Scenarios document at <https://www.w3.org/TR/pronunciation-user-scenarios/>, and refer instead to the Use Cases document (at <https://www.w3.org/TR/pronunciation-use-cases/>).

<IrfanA> +1

matatk: *discusses next steps as per w3c/pronunciation#119 *

<gb> Action 119 TF edits on use cases (on AutoSponge, matatk, alia11y)

PaulG: We could use Steve Faulkner's help on some of the upcoming stuff, e.g. introducing us to what and who we need to know to move the work on.

PaulG: Steve and Scott worked on ARIA in HTML

Combined use cases doc: https://w3c.github.io/pronunciation/use-cases/

matatk: Any thoughts on this? We need to refocus it on user needs, not tech.

Alan: The document seems to act as if web speech supports SSML, which it doesn't to a large extent. We can't rely on that.

matatk: Could you check to see if the Gap Analysis - https://w3c.github.io/pronunciation/gap-analysis/ - is up to date?

Alan: SSML seemed to disappear when switching to Edge/Chromium.

PaulG: Whilst it's irksome for things like accessibility, the sum of the specs and patterns are aspirational and are meant to encourage support.

IrfanA: We have used google docs in the past; could do again.

IrfanA: Timelines?

matatk: ASAP :-). Would be good if by TPAC we have a community-reviewed set of use cases, and solid ideas on how to solve at least some of them.