W3C

- DRAFT -

Spoken Pronunciation Task Force Teleconference

12 Aug 2020

Attendees

Present
JF, irfan, Dee, janina, Roy, SteveNoble_, NeilS
Regrets
Chair
SV_MEETING_CHAIR
Scribe
paul_grenier

Contents


<scribe> scribe: paul_grenier

Irfan: how much time do we need to write a specification after we pick an approach?

paul: my concern is does our specification need to address the bridge between the browser and AT? Do we need to specify modifications to the axTree?

janina: our approach may dictate how much technical detail we need to document
... regardless of the implementation, we need a bridge to AT

JF: we need to speak to the AT vendors to understand how they will consume the new information

markku: browser vendors may not want to take on the potentially heavy lift of making these changes
... due to the 25% staff, do we know if accessibility took a hit?
... due to the 25% staff, do we know if accessibility took a hit? (at mozilla)
... patterns like <use> help make <svg> more reusable but that's not currently part of the <ssml> spec

<JF> +1

paul: creating a new element or adding an attribute to an existing <ssml> element like <speak src=""> might be options.

markku/JF: we can't consider namespaces (hijacking <use>) because it belongs to the <svg> namespace

markku: do we know when we can get a meeting with Jaime (Chrome)?

janina: we need mozilla and chrome
... remind me to start making contacts
... in terms of timelines, if we try to publish prior to TPAC, we need to draft something by Sept 20 or so.

paul: pronunciation info is new to the axTree, we just don't know enough about the mapping/bridging work that needs to happen and the burden on AT vendors.

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/08/12 14:27:12 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: JF irfan Dee janina Roy SteveNoble_ NeilS
Found Scribe: paul_grenier
Inferring ScribeNick: paul_grenier

WARNING: No "Topic:" lines found.


WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 12 Aug 2020
People with action items: 

WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]