<PaulG> (last week was an informal meeting)
<PaulG> We reflected on our conversation with ARIA WG and discussed our approach
<PaulG> I wrote a draft letter to ARIA WG that was reviewed by Janina, Irfan, and Mark.
<PaulG> Based on the conversations following TPAC, we, the Pronunciation Task Force (TF), decided to pursue the "single-attribute" approach for Specification for Spoken Presentation in HTML. Following that decision, the ARIA Working Group (WG) provided additional feedback that we would like to address. In an effort to reach prototype implementation, we will scale back the eight (8) sections of the specification (currently section 3.1) to four (4):[CUT]
<PaulG> break (pausing) phoneme sub Based on the gap analysis, the TF feels these qualities of speech represent the most value to the widest audience and propose they be included in the first phase of prototype development.
<JF> +1 to Neil, pause/break is very important
<PaulG> <break time="string" /> where the value is between 500ms and 2s (I think)
NeilS: Eloquence doesn't take the advantage of IPA. JAWS use Eloquence
aaronlev_: I will have another proposal for the specific use cases.
janina: ARIA part worries me because AT doesn't implement aria.
aaronlev_: this is driven by browser
JF: internationalization part is very important. Can we address this using IPA?
aaronlev_: IPA was not the only idea here... there are more ideas and nothing related to only one particular language
aaronlev_: If you guys want to discuss amongst you and come back, we will be happy to discuss. I will answer any question
janina: we have enough to kick this up
NeilS: thanks for the proposal
aaronlev_: having a global dictionary that you can override and keeping it simple for the browser
aaronlev_: James Craig and I are working on some of the syntax