W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2014

Re: [whatwg] Proposal: Inline pronounce element

From: Brett Zamir <brettz9@yahoo.com>
Date: Tue, 10 Jun 2014 06:59:03 +0800
Message-ID: <53963C37.3060206@yahoo.com>
To: whatwg@lists.whatwg.org
On 6/10/2014 3:05 AM, whatwg-request@lists.whatwg.org wrote:
> Message: 1
> Date: Sun, 08 Jun 2014 15:41:32 -0400
> From: timeless@gmail.com
> To: whatwg@lists.whatwg.org
> Subject: Re: [whatwg] Proposal: Inline pronounce element
> Message-ID: <20140608194132.7602328.57406.381@gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
> Tab wrote:
>> This is already theoretically addressed by <link rel=pronunciation>,
>> linking to a well-defined pronunciation file format. Nobody
>> implements that, but nobody implements anything new either, of course.
> Brett wrote:
>> I think it'd be a lot easier for sites, say along the lines of
>> Wikipedia, to support inline markup to allow users to get a word
>> referenced at the beginning of an article, for example, pronounced
>> accurately.
> Wikipedia can easily use data:... if it needs to.?
> And wiktionary already has a solution...
> A better challenge is explaining to a screen reader if "read" is "rEd" or "rehD" in a page where you want to define and use both. I claim that this can be addressed with id= on the link and a ref= (or similar) on the use.?
> But before User Agents should be asked to support this, I'd want to see real sites showing an interest.?
> Screen Reader vendors seem ok with the current state - they sell the pronunciation tables...

My thought was that browsers could expose some interface for getting the 
word pronounced even if the user was not using a screen reader. And 
without a site needing to have supplied it's own JavaScript to apply 
styling and buttons around such tags so that when clicked, a 
`SpeechSynthesisUtterance` would be made.

Received on Monday, 9 June 2014 22:59:35 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:21 UTC