W3C home > Mailing lists > Public > www-style@w3.org > February 2011

Re: "phonemes" property in the CSS3 Speech module

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 3 Feb 2011 16:28:01 -0800
Message-ID: <AANLkTin4Nnu8JXSvSH_+xMR724MeV8KKxiL_Z3rpETu7@mail.gmail.com>
To: Stephen Zilles <szilles@adobe.com>
Cc: "www-style@w3.org list" <www-style@w3.org>
Just to distill down the essential problem you have, and provide a
tl;dr version:

Authors may start with pages like this:

.a1678 { /* stupid class names are unfortunately common */
  phonemes "toe-MAH-toe";
  font-weight: bold;
<p>My doctor said to eat a <span class=a1678>tomato</span> every day.</p>

And then, at some point in the future, it gets changed to:

<p>My doctor said to take my <span class=a1678>vitamins</span> every day.</p>

(With the <span> being cargo-culted in because of the visual styling.)

Now, screen readers will say "My doctor said to take my toe-MAH-toe
every day.", to nonsensical results.

The problem here is the indirection for what is really a property of
the content.  You instead propose to do something like:

<p>My doctor said to eat a <span
pronounceas="toe-MAH-toe">tomato</span> every day.</p>

Then, if the content changes in the future, it's much more obvious
that this is wrong:

<p>My doctors said to take my <span
pronounceas="toe-MAH-toe">vitamins</span> every day.</p>

Received on Friday, 4 February 2011 00:28:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:07:55 UTC