Re: [EXTERNAL] question from the Publishing A11Y task force

err... rather:

"SSML markup has been provided for spoken presentation and pronunciation
when required and appropriate"

JF

On Wed, Nov 9, 2022 at 1:11 PM John Foliot <john@foliot.ca> wrote:

> Mark writes:
>
> > “TTS markup using the 1EdTech QTI data-ssml attribute has been provided
> for spoken presentation and pronunciation of chemical formulae.”
>
> While this would indeed be technically correct, it sounds and feels a tad
> "geeky" to me - will most ePub readers know (or care) about the *1EdTech
> QTI data-ssml attribute*? Or would they be happy with (prefer) something
> a bit more human readable:
>
> "TTS markup has been provided for spoken presentation and pronunciation
> when required and appropriate"
>
> Asking for a friend ;-)
>
> JF
>
> On Wed, Nov 9, 2022 at 12:43 PM Hakkinen, Mark T <mhakkinen@ets.org>
> wrote:
>
>> Hi George,
>>
>>
>>
>> To answer your question:
>>
>>
>>
>> > Our question, “What should be in the example text, ”
>>
>>
>>
>>
>>
>> We had a quick discussion in our TF meeting today. Since we do not yet
>> have an agreed upon approach for spoken presentation/pronunciation control,
>> perhaps the best solution is to reference what exists in EPUB3, perhaps
>> something like the following:
>>
>>
>>
>> “TTS markup using the EPUB3 ssml attributes has been provided for
>> phonetic pronunciation of uncommon proper names.”
>>
>>
>>
>> At the moment, EPUB3 is the only formal specification that includes
>> pronunciation guidance using SSML [1], and obviously it is a publishing
>> standard.
>>
>>
>>
>> Wearing my QTI hat, the 1EdTech/IMS QTI standard allows SSML, via the
>> data-ssml attribute. So in the context of test publishing, an example might
>> be:
>>
>>
>>
>> “TTS markup using the 1EdTech QTI data-ssml attribute has been provided
>> for spoken presentation and pronunciation of chemical formulae.”
>>
>>
>>
>> Hope this helps.
>>
>>
>>
>> Best regards,
>>
>> Mark
>>
>>
>>
>> [1]
>> https://www.w3.org/publishing/epub3/epub-contentdocs.html#sec-xhtml-ssml-attrib
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *From: *kerscher@montana.com <kerscher@montana.com>
>> *Date: *Tuesday, November 8, 2022 at 7:22 PM
>> *To: *'Spoken Pronunciation Task Force' <public-pronunciation@w3.org>
>> *Subject: *[EXTERNAL] question from the Publishing A11Y task force
>>
>> *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.*
>>
>> Hello,
>>
>>
>>
>> In the Publishing Community Group, we have created the User Experience
>> Guide to help retailers and libraries provide meaning full accessibility
>> metadata.
>>
>>
>>
>> One of the Schema.org features is “TTS Markup”
>>
>>
>>
>> The guidance information says:
>>
>> If specific markup is provided to assist TTS pronunciation, the type
>> should be included.
>>
>>
>>
>> Our question, “What should be in the example text, ”
>>
>>
>>
>> It is OK to have more than one example. It should be short and clear. We
>> do not want anything long and we do not need links to specifications.
>>
>>
>>
>> Something like:
>>
>>
>>
>> TTS markup using SSML has been provided for uncommon proper names.
>>
>> Or
>>
>> XYZ markup was used for important terms.
>>
>>
>>
>>
>>
>> Best
>>
>> George
>>
>>
>>
>>
>>
>>
>>
>> [image: Drawing of a guide dog in harness sitting looking up at a
>> dangling rope in front of a mountain wall. Credits, Outdoor Life.]
>>
>>
>>
>> George Kerscher Ph.D.
>>
>> -In our Information Age, access to information is a fundamental human
>> right.
>>
>> Chief Innovations Officer, DAISY Consortium
>>
>> http://www.daisy.org
>> <https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.daisy.org%2F&data=05%7C01%7Cmhakkinen%40ets.org%7C909ef3c91142427ee82f08dac1e888ca%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C638035501732940285%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QSwGeTRumqsxguQr%2FDi%2FIiuc6044lQ53qK99N6PpBhY%3D&reserved=0>
>>
>> Senior Advisor, Global Literacy, Benetech
>>
>> http://www.benetech.org
>> <https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.benetech.org%2F&data=05%7C01%7Cmhakkinen%40ets.org%7C909ef3c91142427ee82f08dac1e888ca%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C638035501732940285%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3al5J3groKM1ZbWgL1J6QXa1F%2FG5YoDdHz6ax2kTKeY%3D&reserved=0>
>>
>> President, International Digital Publishing Forum (IDPF)
>>
>> http://www.idpf.org
>> <https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.idpf.org%2F&data=05%7C01%7Cmhakkinen%40ets.org%7C909ef3c91142427ee82f08dac1e888ca%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C638035501732940285%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=nyPOoPNkmdqPduOpQLrC36ex4JytnlVV2DKdRYbo0yY%3D&reserved=0>
>>
>> Chair Steering Council Web Accessibility Initiative (WAI), at W3C
>>
>> http://www.w3.org/WAI
>> <https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2FWAI&data=05%7C01%7Cmhakkinen%40ets.org%7C909ef3c91142427ee82f08dac1e888ca%7C0ba6e9b760b34fae92f37e6ddd9e9b65%7C0%7C0%7C638035501733096499%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bdBE6SNbruldsYl6cuN8o46nJ8fnbbdRM2dUsPPcxqI%3D&reserved=0>
>>
>> Phone: +1 406/549-4687
>>
>> Cell:+1 406/544-2466
>>
>> Email: kerscher@montana.com
>>
>>
>>
>> ------------------------------
>>
>> 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.
>> ------------------------------
>>
>
>
> --
> *John Foliot* |
> Senior Industry Specialist, Digital Accessibility |
> W3C Accessibility Standards Contributor |
>
> "I made this so long because I did not have time to make it shorter." -
> Pascal "links go places, buttons do things"
>


-- 
*John Foliot* |
Senior Industry Specialist, Digital Accessibility |
W3C Accessibility Standards Contributor |

"I made this so long because I did not have time to make it shorter." -
Pascal "links go places, buttons do things"

Received on Wednesday, 9 November 2022 18:13:44 UTC