Re: Wanders by and offers a thought... (was Re: Response to WHAT -- Draft #1

Hi Janina,

This isn't a problem, rather an observation: when HTML 5 moved to adopt
SVG, it also adopted MathML at the same time (making both fully fledged
members of HTML 5).

So adding SSML to the spec would be the same precedent as when they
previously added both SVG and MathML (is all). (And yes, I am trying to
keep an eye on things as best I can)

JF

On Tue, Oct 11, 2022 at 12:55 PM Janina Sajka <janina@rednote.net> wrote:

> Perhaps, John, and personally very happy to see you still participating!
>
> However, let us take one problem at a time, please! :)
>
> Janina
>
> John Foliot writes:
> > As I was not party to the discussion, I'll just wonder out loud if
> >
> > > "...elevating SSML to a status parallel to SVG in HTML 5"
> >
> > should actually also include MathML as well (i.e. SVG *and *MathML - both
> > 'xml'-based, but both previously brought in under the HTML5 umbrella)
> >
> > <waves>
> >
> > JF
> >
> >
> > On Tue, Oct 11, 2022 at 11:08 AM Janina Sajka <janina@rednote.net>
> wrote:
> >
> > > Colleagues:
> > >
> > > I have an action to draft a followup to WHATWG regarding elevating SSML
> > > to a status parallel to SVG in HTML 5. Herewith my draft. Clearly, it
> > > needs a little help, especially as I'm not immediately recalling (or
> > > finding) the list of 4 element overlaps!
> > >
> > > When we complete our drafting (hopefully this week), please allow me
> (or
> > > Matthew) to send on behalf of APA. It's a formality I think we should
> > > observe for now.
> > >
> > > <begin draft>
> > >
> > > Dear Anne, All:
> > >
> > > Thank you for the very helpful joint meeting during TPAC in Vancouver
> > > last month. APA is highly encouraged by our conversation and the
> > > outcomes. One of those specific next steps follows below. But, first
> let
> > > me ask you to also thank Mike Smith, Simon Peters, and the other WHAT
> > > participants who joined us. I would cc them--but I don't have current
> > > emails.
> > >
> > > So, in this email we'd like to confirm your recommendation regarding
> > > specifics relating to our work on a normative approach for TTS
> > > generated output that can be relied on to produce consistent results
> > > across multiple operating environments and user agents. This is the
> work
> > > of our Spoken Presentation Task Force whose home wiki page is here:
> > >
> > > https://www.w3.org/WAI/APA/task-forces/pronunciation/
> > >
> > > This was our second topic in Vancouver, under the title "Spoken
> > > Presentation" as logged here:
> > >
> > > https://www.w3.org/2022/09/13-apa-minutes.html#t03
> > >
> > > APA would like to request WHAT consider elevating SSML to a status in
> > > HTML parallel to that currently provided for SVG. We believe this would
> > > be the most direct and productive approach for our various
> accessibility
> > > use cases, and we believe it would be beneficial for nonaccessibility
> > > use cases as well.
> > >
> > > Our analysis indicates there are exactly 4 elements defined both by
> HTML
> > > and SSML for which we'd need to define disambiguation. We believe the
> > > first question should be to confirm our list. Is it correct? Or are
> > > there others? Once confirmed, we could take up what we might do to
> > > resolve the overlap.
> > >
> > > The 4 overlapping elements are:
> > >
> > > *       sub
> > >
> > > *       p
> > >
> > > *       [item 3]
> > >
> > > *       [item 4]
> > >
> > > Please advise your suggestion of next steps. Shall we log a formal
> > > github request for SSML in HTML noting the above 4 pain points?
> > >
> > > With thanks,
> > >
> > > APA Chairs
> > > Spoken Presentation Co-Facilitators
> > > cc'd to various list archives
> > >
> > > <end draft>
> > >
> > >
> > >
> > >
> > >
> > > --
> > >
> > > 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/
> > >
> > >
> > >
> >
> > --
> > *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"
>
> --
>
> 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/
>
>

-- 
*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"