Add ttsMarkup value?

[Matt Garrish]

Hi folks,

 

In looking at how to harmonize with ebook metadata, a hole we have is in identifying that a resource has been enhanced for TTS playback using any of PLS lexicons, SSML and/or CSS3 Speech.

 

ONIX code list 196 has a value for this, so should we also include an accessibilityFeature value “ttsMarkup”? (And that could be refined as /pls, /ssml or /css3speech if you want to be specific.)

 

All of these tts-enhancement technologies are available for web content generally, so the use is not specific to ebooks.

 

Matt

[Anastasia Cheetham]

On 2014-01-29, at 2:37 PM, Matt Garrish wrote:

ONIX code list 196 has a value for this, so should we also include an accessibilityFeature value “ttsMarkup”? (And that could be refined as /pls, /ssml or /css3speech if you want to be specific.)

+1

This seems like a reasonable addition to me. I don't see anything already in the spec that would cover this use case.

-- 
Anastasia Cheetham                    a...@anastasiacheetham.ca
Inclusive Design Research Centre              OCAD University