IndieUI-ISSUE-8 (TTS context dictionary): Need a way to define a context and pronunciation dictionary on a per-resource basis. [IndieUI: User Context 1.0]

IndieUI-ISSUE-8 (TTS context dictionary): Need a way to define a context and pronunciation dictionary on a per-resource basis. [IndieUI: User Context 1.0]

http://www.w3.org/WAI/IndieUI/track/issues/8

Raised by: James Craig
On product: IndieUI: User Context 1.0

Possibly need a way to define page context dictionaries for text-to-speech. 
See https://github.com/darobin/respec/issues/108 for some background.

Basically, you could define (in one location) that ✔ and ✘ are spoken as "True" and "False" rather than needing to define it in the markup for each use.

<span role="text" aria-label="True">✔</span>
<span role="text" aria-label="False">✘</span>

We could also use something like this for phonetic hints for proper nouns or terminology that is uncommon outside the context of the document (and therefore mispronounce by the text-to-speech engine), where the text is not replaced, but the string is used to hint at the correct pronunciation.

I was thinking something along the lines of:

// contextual text alternatives for unicode chars
// (otherwise these would be spoken literally as the unicode descriptions such as "heavy ballot x"
window.accessibility.tts.phonetics.setValueForKey('✔', 'True');
window.accessibility.tts.phonetics.setValueForKey('✘', 'False');

// contextual pronunciation of proper nouns or other terminology
window.accessibility.tts.phonetics.setValueForKey('Knowbility', 'nobility');
window.accessibility.tts.phonetics.setValueForKey('WAI-ARIA', 'way aria');

It's possible this should use a phonemic alphabet for the pronunciation strings, but I'm not sure about the l18n implications of that decision at the time of this writing.

Received on Monday, 3 December 2012 20:16:58 UTC