Re: APA Charter and the Pronunciation TF

Thanks Matthew, All. This does it for me. I will now forward up stream
for management review!

Matthew Atkinson writes:
> Hi Janina, all,
> 
> We discussed the purpose and rationale for the TF today on our call, and
> came up with the following (taking in mind your input, which was helpful):
> 
> The purpose of the TF is to provide author-controlled markup to define
> precise pronunciation across environments when content authors need
> certainty as opposed to cross-platform heuristic variability.
> 
> Here is a piece we wrote that we feel really explains the rationale for this
> work:
> 
> Think of someone that faces barriers such as print and learning
> disabilitiles - they have to deal with the scenario that what's being
> announced isn't what's being communicated, and they have to work around
> those barriers before starting to engage with the content (or having their
> engagement with the content interrupted).
> 
> Best regards,
> 
> 
> Matthew
> 
> Matthew Atkinson
> Head of Web Standards
> Samsung R&D Institute UK
> Samsung Electronics
> +44 7733 238 020
> 
> Samsung R&D Institute (SRUK), Communications House, South Street,
> Staines-upon-Thames, Surrey, TW18 4QE. A division of Samsung Electronics
> (UK) Limited, a limited company registered in England and Wales with
> registered number 03086621 and whose registered address is Samsung House,
> 2000 Hillswood Drive, Chertsey, Surrey, KT16 0RS, UK. This email (including
> any attachments) is private and confidential, and may be privileged. It is
> for the exclusive use of the intended recipient(s). If you have received
> this email in error, please inform the sender immediately and then delete
> this email. Unless you have been given specific permission to do so, please
> do not distribute or copy this email or its contents. Unless the text of
> this email specifically states that it is a contractual offer or acceptance,
> the sender does not intend to create a legal relationship and this email
> shall not constitute an offer or acceptance which could give rise to a
> contract. Any views expressed in this communication are those of the
> individual sender, except where the sender specifically states them to be
> the views of Samsung.
> 
> > -----Original Message-----
> > From: Janina Sajka <janina@rednote.net>
> > Sent: 03 March 2025 13:53
> > To: Paul Grenier <pgrenier@gmail.com>; public-pronunciation@w3.org
> > Subject: Re: APA Charter and the Pronunciation TF
> > 
> > Hi Paul, All:
> > 
> > Sorry for my slow response ... I'm resending this email to get Paul's and
> my
> > thoughts into our archives, and to get the wider group engaged in the
> > conversation!
> > 
> > About the deliverables we need to reference in the new APA Charter, but
> > also about the one-sentence description of the purpose of Spoken
> > Presentation work:
> > 
> > I want to work on phrases that could go into the full description
> statement.
> > We say predictable. I suspect that's in contrast to taking a chance with
> > heuristics. So far I don't see our drafts saying that heuristics are a
> crap-shoot!
> > I think we need a not so in your face way of saying that ...
> > 
> > I'm mulling something like:
> > 
> > use of SSML and PLS markup
> > to define precise pronunciation across environments when content authors
> > need certainty as opposed to cross-platform  heuristic variability
> > 
> > 
> > The above could say "predictability" instead of "certainty," but I wanted
> to
> > test this on you for general direction.
> > 
> > thoughts about saying something about why heuristics are insufficient?
> > 
> > Best,
> > Janina
> > 
> > 
> > Paul Grenier writes:
> > > 11:29 <PaulG> possible: "This specification will provide for
> > > author-controlled pronunciation of HTML content when using text to
> > > speech
> > > (TTS) including assistive technology (AT). This would allow for
> > > precise pronunciation support for the aural user experience beyond
> > > what heuristics can provide because it lacks understanding of the author
> > intent."
> > >
> > > 11:33 <PaulG> possible: "This specification will provide for
> > > author-controlled pronunciation of HTML content when using text to
> > > speech
> > > (TTS) technologies, including assistive technology (AT). This would
> > > allow for precise pronunciation support for the aural user experience
> > > beyond what heuristics can provide because it lacks understanding of the
> > author intent."
> > >
> > > 11:35 <PaulG> possible: "This specification will provide for
> > > author-controlled pronunciation of HTML content when using text to
> > > speech
> > > (TTS) technologies, including assistive technology (AT). This would
> > > allow for precise pronunciation support for the aural user experience
> > > when the author has a specific intent in mind that would not be
> > > supported by heuristics."
> > >
> > >
> > > *--*
> > > *Paul Grenier*
> > >
> > >
> > >
> > > On Mon, Feb 24, 2025 at 5:53???AM Janina Sajka <janina@rednote.net>
> > wrote:
> > >
> > > > Hi Paul:
> > > >
> > > > I see the announcement of today's meeting. I will try to join, but I
> > > > will be at least 10-20 minutes late as I'll be out and about and
> > > > scrounging a location to call in from.
> > > >
> > > > Please, can we consider the deliverable description in the current
> > > > APA Charter here:
> > > >
> > > > https://raw.githack.com/w3c/apa/charter-2025/charter.html#deliverabl
> > > > es
> > > >
> > > > What needs to change -- Or is it OK as is?
> > > >
> > > > What you see there is text from our current Charter, even though
> > > > this is the github for edits to our next Charter.
> > > >
> > > > Best,
> > > > Janina
> > > >
> > > >
> > > > --
> > > >
> > > > Janina Sajka (she/her/hers)
> > > > Accessibility Consultant
> > > > https://protect2.fireeye.com/v1/url?k=67976db4-061c788e-6796e6fb-74f
> > > > e4860008a-f4658043fd75dfd7&q=1&e=33458f68-0b94-4230-a06d-
> > da9dec5de1d
> > > > 2&u=https%3A%2F%2Flinkedin.com%2Fin%2Fjsajka
> > > >
> > > > The World Wide Web Consortium (W3C), Web Accessibility Initiative
> > (WAI)
> > > > Co-Chair, Accessible Platform Architectures
> > http://www.w3.org/wai/apa
> > > >
> > > > Linux Foundation Fellow
> > > > https://www.linuxfoundation.org/board-of-directors-2/
> > > >
> > > >
> > 
> > --
> > 
> > Janina Sajka (she/her/hers)
> > Accessibility Consultant https://protect2.fireeye.com/v1/url?k=9a8ec7a8-
> > fb05d292-9a8f4ce7-74fe4860008a-27dddfd034d4acc9&q=1&e=33458f68-
> > 0b94-4230-a06d-
> > da9dec5de1d2&u=https%3A%2F%2Flinkedin.com%2Fin%2Fjsajka
> > 
> > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> > Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
> > 
> > Linux Foundation Fellow
> > https://www.linuxfoundation.org/board-of-directors-2/
> > 
> 

-- 

Janina Sajka (she/her/hers)
Accessibility Consultant https://linkedin.com/in/jsajka

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Linux Foundation Fellow
https://www.linuxfoundation.org/board-of-directors-2/

Received on Monday, 17 March 2025 23:42:32 UTC