Log in   Register a New Account

Accessify Forum - Independent Accessibility Discussion Since 2003; Professional, Moderated, Web-based, Archived

New to the forum?

Only an email address is required.

Register Here

Already registered? Log In

Currently Online

No registered users are online.

HTML5 Support for PLS (Pronunciation Lexicon Specification)

Reply with quote It appears I can now link HTML5 pages to a *.pls file made under the Pronunciation Lexicon Specification – http://www.w3.org/TR/pronunciation-lexicon/ I’d like to know what people here think of this method.

I would add a *.pls file into my website, such as example.pls in the root. In each HTML5 page, in the head element, I would add an element in the form of (if with a relative reference) <link rel=”pronunciation” href=”example.pls” />. I would support TTS in CSS3 using the CSS Speech Module – www.w3.org/TR/css3-speech/ Where the *.pls file is inadequate for a string in an HTML5 page’s body element, such as when the visual word “read” could be pronounced /reed/ or /red/ unless one pronunciation is exclusively specified, I would apply EPUB 3.0.1 even though the pages I’m authoring would not be EPUB files (idpf.org/epub/301 (see especially www.idpf.org/epub/301/spec/epub-overview.html#sec-tts (sec. 2.11)) and www.idpf.org/epub/301/spec/epub-contentdocs.html#sec-xhtml-ssml-attrib (sec. 2.1.3.2)).

The history of this discussion, not necessarily in chronological order, is that I asked in this forum if there’s a method and whether one was even needed was debated on this forum – http://www.accessifyforum.com/viewtopic.php?t=15249 I proposed to W3C that HTML5 include a method www.w3.org/Bugs/Public/show_bug.cgi?id=7601 and was told that a method would have to be already in the wild before it would be added to HTML5 and that a specification would also be needed, whereupon I tried writing a spec but gave up on it and so I closed the issue, after which someone else reopened the W3C issue and it was partly accepted; and I added “pronunciation” to RelExtensions for HTML5 http://wiki.whatwg.org/wiki/RelExtensions and then RelExtensions was replaced by a Microformats.org page http://microformats.org/wiki/existing-rel-values with some details of the “pronunciation” proposal also published by Microformats.org http://microformats.org/wiki/rel-pronunciation (all as accessed Jan. 2, 2015).

Now, I think, as I resume creating websites, I can support TTS with better clarity about what I intend in my pages but without having to spend enormous time creating parallel pages in SSML. And, if this method is good, I hope other website authors adapt or adopt it, so it can get better recognition in a future version of HTML by W3C and let authors have time for both accessibility support and content creation.

Opinions? Thank you very kindly.
Reply with quote Sorry for the problems with adding links to your post Nick. Your account is now authorised so you won’t have to mess about like that in future (we added some new protection since you last visited, and you didn’t make enough posts yet to avoid them). I updated your post so the URLs are all now linked.

Accessify Forum Administrator ~ Nigel Peck / Starstream
“Everything I say is not meant to be set in stone” – Van Morrison

Display posts from previous:   

All times are GMT

  • Reply to topic
  • Post new topic