Re: [EXTERNAL] Re: DRAFT- Response to WHAT

Those sound good.

As is apparent, I didn't reread the explainer. My faulty memory was that it
said that in the absence of being able to directly use SSML, here are two
attribute-based approaches. I'm glad that's not the case as it shows the
group has spent time on SSML inclusion.

    Neil


On Tue, Nov 1, 2022 at 2:13 PM Hakkinen, Mark T <mhakkinen@ets.org> wrote:

> Thanks, Neil.  I’ll suggest some further tweaks in two sentences.
>
>
>
> First:
>
>
>
> > This is needed by both AT such as screen readers and by voice assistants
> such as Alexa, Siri, and Google [is there a name?].
>
>
>
> I would suggest instead:
>
>
>
> “This  benefits users of both AT, such as screen readers and read aloud
> tools, and voice assistants, such as Alexa, Siri, and Google Assistant.”
>
>
>
> Second:
>
>
>
> > Your recommendation of direct inclusion of SSML into web pages is a much
> more straightforward solution than that contained in the explainer.
> In-line SSML in HTML is indeed described in the explainer (see 6.1 In-line
> SSML), with pros and cons, including the concern that it may be difficult
> for assistive technologies to implement (which is what we heard at the
> time).  Perhaps changing the sentence to the following:
>
> “Your recommendation of direct inclusion of SSML into web pages is in line
> with one of the two identified approaches in the Explainer,  with the
> concern noted that it appears to be more difficult for Assistive
> Technologies to implement.  It will be important to explore those concerns,
> as this is a critical audience for the proposal."
>
>
>
>
>
>
>
>
>
>
>
> *From: *Neil Soiffer <soiffer@alum.mit.edu>
> *Date: *Tuesday, November 1, 2022 at 4:52 PM
> *To: *Irfan Ali <irfan79@gmail.com>
> *Cc: *Spoken Pronunciation Task Force <public-pronunciation@w3.org>
> *Subject: *[EXTERNAL] Re: DRAFT- Response to WHAT
>
> *CAUTION: This email originated from outside of our organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.*
>
> I can't parse this sentence:
>
> > So, in this email, we'd like to confirm your recommendation regarding
> specifics relating to our work on a normative approach for TTS the
> generated output that can be relied on to produce consistent results across
> multiple operating environments and user agents.
>
>
>
> Are some words missing?
>
>
>
> I'm happy to see the link to the explainer is now included. However, I
> still feel like the setup doesn't give readers who aren't aware of what the
> group is trying to do, much of a reason to bother clicking on the links. I
> suggest maybe something like:
>
>
>
> "As a reminder, the Spoken Presentation Task Force is tackling the issue
> of how TTS can be told to more accurately pronounce content in web pages.
> This is needed by both AT such as screen readers and by voice assistants
> such as Alexa, Siri, and Google [is there a name?]. Our home page (
> https://www.w3.org/WAI/APA/task-forces/pronunciation/
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2FAPA%2Ftask-forces%2Fpronunciation%2F&data=05%7C01%7Cmhakkinen%40ets.org%7C37b8910223b3415faa0e08dabc4b05b4%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C638029327673822120%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=SUY4e7cJo7V2kPGxJQ8ZDYIRfatXX3zq0JRB%2FxOyTEA%3D&reserved=0>)
> has a number of links to background information and demos. There is a
> detailed explainer (https://w3c.github.io/pronunciation/explainer/
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fpronunciation%2Fexplainer%2F&data=05%7C01%7Cmhakkinen%40ets.org%7C37b8910223b3415faa0e08dabc4b05b4%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C638029327673978366%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rbZ5cJ6xB0OuHzb79TxHNeaLAuCTvUBim9UfNQU7X0Q%3D&reserved=0>)
> that contains two identified approaches and enumerates their advantages and
> disadvantages. Your recommendation of direct inclusion of SSML into web
> pages is a much more straightforward solution than that contained in the
> explainer."
>
>
>
> On Tue, Nov 1, 2022 at 11:15 AM Irfan Ali <irfan79@gmail.com> wrote:
>
> Dear All,
>
> I have created a wiki page for the draft response to  WHATWG, Please take
> a look and let me know what you think. Please send me and Paul your
> comments and we shall make the changes.
>
>
>
> https://github.com/w3c/pronunciation/wiki/DRAFT-:-Response-to-WHAT
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fpronunciation%2Fwiki%2FDRAFT-%3A-Response-to-WHAT&data=05%7C01%7Cmhakkinen%40ets.org%7C37b8910223b3415faa0e08dabc4b05b4%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C638029327673978366%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Rf9Q6vQBe%2B8jiMSm5wvGZBWKfioEVFatKBsdBK7ycBc%3D&reserved=0>
>
>
>
> Best Regards,
>
> Irfan Ali
>
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
> Thank you for your compliance.
> ------------------------------
>