Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

APA Pronunciation TF Review of Implementation Options #46

Closed
becka11y opened this issue Sep 29, 2020 · 4 comments
Closed

APA Pronunciation TF Review of Implementation Options #46

becka11y opened this issue Sep 29, 2020 · 4 comments

Comments

@becka11y
Copy link

こんにちはTAG!

I'm requesting TAG presence at the following virtual meeting during TPAC 2020:

When the meeting agenda and specific room has been finalized, we request the groups to note these details as comments in this issue.

Please note that we will not officially register as observers, as the assignee for presence will not be decided until all the groups have sent in requests.

@becka11y
Copy link
Author

becka11y commented Sep 29, 2020

Introductory Pronunciation Video: https://www.w3.org/2020/10/TPAC/apa-pronunciation.html

Screen reader users, as well as "read aloud" assistive technology users
(such as persons living with dyslexia) have long put up with some pretty
horrendous pronunciation from text to speech (TTS) engines. This becomes
more than simply annoying, however, in circumstances such as timed
academic test taking (such as the LSAT that is used in law school
applications).

We are now on the verge of writing a specification for First Public
Working Draft (FPWD) publication specifying an approach to close this
gap for accessibility.

However, we need to decide between two candidate approaches.

1.) We have at least one candidate approach that will serve
accessibility requirements well. This could be the end of the story.

2.) However, it seems to us there's need of an approach that's more
widely applicable across the industry now that we've moved into an era
of voice computing with major platforms like Amazon's Alexa, Apple's
Siri, Google's Assistant, and Microsoft's cortana. Our forthcoming video
will illustrate an SSML based approach we believe could work for us and
the wider industry.

The question is whether (or not) there is interest in pursuing a more generally applicable specification? This is what
we want to discuss with you during TPAC.

What we would need from WHAT: The more widely applicable approach would require admitting a subset of SSML markup into the HTML specification with the same kind of status as currently exists for XVG and MathML.

@torgo
Copy link
Member

torgo commented Oct 7, 2020

It looks like @hadleybeeman and @atanassov at the minimum can make this.

@torgo
Copy link
Member

torgo commented Oct 15, 2020

Hi @becka11y we haven't been able to be there for today's discussion (due to availability of participants) but we can definitely make tomorrow's one (this request). Hopefully we can use the time to discuss both issues. Can you please update your meeting page to reflect that Friday's TAG joint meeting is confirmed and to let us know the call details? Thanks.

@becka11y
Copy link
Author

We can use the apa standard call information for the Friday meeting. Find it at https://www.w3.org/2017/08/telecon-info_apa-tpac

@cynthia cynthia closed this as completed Jun 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants