W3C home > Mailing lists > Public > public-pronunciation@w3.org > April 2020

Announcements are out

From: Janina Sajka <janina@rednote.net>
Date: Mon, 27 Apr 2020 14:29:04 -0400
To: public-pronunciation@w3.org
Message-ID: <20200427182904.GE141412@rednote.net>
Colleagues:

Shawn Henry just posted the following on WAI-IG. I haven't looked yet,
but I expect the remaining announcements are now also out, or imminent.

We should plan accordingly now, especially with respect to taking our
proposals to WICG.

Best,

Janina

Shawn Henry writes:
> Dear WAI Interest Group,
> 
> The Pronunciation Task Force and the Accessible Platform Architectures Working Group (APA WG) are seeking input on the following Working Drafts:
> 
> 1. Explainer: Improving Spoken Presentation on the Web
> 	https://www.w3.org/TR/pronunciation-explainer/
> - Briefly introduces the context for W3C work on pronunciation
> - Describes the advantages and disadvantages of two approaches
> - Poses questions for additional input
> 
> 2. Pronunciation Gap Analysis and Use Cases
> 	https://www.w3.org/TR/pronunciation-gap-analysis-and-use-cases/
> - Provides more detailed context
> - Describes required features for pronunciation and spoken presentation
> - Describes specific implementation approaches for introducing presentation authoring markup into HTML5 (called “use cases”)
> - Provides a gap analysis
> - Describes how the required features may be met by existing approaches
> 
> Background: These documents will guide work on a normative specification to enable content authors to ensure that text-to-speech (TTS) synthesis properly pronounces HTML content. For context on this work, please see:
> 	Pronunciation Overview
> 	https://www.w3.org/WAI/pronunciation/
> 
> Review: We seek reviews of these Working Drafts from all interested web stakeholders, whether or not you specialize in web accessibility.
> *We particularly request input on the following*:
> * Are there additional use cases and requirements not described in these documents?
> * Are there aspects of these requirements, use cases, and gap analysis that are incorrect or insufficiently defined?
> * Have we overlooked some aspect in this analysis that should be addressed?
> 
> Comments: To comment, please open a new issue in the W3C Spec GitHub repository:
> 	https://github.com/w3c/pronunciation/issues
> If this is not feasible, send email to: public-pronunciation@w3.org
> 
> Please send comments as soon as feasible.
> 
> Share: We encourage you to share this information and include @w3c_wai, @w3c, #a11y, #TTSpronunciation #SSML
> Here’s a tweet you can use: https://twitter.com/w3c_wai/status/1254837383520030720
> 
> Regards,
> Janina Sajka, APA Working Group Chair
> Irfan Ali, Pronunciation Task Force Facilitator
> Roy Ran, W3C Staff Contact for Pronunciation Task Force

-- 

Janina Sajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Monday, 27 April 2020 18:29:17 UTC

This archive was generated by hypermail 2.4.0 : Monday, 27 April 2020 18:29:18 UTC